kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	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 09:46:04 +0300	[thread overview]
Message-ID: <20090825064604.GB10429@redhat.com> (raw)
In-Reply-To: <4A936525.5030300@redhat.com>

On Tue, Aug 25, 2009 at 07:14:29AM +0300, Avi Kivity wrote:
> On 08/25/2009 05:22 AM, Anthony Liguori wrote:
>>
>> I think 2.6.32 is pushing it. 
>
> 2.6.32 is pushing it, but we need to push it.
>
>> I think some time is needed to flush out the userspace interface.  In  
>> particular, I don't think Mark's comments have been adequately  
>> addressed.  If a version were merged without GSO support, some  
>> mechanism to do feature detection would be needed in the userspace API. 
>> 
>
> I don't see any point  in merging without gso (unless it beats userspace  
> with gso, which I don't think will happen).  In any case we'll need  
> feature negotiation.
>
>> I think this is likely going to be needed regardless.  I also think  
>> the tap compatibility suggestion would simplify the consumption of  
>> this in userspace.
>
> What about veth pairs?
>
>> I'd like some time to look at get_state/set_state ioctl()s along with  
>> dirty tracking support.  It's a much better model for live migration  
>> IMHO.
>
> 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?

>> I think so more thorough benchmarking would be good too.  In  
>> particular, netperf/iperf runs would be nice.
>
> Definitely.
>
> -- 
> I have a truly marvellous patch that fixes the bug which this
> signature is too narrow to contain.

  reply	other threads:[~2009-08-25  6:47 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 [this message]
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
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=20090825064604.GB10429@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 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).