[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1314800784.3578.28.camel@twins>
Date: Wed, 31 Aug 2011 16:26:23 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Gilad Ben-Yossef <gilad@...yossef.com>
Cc: Mike Galbraith <efault@....de>,
Frederic Weisbecker <fweisbec@...il.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 17:00 +0300, Gilad Ben-Yossef wrote:
> >> > cpusets? Afaict all it does is not include a number of cpus in the sched
>
> I think you meant to write cpuisol here :-)
Uhh, yeah ;-)
> >> > 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.
> >
> > You need to play with the sched_load_balance file, no idea what this
> > cset utility is though, never encountered it before.
> >
>
> It's just a python wrapper around the /cgroup file system.
ok, just never encountered 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