lkml.org 
[lkml]   [2009]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch -mm] cpusets: add memory_slab_hardwall flag
From
Date
On Sun, 2009-03-08 at 09:27 -0700, David Rientjes wrote:
> Adds a per-cpuset `memory_slab_hardwall' flag.
>
> The slab allocator interface for determining whether an object is allowed
> is
>
> int current_cpuset_object_allowed(int node, gfp_t flags)
>
> This returns non-zero when the object is allowed, either because
> current's cpuset does not have memory_slab_hardwall enabled or because
> it allows allocation on the node. Otherwise, it returns zero.
>
> This interface is lockless because a task's cpuset can always be safely
> dereferenced atomically.
>
> For slab, if the physical node id of the cpu cache is not from an
> allowable node, the allocation will fail. If an allocation is targeted
> for a node that is not allowed, we allocate from an appropriate one
> instead of failing.
>
> For slob, if the page from the slob list is not from an allowable node,
> we continue to scan for an appropriate slab. If none can be used, a new
> slab is allocated.

Looks fine to me, if a little expensive. We'll be needing SLQB support
though.

--
http://selenic.com : development and support for Mercurial and Linux




\
 
 \ /
  Last update: 2009-03-08 18:05    [W:1.827 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site