[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1314786377.4653.19.camel@marge.simson.net>
Date: Wed, 31 Aug 2011 12:26:17 +0200
From: Mike Galbraith <efault@....de>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Gilad Ben-Yossef <gilad@...yossef.com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Anton Blanchard <anton@....ibm.com>,
Avi Kivity <avi@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Lai Jiangshan <laijs@...fujitsu.com>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Menage <menage@...gle.com>,
Stephen Hemminger <shemminger@...tta.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tim Pepper <lnxninja@...ux.vnet.ibm.com>
Subject: Re: [RFC PATCH 00/32] Nohz cpusets (was: Nohz Tasks)
On Wed, 2011-08-31 at 11:28 +0200, Peter Zijlstra wrote:
> On Wed, 2011-08-31 at 05:47 +0200, Mike Galbraith wrote:
> > On Tue, 2011-08-30 at 16:06 +0200, Frederic Weisbecker wrote:
> >
> > > Ah I haven't tested with that isolcpus especially as it's headed toward
> > > removal.
> >
> > It is? Is it being replaced by something? (I find it useful)
>
> cpusets? Afaict all it does is not include a number of cpus in the sched
> domains, creating a bunch of independent scheduling cpus. You can use
> cpusets to get to the same state.
Guess I'll have to try creating a cpuset per cpu, and see how it
compares to isolcpus. cset shield --cpu 4-63 didn't work well enough.
-Mike
--
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