(reiserfs) Re: More on 2.2.18pre2aa2

[Alan Cox]

> That problem: the original elevator code did not schedule I/O particularly
> fairly under certain I/O usage patterns. So it got fixed.

No it got hacked up a bit.

> Now, I see people trying to introduce the concept of elapsed time into
> that fix, which smells strongly of hack. How will this hack be cobbled

Actually my brain says that elapsed time based scheduling is the right thing
to do. It certainly works for networks


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/