linux-kernel - Re: [patch -mm v2] cpusets: add memory_slab

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0903121137320.1514@chino.kir.corp.google.com>
Date:	Thu, 12 Mar 2009 11:43:57 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Matt Mackall <mpm@...enic.com>,
	Paul Menage <menage@...gle.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch -mm v2] cpusets: add memory_slab_hardwall flag

On Thu, 12 Mar 2009, Christoph Lameter wrote:

> > Cpusets are hierarchical, so it is quite possible that a parent cpuset
> > will include a group of cpus that has affinity to a specific group of
> > mems.  This isolates that cpuset and all of its children for NUMA
> > optimiziations.  Within that, there can be several descendant cpusets that
> > include disjoint subsets of mems to isolate the memory that can be used
> > for specific jobs.
> 
> Yes cpusets are hierachical for management purposes but it is well known
> that overlaying cpusets for running applications can cause issues with the
> scheduler etc. Jobs run in the leaf not in the higher levels that may
> overlap.
> 

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/