Re: [PATCH] block/elevator updates + deadline i/o scheduler

[Jens Axboe <axboe@suse.de>]

On Tue, Jul 30 2002, Bill Davidsen wrote:
> On Fri, 26 Jul 2002, Jens Axboe wrote:
> > Finally, I've done some testing on it. No testing on whether this really
> > works well in real life (that's what I want testers to do), and no
> > testing on benchmark performance changes etc. What I have done is
> > beat-up testing, making sure it works without corrupting your data. I'm
> > fairly confident that does. Most testing was on SCSI (naturally),
> > however IDE has also been tested briefly.
> 
> First, great job on the explanation, it went right in my folder for "when
> the docs are clear" explanations.

Thanks :-)

> Now a request, if someone is running a database app and tests this I'd
> love to see the results. I expect things like LMbench to show more threads
> ending at the same time, but will it help a reall app?

Note that the deadline i/o scheduler only considers deadlines on
individual requests so far, so there's no real guarentee that process X,
Y, and Z will receive equal share of the bandwidth. This is something
I'm thinking about, though.

My testing does seem to indicate that the deadline scheduler is fairer
than the linus scheduler, but ymmv.

> I bet it was tested briefly on IDE, my last use of IDE a week or so ago
> lasted until I did "make dep" and the output went all over every attached
> drive :-( Still, nice to know it will work if IDE makes it into 2.5.

:/

I'll say that 2.5.29 IDE did work fine for the testing I did with the
deadline scheduler, at least it survived a dbench 64 (that's about the
testing it got).

-- 
Jens Axboe