From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: vhost net: performance with ping benchmark
Date: Tue, 25 Aug 2009 18:57:34 +0300 [thread overview]
Message-ID: <4A9409EE.3030906@redhat.com> (raw)
In-Reply-To: <4A93E235.5040008@codemonkey.ws>
On 08/25/2009 04:08 PM, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>>> My preference is ring proxying. Not we'll need ring proxying (or
>>> at least event proxying) for non-MSI guests.
>>
>> Exactly, that's what I meant earlier. That's enough, isn't it, Anthony?
>
> It is if we have a working implementation that demonstrates the
> userspace interface is sufficient. Once it goes into the upstream
> kernel, we need to have backwards compatibility code in QEMU forever
> to support that kernel version.
Not at all. We still have pure userspace support, so if we don't like
the first two versions of vhost, we can simply not support them. Of
course I'm not advocating merging something known bad or untested, just
pointing out that the cost of an error is not that bad.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-25 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090824081240.GA3415@redhat.com>
2009-08-24 21:21 ` vhost net: performance with ping benchmark Michael S. Tsirkin
2009-08-25 2:22 ` Anthony Liguori
2009-08-25 4:14 ` Avi Kivity
2009-08-25 6:46 ` Michael S. Tsirkin
2009-08-25 13:08 ` Anthony Liguori
2009-08-25 13:34 ` Michael S. Tsirkin
2009-08-25 13:45 ` Michael S. Tsirkin
2009-08-25 15:57 ` Avi Kivity [this message]
2009-08-25 12:34 ` Arnd Bergmann
2009-08-26 7:34 ` Rusty Russell
2009-08-26 8:14 ` Michael S. Tsirkin
2009-08-27 16:00 ` Michael S. Tsirkin
2009-08-25 13:06 ` Anthony Liguori
2009-08-25 14:02 ` Michael S. Tsirkin
2009-08-25 13:24 ` Anthony Liguori
2009-08-25 13:43 ` Michael S. Tsirkin
2009-08-25 6:44 ` Michael S. Tsirkin
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=4A9409EE.3030906@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).