Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Paul Jackson <pj@...>
Cc: Andi Kleen <andi@...>, <ioe-lkml@...>, <sivanich@...>, <a.p.zijlstra@...>, <linux-kernel@...>, <kernel@...>, <dfults@...>, <devik@...>, <dino@...>, <emmanuel.pacaud@...>, <deweerdt@...>, <mingo@...>, <colpatch@...>, <nickpiggin@...>, <rostedt@...>, <oleg@...>, <paulmck@...>, <menage@...>, <rddunlap@...>, <suresh.b.siddha@...>, <tglx@...>
Date: Wednesday, June 4, 2008 - 5:16 pm

Paul Jackson wrote:

btw I'm putting together a set of scripts that I call "syspart" (for "system
partitioning") which creates cpusets, sets up IRQ affinity, etc at boot. We
can make your init replacement a part of that package. You could then tell
people to
1. Install syspart rpm
2. Change boot opts to "init=/sbin/syspart par0_cpus=0-3 par0_mems=0-2 par0_init"

The thing will then create /dev/cpuset/par0 with cpus0-3 and mems0-2 and put
/sbin/init into that cpuset.

With the exception of the #1 it's as easy to explain as "isolcpus=".

Paul, I beleive you mentioned a while ago that the tools you guys use for this
aren't open source. Has that changed ? If not I'll write my own. I have all
the scripts ready to go but as you pointed out it has to be a standalone
statically linked binary.

Thanx
Max

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Michael Trimarchi, (Thu Jun 5, 10:57 am)
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Max Krasnyansky, (Wed Jun 4, 5:16 pm)