[lkml]   [2010]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH/RFCv4 0/6] The Contiguous Memory Allocator framework
    On Fri, 20 Aug 2010 15:15:10 +0200, Peter Zijlstra <> wrote:
    > So the idea is to grab a large chunk of memory at boot time and then
    > later allow some device to use it?
    > I'd much rather we'd improve the regular page allocator to be smarter
    > about this. We recently added a lot of smarts to it like memory
    > compaction, which allows large gobs of contiguous memory to be freed for
    > things like huge pages.
    > If you want guarantees you can free stuff, why not add constraints to
    > the page allocation type and only allow MIGRATE_MOVABLE pages inside a
    > certain region, those pages are easily freed/moved aside to satisfy
    > large contiguous allocations.

    I'm aware that grabbing a large chunk at boot time is a bit of waste of
    space and because of it I'm hoping to came up with a way of reusing the
    space when it's not used by CMA-aware devices. My current idea was to
    use it for easily discardable data (page cache?).

    > Also, please remove --chain-reply-to from your git config. You're using
    > 1.7 which should do the right thing (--no-chain-reply-to) by default.


    Best regards, _ _
    | Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
    | Computer Science, Michał "mina86" Nazarewicz (o o)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2010-08-26 03:31    [W:0.024 / U:6.732 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site