From: Avi Kivity <avi@redhat.com>
To: Avishay Traeger1 <AVISHAY@il.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] virtio-blk: add max sectors feature
Date: Mon, 30 Nov 2009 16:18:55 +0200 [thread overview]
Message-ID: <4B13D44F.8060303@redhat.com> (raw)
In-Reply-To: <OF6170BA26.9C2A4C26-ONC2257679.005FFE86-C2257679.006A083E@il.ibm.com>
On 11/25/2009 09:18 PM, Avishay Traeger1 wrote:
> 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
> (kvm) and user-space (qemu-kvm) changes. I appreciate any comments.
>
This should be started by a patch to http://ozlabs.org/~rusty/virtio-spec/.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-11-30 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 19:18 [Qemu-devel] [PATCH] virtio-blk: add max sectors feature Avishay Traeger1
2009-11-30 14:18 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B13D44F.8060303@redhat.com \
--to=avi@redhat.com \
--cc=AVISHAY@il.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).