I was too. However it didn't seem to make too much of a difference in
real life, I guess your test cases shows a bit differently.
> Appended here is a program which creates 100,000 small files.
> Using ext2 on -pre5. We see how long it takes to run
>
> (make-many-files ; sync)
>
> For several values of queue_nr_requests:
>
> queue_nr_requests: 128 8192 32768
> execution time: 4:43 3:25 3:20
>
> Almost all of the execution time is in the `sync'.
>
> This is on a disk with a 2 meg cache which does pretty aggressive
> write-behind. I expect the difference would be worse with a disk
> which doesn't help so much.
>
> By restricting the number of requests in flight to 128 we're
> giving new requests only a very small chance of getting merged with
> an existing request. More seeking.
>
> OK, not an interesting workload. But I suspect that there are real
> workloads which will be bitten by this.
>
> Why is the queue length so tiny now? Latency? If so, couldn't this
> be addressed by giving reads higher priority versus writes?
Should be possible. Try for yourself. When you do your 100,000 small
file tes with 8k or more of requests, how is interactive feel of other
programs accessing the same spindle? Play around with the READ and WRITE
intial elevator sequence numbers, repeat :-)
-- 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/