Quoting Robert Love <rml@tech9.net>:
> We strive for simple interfaces here in Linux :)
>
> If you want to give them exclusive access, you need to bind all the
> other processes to the other processors. One easy way to do this is to
> have init bind itself elsewhere on boot.
Interesting idea. AFAICS, this involves either changing the code of /sbin/init
to set its affinity to a default cpu mask (provided by a kernel boot flag, I
presume), or using taskset-like functionality and then hoping that all current
shells etc. die before the programs I care about start.
Would it not be better to simply have the kernel use the boot flag directly as
the default CPU mask setting?
[ I can see the argument that "if you need such control, you should set up your
distro to deal with it", but that is a level of tweaking I would like to avoid
for my customers ]
Thanks, Shaheed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:28 EST