That completely ignores that there is a _bug_ there currently. There was
a reason I removed disabled clustering, you know... 2.4 before the
change oopses, 2.4.18-preX (forget when Marcelo took the patch) has it
> > Now, disabling request merging for MO devices might make a whole lot
> > more sense. That might be worth while trying, and I'd be happy to give
> > you a patch to try that out instead.
> I don't think that should be required actually. The killer on M/O disks
> is seek time, and to an extent rotational latency (its 3 trips round a
> cheaper M/O disk to rewrite a sector). If anything clustering writes to
> the same track should be a big win.
You are probably right. Can't make pigs fly :-)
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/