Paolo Valente 43c1b3d6e5 block, bfq: stress that low_latency must be off to get max throughput ... The introduction of the BFQ and Kyber I/O schedulers has triggered a new wave of I/O benchmarks. Unfortunately, comments and discussions on these benchmarks confirm that there is still little awareness that it is very hard to achieve, at the same time, a low latency and a high throughput. In particular, virtually all benchmarks measure throughput, or throughput-related figures of merit, but, for BFQ, they use the scheduler in its default configuration. This configuration is geared, instead, toward a low latency. This is evidently a sign that BFQ documentation is still too unclear on this important aspect. This commit addresses this issue by stressing how BFQ configuration must be (easily) changed if the only goal is maximum throughput. Signed-off-by: Paolo Valente <paolo.valente@linaro.org> Signed-off-by: Jens Axboe <axboe@fb.com>		2017-05-10 07:39:43 -06:00
..
00-INDEX	block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler	2017-04-19 08:29:02 -06:00
bfq-iosched.txt	block, bfq: stress that low_latency must be off to get max throughput	2017-05-10 07:39:43 -06:00
biodoc.txt
biovecs.txt
capability.txt
cfq-iosched.txt
cmdline-partition.txt
data-integrity.txt
deadline-iosched.txt
ioprio.txt
kyber-iosched.txt	blk-mq: introduce Kyber multiqueue I/O scheduler	2017-04-14 14:06:58 -06:00
null_blk.txt
pr.txt
queue-sysfs.txt	block: remove the discard_zeroes_data flag	2017-04-08 11:25:38 -06:00
request.txt
stat.txt
switching-sched.txt
writeback_cache_control.txt