All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@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 16:34:45 +0300	[thread overview]
Message-ID: <20090825133445.GB13949@redhat.com> (raw)
In-Reply-To: <4A93E235.5040008@codemonkey.ws>

On Tue, Aug 25, 2009 at 08:08:05AM -0500, 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.

The idea is trivial enough to be sure the interface is sufficient:
we point kernel at used buffer at address X, and
copy stuff from there to guest buffer, then signal guest.
I'll post a code snippet to show how it's done if you like.

> Once it goes into the upstream
> kernel, we need to have backwards compatibility code in QEMU forever
> to  support that kernel version.

Don't worry: kernel needs to handle old userspace as well, and neither I
nor Rusty want to have a compatibility mess in kernel.

> Regards,
>
> Anthony Liguori

  reply	other threads:[~2009-08-25 13:37 UTC|newest]

Thread overview: 33+ 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  4:14     ` Avi Kivity
2009-08-25  6:46       ` Michael S. Tsirkin
2009-08-25  6:46       ` Michael S. Tsirkin
2009-08-25 13:08         ` Anthony Liguori
2009-08-25 13:08         ` Anthony Liguori
2009-08-25 13:34           ` Michael S. Tsirkin [this message]
2009-08-25 13:34           ` Michael S. Tsirkin
2009-08-25 13:45           ` Michael S. Tsirkin
2009-08-25 13:45           ` Michael S. Tsirkin
2009-08-25 15:57           ` Avi Kivity
2009-08-25 15:57           ` Avi Kivity
2009-08-25 12:34       ` Arnd Bergmann
2009-08-25 12:34       ` Arnd Bergmann
2009-08-26  7:34         ` Rusty Russell
2009-08-26  7:34         ` Rusty Russell
2009-08-26  8:14           ` Michael S. Tsirkin
2009-08-26  8:14           ` Michael S. Tsirkin
2009-08-27 16:00           ` 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 14:02         ` Michael S. Tsirkin
2009-08-25 13:06       ` Anthony Liguori
2009-08-25 13:24       ` Anthony Liguori
2009-08-25 13:24       ` Anthony Liguori
2009-08-25 13:43         ` Michael S. Tsirkin
2009-08-25 13:43         ` Michael S. Tsirkin
2009-08-25  6:44     ` Michael S. Tsirkin
2009-08-25  2:22   ` Anthony Liguori
2009-08-24 21:21 ` 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=20090825133445.GB13949@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.