diff options
author | Christoph Hellwig <hch@lst.de> | 2010-02-10 23:37:09 +0100 |
---|---|---|
committer | Anthony Liguori <aliguori@us.ibm.com> | 2010-02-10 16:53:25 -0600 |
commit | 428c149b0be790b440e1cbee185b152cdb22feec (patch) | |
tree | d44fa0cdd84ba5fb9b4ea3c37791846c36d0a811 /hw/s390-virtio-bus.c | |
parent | 37d5ddd6f4a898134b6430c0126378baf5abff4b (diff) | |
download | qemu-428c149b0be790b440e1cbee185b152cdb22feec.zip qemu-428c149b0be790b440e1cbee185b152cdb22feec.tar.gz qemu-428c149b0be790b440e1cbee185b152cdb22feec.tar.bz2 |
block: add topology qdev properties
Add three new qdev properties to export block topology information to
the guest. This is needed to get optimal I/O alignment for RAID arrays
or SSDs.
The options are:
- physical_block_size to specify the physical block size of the device,
this is going to increase from 512 bytes to 4096 kilobytes for many
modern storage devices
- min_io_size to specify the minimal I/O size without performance impact,
this is typically set to the RAID chunk size for arrays.
- opt_io_size to specify the optimal sustained I/O size, this is
typically the RAID stripe width for arrays.
I decided to not auto-probe these values from blkid which might easily
be possible as I don't know how to deal with these issues on migration.
Note that we specificly only set the physical_block_size, and not the
logial one which is the unit all I/O is described in. The reason for
that is that IDE does not support increasing the logical block size and
at last for now I want to stick to one meachnisms in queue and allow
for easy switching of transports for a given backing image which would
not be possible if scsi and virtio use real 4k sectors, while ide only
uses the physical block exponent.
To make this more common for the different block drivers introduce a
new BlockConf structure holding all common block properties and a
DEFINE_BLOCK_PROPERTIES macro to add them all together, mirroring
what is done for network drivers. Also switch over all block drivers
to use it, except for the floppy driver which has weird driveA/driveB
properties and probably won't require any advanced block options ever.
Example usage for a virtio device with 4k physical block size and
8k optimal I/O size:
-drive file=scratch.img,media=disk,cache=none,id=scratch \
-device virtio-blk-pci,drive=scratch,physical_block_size=4096,opt_io_size=8192
aliguori: updated patch to take into account BLOCK events
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/s390-virtio-bus.c')
-rw-r--r-- | hw/s390-virtio-bus.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/hw/s390-virtio-bus.c b/hw/s390-virtio-bus.c index 6b6dafc..fa0a74f 100644 --- a/hw/s390-virtio-bus.c +++ b/hw/s390-virtio-bus.c @@ -123,7 +123,7 @@ static int s390_virtio_blk_init(VirtIOS390Device *dev) { VirtIODevice *vdev; - vdev = virtio_blk_init((DeviceState *)dev, dev->dinfo); + vdev = virtio_blk_init((DeviceState *)dev, dev->block.dinfo); if (!vdev) { return -1; } @@ -337,7 +337,7 @@ static VirtIOS390DeviceInfo s390_virtio_blk = { .qdev.name = "virtio-blk-s390", .qdev.size = sizeof(VirtIOS390Device), .qdev.props = (Property[]) { - DEFINE_PROP_DRIVE("drive", VirtIOS390Device, dinfo), + DEFINE_BLOCK_PROPERTIES(VirtIOS390Device, block), DEFINE_PROP_END_OF_LIST(), }, }; |