summaryrefslogtreecommitdiffstats
path: root/drivers/md/bcache/writeback.c
diff options
context:
space:
mode:
authorTang Junhui <tang.junhui@zte.com.cn>2018-01-08 21:21:21 +0100
committerJens Axboe <axboe@kernel.dk>2018-01-08 21:29:00 +0100
commit4eca1cb28d8b0574ca4f1f48e9331c5f852d43b9 (patch)
tree45a5d565193993e41d3cf8a2e78a363dc6f92883 /drivers/md/bcache/writeback.c
parentbcache: Use PTR_ERR_OR_ZERO() (diff)
downloadlinux-4eca1cb28d8b0574ca4f1f48e9331c5f852d43b9.tar.xz
linux-4eca1cb28d8b0574ca4f1f48e9331c5f852d43b9.zip
bcache: segregate flash only volume write streams
In such scenario that there are some flash only volumes , and some cached devices, when many tasks request these devices in writeback mode, the write IOs may fall to the same bucket as bellow: | cached data | flash data | cached data | cached data| flash data| then after writeback of these cached devices, the bucket would be like bellow bucket: | free | flash data | free | free | flash data | So, there are many free space in this bucket, but since data of flash only volumes still exists, so this bucket cannot be reclaimable, which would cause waste of bucket space. In this patch, we segregate flash only volume write streams from cached devices, so data from flash only volumes and cached devices can store in different buckets. Compare to v1 patch, this patch do not add a additionally open bucket list, and it is try best to segregate flash only volume write streams from cached devices, sectors of flash only volumes may still be mixed with dirty sectors of cached device, but the number is very small. [mlyle: fixed commit log formatting, permissions, line endings] Signed-off-by: Tang Junhui <tang.junhui@zte.com.cn> Reviewed-by: Michael Lyle <mlyle@lyle.org> Signed-off-by: Michael Lyle <mlyle@lyle.org> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/md/bcache/writeback.c')
0 files changed, 0 insertions, 0 deletions