lkml.org 
[lkml]   [2002]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK
> I'm also a big fan of "Do that crap outside the kernel until it 
> works properly" type projects.

Agreed. That's why we have things like the lse (scalability) rollup
patches for 2.4. People have been playing with such things outside
the kernel. And nobody's suggesting that it should get accepted before
being properly tested.

> The Linux view should not be that N-way boxes are its manifest
> destiny. The same goes for thousands of threads. Linux works
> pretty well on 95% of the boxes that it is being run on. Lets
> not screw that up to fix the other 5%. Try some fixes _outside_
> the main kernel for a while, find a workable solution and then
> merge it in.

Why do you think these things are floating around as patches for
a while, and not going straight into the kernel?
Why do you think there are things like a Redhat Advanced server
build?

Nobody's trying to screw the desktop users, we're being mind-
bogglingly careful not to, in fact. If you have specific objections
to a particular patch, raise them as technical arguments. Saying
"we shouldn't do that because I'm not interested in it" is far
less useful.

The fact that there's lots of patches floating around for larger
systems isn't some evil plot to undermine the world - there's
just a lot of people working on it full time because that's where
much of the money is ...

M.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:18    [W:0.105 / U:0.800 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site