diff options
author | Shaohua Li <shli@fusionio.com> | 2012-11-09 08:44:27 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2012-11-09 08:44:27 +0100 |
commit | bee0393cc12b6d8f10e884e555a095e050e0b2b9 (patch) | |
tree | eabe7526c63a6a965cf0aa5574c222ff2f431e13 /block/blk-core.c | |
parent | 3d106fba2e7eb6967b1e2cc147a6894ec4307cef (diff) | |
download | linux-stable-bee0393cc12b6d8f10e884e555a095e050e0b2b9.tar.gz linux-stable-bee0393cc12b6d8f10e884e555a095e050e0b2b9.tar.bz2 linux-stable-bee0393cc12b6d8f10e884e555a095e050e0b2b9.zip |
block: recursive merge requests
In a workload, thread 1 accesses a, a+2, ..., thread 2 accesses a+1, a+3,....
When the requests are flushed to queue, a and a+1 are merged to (a, a+1), a+2
and a+3 too to (a+2, a+3), but (a, a+1) and (a+2, a+3) aren't merged.
If we do recursive merge for such interleave access, some workloads throughput
get improvement. A recent worload I'm checking on is swap, below change
boostes the throughput around 5% ~ 10%.
Signed-off-by: Shaohua Li <shli@fusionio.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-core.c')
0 files changed, 0 insertions, 0 deletions