[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64N.0611010154290.32554@attu4.cs.washington.edu>
Date: Wed, 1 Nov 2006 01:58:15 -0800 (PST)
From: David Rientjes <rientjes@...washington.edu>
To: Paul Jackson <pj@....com>
cc: menage@...gle.com, dev@...nvz.org, vatsa@...ibm.com,
sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net,
balbir@...ibm.com, haveblue@...ibm.com,
linux-kernel@...r.kernel.org, matthltc@...ibm.com,
dipankar@...ibm.com, rohitseth@...gle.com
Subject: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
On Wed, 1 Nov 2006, Paul Jackson wrote:
> David wrote:
> > - While the process containers are only single-level, the controllers are
> > _inherently_ hierarchial just like a filesystem. So it appears that
>
> Cpusets certainly enjoys what I would call hierarchical process
> containers. I can't tell if your flat container space is just
> a "for instance", or you're recommending we only have a flat
> container space.
>
This was using the recommendation of "each process belongs to a single
container that can be attached to controller nodes later." So while it is
indeed possible for the controllers, whatever they are, to be hierarchical
(and most assuredly should be), what is the objection against grouping
processes in single-level containers? The only difference is that now
when we assign processes to specific controllers with their attributes set
as we desire, we are assigning a container (or group) processes instead of
individual ones.
David
-
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