On Sat, Jul 26 2003, Lou Langholtz wrote:
> Con Kolivas wrote:
>
> >. . .
> >Actually this is not strange to me. It has become obvious that the
> >problems with interactivity that have evolved in 2.5 are not scheduler
> >related. Just try plugging in all the old 2.4 O(1) scheduler settings into
> >the current scheduler and you will see that it still performs badly. What
> >exactly is the cause is a mystery but seems to be more a combination of
> >factors with a careful look at the way the vm behaves being part of that.
> >. . .
> >
> Any chance that the problem may be due to the block layer system (and
> block driver(s)) getting more cycles than it should? Particularly with
Not likely
> the out-of-band like work queue scheduling? That would at least explain
If anything, 2.6 will unplug sooner than 2.4. 2.4 will unplug only when
someone does a wait_on_buffer/page, 2.6 will unplug when:
- queued requests exceed unplug threshold, 4 requests
- unplug timeout, 3ms
- someone doing wait_on_page/buffer
Can't rule out a bug of course, the horrible audio skips I've seen in
2.6 are not io related though. Block layer will only do out of band
unplugs for the timer unplug, and even that could be superceded by a new
request entering the queue (or someone doing wait_bla)
> the scheduling oddities I'm seeing with 2.6.0-test1 after a minute of so
> of intense I/O.
CPU or disk scheduling oddities?
People should try booting with elevator=deadline to see if it changes
anything for these types of workloads, AS is really not optimal for that
at all.
-- Jens Axboe- 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/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:29 EST