mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-21 11:44:01 +08:00
43c1b3d6e5
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> |
||
|---|---|---|
| .. | ||
| 00-INDEX | ||
| bfq-iosched.txt | ||
| biodoc.txt | ||
| biovecs.txt | ||
| capability.txt | ||
| cfq-iosched.txt | ||
| cmdline-partition.txt | ||
| data-integrity.txt | ||
| deadline-iosched.txt | ||
| ioprio.txt | ||
| kyber-iosched.txt | ||
| null_blk.txt | ||
| pr.txt | ||
| queue-sysfs.txt | ||
| request.txt | ||
| stat.txt | ||
| switching-sched.txt | ||
| writeback_cache_control.txt | ||