This is the accompanying qemu patch for the maximum number of total sectors
in an I/O feature.
Please CC me on replies, as I am not subscribed.
Thanks,
Avishay
Signed-off-by: Avishay Traeger avis...@il.ibm.com
---
diff --git a/block.c b/block.c
index 3f3496e..9fa97b8 100644
--- a/block.c
+++
This is a revised patch that allows the guest and host to negotiate the
maximum number of total sectors in an I/O. This feature has already been
added by Rusty to the virtio spec.
Please CC me on replies, as I am not subscribed.
Thanks,
Avishay
Signed-off-by: Avishay Traeger
Rusty Russell ru...@rustcorp.com.au wrote on 12/08/2009 07:48:00 AM:
Avishay; this would be the total sectors in an I/O, as separate from
SIZE_MAX
(maximum size of any single scatterlist entry) and SEG_MAX (maximum
number of
scatterlist entries)?
Correct. In the guest virtblk driver, it
I previously submitted a patch to have the guest virtio-blk driver get the
value for the maximum I/O size from the host bdrv, rather than assume that
there is no limit. Avi requested that I first patch the virtio spec
(http://ozlabs.org/~rusty/virtio-spec/). Below is that patch.
Please CC me
This is a patch to have the guest virtio-blk driver get the value for the
maximum I/O size from the host bdrv, rather than assume that there is no
limit. Right now we use it for an in-house bdrv driver that needs this
option. The patches are below, against the latest gits, split into kernel
Hello,
I am trying to compile kvm-userspace on one machine (let's call it the
build machine), and plan to use it on another (let's call it the target
machine). Both machines are x86-64. I got a fresh copy from git:
$ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
Initialized
