[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0903121145510.27660@qirst.com>
Date: Thu, 12 Mar 2009 11:47:32 -0400 (EDT)
From: Christoph Lameter <cl@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
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 Tue, 10 Mar 2009, David Rientjes wrote:
> > The description is not accurate. This feature is only useful if someone
> > comes up with a crummy cpuset definition in which a processor is a member
> > of multiple cpusets and thus the per cpu queues of multiple subsystems get
> > objects depending on which cpuset is active.
> >
>
> 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.
--
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/
Powered by blists - more mailing lists