On Sun, Apr 15, 2007 at 10:48:24PM +0200, Ingo Molnar wrote:
>
> * Matt Mackall <[email protected]> wrote:
>
> > Look at what happened with I/O scheduling. Opening things up to some
> > new ideas by making it possible to select your I/O scheduler took us
> > from 10 years of stagnation to healthy, competitive development, which
> > gave us a substantially better I/O scheduler.
>
> actually, 2-3 years ago we already had IO schedulers, and my opinion
> against plugsched back then (also shared by Nick and Linus) was very
> much considering them. There are at least 4 reasons why I/O schedulers
> are different from CPU schedulers:
...
> 3) I/O schedulers are pretty damn clean code, and plugsched, at least
> the last version i saw of it, didnt come even close.
That's irrelevant. Plugsched was an attempt to get alternative
schedulers exposure in mainline. I know, because I remember
encouraging Bill to pursue it. Not only did you veto plugsched (which
may have been a perfectly reasonable thing to do), but you also vetoed
the whole concept of multiple schedulers in the tree too. "We don't
want to balkanize the scheduling landscape".
And that latter part is what I'm claiming has set us back for years.
It's not a technical argument but a strategic one. And it's just not a
good strategy.
> 4) the good thing that happened to I/O, after years of stagnation isnt
> I/O schedulers. The good thing that happened to I/O is called Jens
> Axboe. If you care about the I/O subystem then print that name out
> and hang it on the wall. That and only that is what mattered.
Disagree. Things didn't actually get interesting until Nick showed up
with AS and got it in-tree to demonstrate the huge amount of room we
had for improvement. It took several iterations of AS and CFQ (with a
couple complete rewrites) before CFQ began to look like the winner.
The resulting time-sliced CFQ was fairly heavily influenced by the
ideas in AS.
Similarly, things in scheduler land had been pretty damn boring until
Con finally got Andrew to take one of his schedulers for a spin.
> nor was the non-modularity of some piece of code ever an impediment to
> competition. May i remind you of the pretty competitive SLAB allocator
> landscape, resulting in things like the SLOB allocator, written by
> yourself? ;-)
Thankfully no one came out and said "we don't want to balkanize the
allocator landscape" when I submitted it or I probably would have just
dropped it, rather than painfully dragging it along out of tree for
years. I'm not nearly the glutton for punishment that Con is. :-P
--
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
