aboutsummaryrefslogtreecommitdiff
path: root/hw/xio3130_downstream.h
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2012-11-14 15:45:38 +0100
committerStefan Hajnoczi <stefanha@redhat.com>2013-01-02 16:08:51 +0100
commit392808b49b6aee066d0c1d200e72fc3dc11c9d0f (patch)
tree1bc5e98807a0356500a99fd8cd842c560622a063 /hw/xio3130_downstream.h
parente72f66a0a20f38d0c7576f6c0aec0ca644976e35 (diff)
downloadqemu-392808b49b6aee066d0c1d200e72fc3dc11c9d0f.zip
qemu-392808b49b6aee066d0c1d200e72fc3dc11c9d0f.tar.gz
qemu-392808b49b6aee066d0c1d200e72fc3dc11c9d0f.tar.bz2
virtio-blk: add x-data-plane=on|off performance feature
The virtio-blk-data-plane feature is easy to integrate into hw/virtio-blk.c. The data plane can be started and stopped similar to vhost-net. Users can take advantage of the virtio-blk-data-plane feature using the new -device virtio-blk-pci,x-data-plane=on property. The x-data-plane name was chosen because at this stage the feature is experimental and likely to see changes in the future. If the VM configuration does not support virtio-blk-data-plane an error message is printed. Although we could fall back to regular virtio-blk, I prefer the explicit approach since it prompts the user to fix their configuration if they want the performance benefit of virtio-blk-data-plane. Limitations: * Only format=raw is supported * Live migration is not supported * Block jobs, hot unplug, and other operations fail with -EBUSY * I/O throttling limits are ignored * Only Linux hosts are supported due to Linux AIO usage Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'hw/xio3130_downstream.h')
0 files changed, 0 insertions, 0 deletions