[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080604152317.5a36d2cc.pj@sgi.com>
Date: Wed, 4 Jun 2008 15:23:17 -0500
From: Paul Jackson <pj@....com>
To: Andi Kleen <andi@...stfloor.org>
Cc: maxk@...lcomm.com, andi@...stfloor.org, ioe-lkml@...eria.de,
sivanich@....com, a.p.zijlstra@...llo.nl,
linux-kernel@...r.kernel.org, kernel@...ivas.org, dfults@....com,
devik@....cz, dino@...ibm.com, emmanuel.pacaud@...v-poitiers.fr,
deweerdt@...e.fr, mingo@...e.hu, colpatch@...ibm.com,
nickpiggin@...oo.com.au, rostedt@...dmis.org, oleg@...sign.ru,
paulmck@...ibm.com, menage@...gle.com, rddunlap@...l.org,
suresh.b.siddha@...el.com, tglx@...utronix.de
Subject: Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may
have realtime uses)
Andi, replying to Max:
> > That script will move init itself into the appropriate cpuset and from then on
> > everything will inherit it.
>
> It won't be the parent of the other init scripts.
True, but init will be the parent of other init scripts,
and init itself was moved into the appropriate cpuset.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.940.382.4214
--
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