All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	virtualization@lists.linux-foundation.org,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] qemu-kvm: vhost net support
Date: Thu, 20 Aug 2009 20:24:37 +0300	[thread overview]
Message-ID: <4A8D86D5.4090809@redhat.com> (raw)
In-Reply-To: <20090820170028.GA8908@redhat.com>

On 08/20/2009 08:00 PM, Michael S. Tsirkin wrote:
>
> Surprisingly, I seem to get better-than-userspace throughput with this
> benchmark as well.  Here's a test run locally, host-to-guest,
> over a veth link:
>
> vhost:
> [root@qus19 ~]# ping -c 1000000 -f -q 11.0.0.4
> PING 11.0.0.4 (11.0.0.4) 56(84) bytes of data.
>
> --- 11.0.0.4 ping statistics ---
> 1000000 packets transmitted, 1000000 received, 0% packet loss, time 10230ms
> rtt min/avg/max/mdev = 0.005/0.006/0.035/0.000 ms, ipg/ewma 0.010/0.006 ms
>    

6 microseconds is very impressive for round-trip time.

> [root@qus19 ~]# ping -s 1024 -l 120 -c 1000000 -f -q 11.0.0.4
> PING 11.0.0.4 (11.0.0.4) 1024(1052) bytes of data.
>
> --- 11.0.0.4 ping statistics ---
> 1000000 packets transmitted, 1000000 received, 0% packet loss, time 11270ms
> rtt min/avg/max/mdev = 0.006/0.006/0.022/0.002 ms, pipe 120, ipg/ewma 0.011/0.007 ms
>
>    

That's only 100MB/sec, but understandable given the lack of interrupt 
mitigation.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-08-20 17:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 19:23 [PATCH 0/3] qemu-kvm: vhost net support Michael S. Tsirkin
2009-08-10 20:51 ` Anthony Liguori
2009-08-12 17:35   ` Michael S. Tsirkin
2009-08-19  8:11     ` Or Gerlitz
2009-08-19  8:11     ` Or Gerlitz
2009-08-20  7:19     ` Rusty Russell
2009-08-20  7:19     ` Rusty Russell
2009-08-20 13:41       ` Michael S. Tsirkin
2009-08-20 13:41       ` Michael S. Tsirkin
2009-08-20 17:00       ` Michael S. Tsirkin
2009-08-20 17:24         ` Avi Kivity [this message]
2009-08-20 17:49           ` Michael S. Tsirkin
2009-08-20 17:49           ` Michael S. Tsirkin
2009-08-20 17:24         ` Avi Kivity
2009-08-20 17:00       ` Michael S. Tsirkin
2009-08-12 17:35   ` Michael S. Tsirkin
2009-08-12 20:27 ` Gregory Haskins
2009-08-13  5:59   ` Michael S. Tsirkin
2009-08-13  5:59   ` Michael S. Tsirkin
2009-08-13 11:35     ` Gregory Haskins
2009-08-13 11:35     ` Gregory Haskins
2009-08-13 11:53       ` Michael S. Tsirkin
2009-08-13 11:53       ` Michael S. Tsirkin
2009-08-12 20:27 ` Gregory Haskins
  -- strict thread matches above, loose matches on Subject: below --
2009-08-10 19:23 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=4A8D86D5.4090809@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --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 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.