[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130911213656.GA15367@somewhere>
Date: Wed, 11 Sep 2013 23:36:58 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: Mike Galbraith <bitbucket@...ine.de>,
Gilad Ben-Yossef <gilad@...yossef.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Mike Frysinger <vapier@...too.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of
cpus.
On Wed, Sep 11, 2013 at 02:21:06PM +0000, Christoph Lameter wrote:
> On Wed, 11 Sep 2013, Mike Galbraith wrote:
>
> > Mind saying why? To me, creating properties of exclusive sets of CPUs
> > that the interface which manages sets and their properties is not fully
> > aware of is a dainbramaged thing to do.
>
> cpusets is being replaced by cgropus.
You are confusing me. Cpusets is a cgroups subsystem, how can it be replaced
by it?
--
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