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
On 12/08/2009 11:44 AM, Avishay Traeger1 wrote:
Thanks!
Rusty.
Sure. Avi - do you want me to resubmit the kvm and qemu patches?
You mean the virtio and qemu patches. That's up to their maintainers
(Rusty and Anthony).
--
error compiling committee.c: too many arguments to
On Thu, 3 Dec 2009 08:28:38 pm Avi Kivity wrote:
On 12/03/2009 10:42 AM, Avishay Traeger1 wrote:
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
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
On 12/03/2009 10:42 AM, Avishay Traeger1 wrote:
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
