public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Andy Ross <andy-DKCljQvcl/LNLxjTenLetw@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [announce] KVM/NET, paravirtual network device
Date: Thu, 11 Jan 2007 19:49:49 +0200	[thread overview]
Message-ID: <45A678BD.3020401@qumranet.com> (raw)
In-Reply-To: <45A67653.9000406-DKCljQvcl/LNLxjTenLetw@public.gmane.org>

Andy Ross wrote:
> Avi Kivity wrote:
>  > Ingo Molnar wrote:
>  > >   | Qemu via RTL-8029 emulation            :    2.84 MB/sec |
>  > >   | KVM via RTL-8029 emulation             :    7.41 MB/sec |
>  > >   | KVM-para via KVM/NET device (mtu=1500) :  303.35 MB/sec |
>  >
>  > That's about a 5000% improvement :)
>  >
>  > Amazing, both the bandwidth results and the speed in which it was
>  > reached.  I'm really at a loss for words.
>
> Is maybe a better question to ask what it is that makes the Qemu
> hardware emulation so slow?
>   

To send a packet through ne2k, you need about 44 pio writes. at ~10us 
per pio write, that's about 2k packets/sec, or 3MB/sec.  RTL8029 is 
about twice as fast.

A pv interface can send multiple packets per hypercall.  Working 
backward from Ingo's numbers, 300 MB/sec = 200k packets/sec = 2 
packets/hypercall.  Or perhaps his hardware is faster and he does 1 
packet/hypercall.  Or maybe I need to take the memcpy time into account 
at this bandwidth :)

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-01-11 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11  0:10 [announce] KVM/NET, paravirtual network device Ingo Molnar
     [not found] ` <20070111001010.GA28779-X9Un+BFzKDI@public.gmane.org>
2007-01-11  1:27   ` Rusty Russell
     [not found]     ` <1168478834.19646.230.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-11  1:38       ` Ingo Molnar
2007-01-11  9:57       ` Dor Laor
2007-01-11  8:21   ` Avi Kivity
     [not found]     ` <45A5F382.7050207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-11 17:39       ` Andy Ross
     [not found]         ` <45A67653.9000406-DKCljQvcl/LNLxjTenLetw@public.gmane.org>
2007-01-11 17:49           ` Avi Kivity [this message]

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=45A678BD.3020401@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=andy-DKCljQvcl/LNLxjTenLetw@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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