Messages in this thread | | | Date | Wed, 04 Jun 2008 14:16:43 -0700 | From | Max Krasnyansky <> | Subject | Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses) |
| |
Paul Jackson wrote: > Andi wrote: >> I occasionally recommended it to people because it was much easier >> to explain than replacing init. > > Definitely ... I'd do the same in such cases. >
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
| |