[lkml]   [2007]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
    On Fri, 26 Jan 2007, Christoph Lameter wrote:

    > Unmovable allocations in the movable zone. Yuck.

    I know, but my objective at this time is to allow the hugepage pool to be
    resized at runtime for situations where the number of required hugepages
    is not known in advance. Having a zone for movable pages allows that to
    happen. Also, it's possible that migration of hugepages will be supported
    at some time in the future. That's a more reasonable possibility than
    moving kernel memory.

    > Why dont you abandon the
    > whole concept of statically sized movable zone and go back to the nice
    > earlier idea of dynamically assigning MAX_ORDER chunks to be movable or not?

    Because Andrew has made it pretty clear he will not take those patches on
    the grounds of complexity - at least until it can be shown that they fix
    the e1000 problem. Any improvement on the behavior of those patches such
    as address biasing to allow memory hot-remove of the higher addresses
    makes them even more complex.

    Also, almost every time the anti-frag patches are posted, someone suggests
    that zones be used instead. I wanted to show what those patches look like.
    (of course, every time I post the zone approach, someone suggests I go
    back the other way)

    Mel Gorman
    Part-time Phd Student Linux Technology Center
    University of Limerick IBM Dublin Software Lab
    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: 2007-01-26 18:07    [W:0.031 / U:1.476 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site