summaryrefslogtreecommitdiff
path: root/hw/virtio-net.c
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2011-01-10 17:15:10 +0100
committerKevin Wolf <kwolf@redhat.com>2011-01-24 11:08:51 +0100
commit493810940bfaad0fd5dd9bfb79cdc89519f89588 (patch)
tree4411cb848b5180d8792cc31ae5d01680997c0597 /hw/virtio-net.c
parentc641483fbe0aa08cd7c0580d019dc2d5a7e71138 (diff)
downloadqemu-493810940bfaad0fd5dd9bfb79cdc89519f89588.tar.gz
qemu-493810940bfaad0fd5dd9bfb79cdc89519f89588.tar.bz2
qemu-493810940bfaad0fd5dd9bfb79cdc89519f89588.zip
qcow2: Add QcowCache
This adds some new cache functions to qcow2 which can be used for caching refcount blocks and L2 tables. When used with cache=writethrough they work like the old caching code which is spread all over qcow2, so for this case we have merely a cleanup. The interesting case is with writeback caching (this includes cache=none) where data isn't written to disk immediately but only kept in cache initially. This leads to some form of metadata write batching which avoids the current "write to refcount block, flush, write to L2 table" pattern for each single request when a lot of cluster allocations happen. Instead, cache entries are only written out if its required to maintain the right order. In the pure cluster allocation case this means that all metadata updates for requests are done in memory initially and on sync, first the refcount blocks are written to disk, then fsync, then L2 tables. This improves performance of scenarios with lots of cluster allocations noticably (e.g. installation or after taking a snapshot). Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/virtio-net.c')
0 files changed, 0 insertions, 0 deletions