summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorChris Mason <chris.mason@oracle.com>2009-06-09 15:39:08 -0400
committerChris Mason <chris.mason@oracle.com>2009-06-10 11:29:49 -0400
commitd84275c938e1a5e2dc5b89eb9b878e0ddb2c55e0 (patch)
tree7d8f49716140738c1bdcb97978b06328dd148a7a /virt/kvm
parent585ad2c3797dcaa643aeba75b9f072778adf3490 (diff)
downloadblackbird-op-linux-d84275c938e1a5e2dc5b89eb9b878e0ddb2c55e0.tar.gz
blackbird-op-linux-d84275c938e1a5e2dc5b89eb9b878e0ddb2c55e0.zip
Btrfs: don't allow WRITE_SYNC bios to starve out regular writes
Btrfs uses dedicated threads to submit bios when checksumming is on, which allows us to make sure the threads dedicated to checksumming don't get stuck waiting for requests. For each btrfs device, there are two lists of bios. One list is for WRITE_SYNC bios and the other is for regular priority bios. The IO submission threads used to process all of the WRITE_SYNC bios first and then switch to the regular bios. This commit makes sure we don't completely starve the regular bios by rotating between the two lists. WRITE_SYNC bios are still favored 2:1 over the regular bios, and this tries to run in batches to avoid seeking. Benchmarking shows this eliminates stalls during streaming buffered writes on both multi-device and single device filesystems. If the regular bios starve, the system can end up with a large amount of ram pinned down in writeback pages. If we are a little more fair between the two classes, we're able to keep throughput up and make progress on the bulk of our dirty ram. Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud