[lkml]   [2007]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 00/10] foundations for reserve-based allocation
    On Mon, 6 Aug 2007, Peter Zijlstra wrote:

    > We want a guarantee for N bytes from kmalloc(), this translates to a demand
    > on the slab allocator for 2*N+m (due to the power-of-two nature of kmalloc
    > slabs), where m is the meta-data needed by the allocator itself.

    The guarantee occurs in what context? Looks like its global here but
    allocations may be restricted to a cpuset context? What happens in a
    GFP_THISNODE allocation? Or a memory policy restricted allocations?

    > So we need functions translating our demanded kmalloc space into a page
    > reserve limit, and then need to provide a reserve of pages.

    Only kmalloc? What about skb heads and such?

    > And we need to ensure that once we hit the reserve, the slab allocator honours
    > the reserve's access. That is, a regular allocation may not get objects from
    > a slab allocated from the reserves.

    From a cpuset we may hit the reserves since cpuset memory is out and then
    the rest of the system fails allocations?
    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-08-06 19:59    [W:0.019 / U:69.128 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site