[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:

>We can already set different figures for different drives.


>Would it really be more than 30 minutes of work to put in
>a different request # limit for each drive that automatically
>satisfies the latency specified by the user?

Note that if you know the transfer rate of each of your harddisk you can
just almost emulate the "in function of time" behaviour by converting from
"throughput" and "latency in function of time", to "latency in function of
bh sized requests". (one userspace script could do that automatically for
example using hdparm to first benchmark the throughput)

The reason I prefer working with "latency in function of bh sized
requests" in kernel space is that I can just use one constant for most of
the blockdevices. Using the same latency setting with the "in function of
time approch" would be wrong instead (and you should gather some hardware
info from the device before you are able to decide a good constant).


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.164 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site