lkml.org 
[lkml]   [2009]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch -mm v2] cpusets: add memory_slab_hardwall flag
On Thu, 12 Mar 2009, Christoph Lameter wrote:

> > Yes, jobs are running in the leaf with my above example. And it's quite
> > possible that the higher level has segmented the machine for NUMA locality
> > and then further divided that memory for individual jobs. When a job
> > completes or is killed, the slab cache that it has allocated can be freed
> > in its entirety with no partial slab fragmentation (i.e. there are no
> > objects allocated from its slabs for disjoint, still running jobs). That
> > cpuset may then serve another job.
>
> Looks like we are talking about a differing project here. Partial slabs
> are shared between all processors with SLUB. Slab shares the partial slabs
> for the processors on the same node.
>

If `memory_slab_hardwall' is set for a cpuset, its tasks will only pull a
slab off the partial list that was allocated on an allowed node. So in my
earlier example which segments the machine via cpusets for NUMA locality
and then divides those cpusets further for exclusive memory to provide to
individual jobs, slab allocations will be constrained within the cpuset of
the task that allocated them. When a job dies, all slab allocations are
freed so that no objects remain on the memory allowed to that job and,
thus, no partial slabs remain (i.e. there were no object allocations on
the job's slabs from disjoint cpusets because of the exclusivity).


\
 
 \ /
  Last update: 2009-03-12 20:37    [from the cache]
©2003-2011 Jasper Spaans