summaryrefslogtreecommitdiffstats
path: root/block/bfq-iosched.c
diff options
context:
space:
mode:
authorPaolo Valente <paolo.valente@linaro.org>2017-11-13 07:34:07 +0100
committerJens Axboe <axboe@kernel.dk>2017-11-14 20:13:33 -0700
commit68017e5d87a2477d40476f1a0a06f202ee79316b (patch)
treef88bf82de22ae2d7c73ce2c80ce2f124701a5bae /block/bfq-iosched.c
parent4fc930896db910c39999ed0e298798b57362772a (diff)
downloadlinux-0-day-68017e5d87a2477d40476f1a0a06f202ee79316b.tar.gz
linux-0-day-68017e5d87a2477d40476f1a0a06f202ee79316b.tar.xz
doc, block, bfq: update max IOPS sustainable with BFQ
We have investigated more deeply the performance of BFQ, in terms of number of IOPS that can be processed by the CPU when BFQ is used as I/O scheduler. In more detail, using the script [1], we have measured the number of IOPS reached on top of a null block device configured with zero latency, as a function of the workload (sequential read, sequential write, random read, random write) and of the system (we considered desktops, laptops and embedded systems). Basing on the resulting figures, with this commit we update the current, conservative IOPS range reported in BFQ documentation. In particular, the documentation now reports, for each of three different systems, the lowest number of IOPS obtained for that system with the above test (namely, the value obtained with the workload leading to the lowest IOPS). [1] https://github.com/Algodev-github/IOSpeed Reviewed-by: Lee Tibbert <lee.tibbert@gmail.com> Signed-off-by: Paolo Valente <paolo.valente@linaro.org> Signed-off-by: Luca Miccio <lucmiccio@gmail.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/bfq-iosched.c')
0 files changed, 0 insertions, 0 deletions