From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org, avi@redhat.com,
kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: vhost net: performance with ping benchmark
Date: Mon, 24 Aug 2009 21:22:47 -0500 [thread overview]
Message-ID: <4A934AF7.2090904@codemonkey.ws> (raw)
In-Reply-To: <20090824212137.GA9835@redhat.com>
Michael S. Tsirkin wrote:
> On Mon, Aug 24, 2009 at 11:12:41AM +0300, Michael S. Tsirkin wrote:
>
>> At Rusty's suggestion, I tested vhost base performance with ping.
>> Results below, and seem to be what you'd expect.
>>
>
> Rusty, any chance you could look at the code? Is it in reasonable
> shape? I think it makes sense to merge it through you. What do you
> think? One comment on file placement: I put files under a separate
> vhost directory to avoid confusion with virtio-net which runs in guest.
> Does this sound sane? Also, can a minimal version (without TSO, tap or
> any other features) be merged upstream first so that features can be
> added later? Or do we have to wait until it's more full featured?
> Finally, can it reasonably make 2.6.32, or you think it needs more time
> out of tree?
>
I think 2.6.32 is pushing 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 think this is likely going to be needed regardless. I
also think the tap compatibility suggestion would simplify the
consumption of this in userspace.
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.
I think so more thorough benchmarking would be good too. In particular,
netperf/iperf runs would be nice.
Regards,
Anthony Liguori
> Thanks very much,
>
>
next prev parent reply other threads:[~2009-08-25 2:22 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 [this message]
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
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=4A934AF7.2090904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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).