[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080604122644.cd73bfb9.pj@sgi.com>
Date: Wed, 4 Jun 2008 12:26:44 -0500
From: Paul Jackson <pj@....com>
To: Mark Hounschell <dmarkh@....rr.com>
Cc: nickpiggin@...oo.com.au, a.p.zijlstra@...llo.nl,
ioe-lkml@...eria.de, linux-kernel@...r.kernel.org,
kernel@...ivas.org, dfults@....com, devik@....cz, sivanich@....com,
dino@...ibm.com, emmanuel.pacaud@...v-poitiers.fr,
deweerdt@...e.fr, mingo@...e.hu, colpatch@...ibm.com,
maxk@...lcomm.com, 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)
Mark wrote:
> What is an abonination, is that cpusets are equired for this type of
> isolation to begin with, even on a 2 processor machine.
Just to be sure I'm following you here, you stating that you
want to be able to manipulate the isolated cpu map at runtime,
not just with the boot option isolcpus, right? Where this
isolated cpu map works just fine even on systems which do
not have cpusets configured, right?
--
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