Re: 2.6 must-fix list, v2

From: Robert Love <rml@tech9.net>
To: shaheed <srhaque@iee.org>
Cc: Felipe Alfaro Solana <yo@felipe-alfaro.com>,
	Andrew Morton <akpm@digeo.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6 must-fix list, v2
Date: 15 May 2003 16:20:11 -0400	[thread overview]
Message-ID: <1053030010.899.24.camel@icbm> (raw)
In-Reply-To: <200305152107.17419.srhaque@iee.org>

On Thu, 2003-05-15 at 16:07, shaheed wrote:

> I have no idea with whom to persue this path, and as I say, I feel that 
> solving this once for each distro is crazy IMHO.

It does not have to be done for each distribution. Modify the SysVinit
package directly to support this feature. All init needs to do is bind
itself to the allowed processors prior to its first fork(). This can be
done as part of the core init package, and thus all distributions
automatically reap the benefits.

If init is not modified, then it can be done in rc.d or wherever by
hand.

> I'm sorry to appear foolish, but as explained above, I genuinely don't 
> understand why this does not belong in the kernel. I would be grateful for 
> elaboration. If I really am being thick, then just ignore me and I'll just 
> solve this for myself using route 4.

Things which can be done in user-space should be done in user-space.
There is absolutely zero reason to do this in the kernel.  init can do
it.

Submit a patch to the init maintainer to have it bind itself on boot to
a given command line value. Maybe I will do this if I find the time...

	Robert Love