[lkml]   [2000]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: More on 2.2.18pre2aa2
On Tue, 12 Sep 2000, Rik van Riel wrote:

>The large IO delays I'm seeing in certain tests have
>been traced back to the /elevator/ code. I think I'll

Actually the elevator works as in 2.2.15 (before any fix). The latency
settings are too high. They should be around 250 for reads and 500 for

If you want better latency than that you should reinsert the stuff that we
had until test1 that account the position where the request is put on the
queue. We backed it out because it was making a performance difference.

Even if you disable the elevator completly (so if you use elevator_noop)
with the long queues we have these days you'll still get bad latency.

Please try to decrease the size of the queue if even "enabling" the
latency control doesn't make a difference.

BTW, 2.2.18pre2aa2 put the elevator in sync with 2.4.x using the settings
250 for reads and 500 for writes. Note that 250 for reads - without the
logic that take into account the position the request is put in the queue
- is much more than 250 with the previous logic included.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.104 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site