[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070608130517.8e2c5d51.pj@sgi.com>
Date: Fri, 8 Jun 2007 13:05:17 -0700
From: Paul Jackson <pj@....com>
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: menage@...gle.com, vatsa@...ibm.com, linux-kernel@...r.kernel.org,
ckrm-tech@...ts.sourceforge.net, balbir@...ibm.com,
haveblue@...ibm.com, xemul@...ru, dev@...ru,
containers@...ts.osdl.org, ebiederm@...ssion.com,
mbligh@...gle.com, rohitseth@...gle.com, serue@...ibm.com,
akpm@...ux-foundation.org, svaidy@...ux.vnet.ibm.com, cpw@....com,
devel@...nvz.org, serge@...lyn.com
Subject: Re: [ckrm-tech] [PATCH 00/10] Containers(V10): Generic Process
Containers
Serge wrote:
> Paul (Jackson), is this comment added in cpusets close enough to what
> you were asking for?
This comment?
+ * Currently we refuse to set up the container - thereby
+ * refusing the task to be entered, and as a result refusing
+ * the sys_unshare() or clone() which initiated it - if any
+ * sibling cpusets have exclusive cpus or mem.
+ *
+ * If this becomes a problem for some users who wish to
+ * allow that scenario, then cpuset_post_clone() could be
+ * changed to grant parent->cpus_allowed-sibling_cpus_exclusive
+ * (and likewise for mems) to the new container.
Nice - thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.925.600.0401
-
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