public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 2/4] Revert virtio tap hack
Date: Sat, 03 May 2008 23:03:47 -0500	[thread overview]
Message-ID: <481D35A3.5080508@codemonkey.ws> (raw)
In-Reply-To: <1209869233-17324-2-git-send-email-aliguori@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

Anthony Liguori wrote:
> While it has served us well, it is long overdue that we eliminate the
> virtio-net tap hack.  It turns out that zero-copy has very little impact on
> performance.  The tap hack was gaining such a significant performance boost
> not because of zero-copy, but because it avoided dropping packets on receive
> which is apparently a significant problem with the tap implementation in QEMU.
>   

FWIW, attached is a pretty straight forward zero-copy patch.  What's 
interesting is that I see no change in throughput using this patch.  The 
CPU is pegged at 100% during the iperf run.  Since we're still using 
small MTUs, this isn't surprising.  Copying a 1500 byte packet that we 
have to bring into the cache anyway doesn't seem significant.  I think 
zero-copy will be more important with GSO though.

Regards,

Anthony Liguori

> Patches 3 and 4 in this series address the packet dropping issue and the net
> result is a 25% boost in RX performance even in the absence of zero-copy.
>
> Also worth mentioning, is that this makes merging virtio into upstream QEMU
> significantly easier.
>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>   


[-- Attachment #2: net-tap-zero-copy.patch --]
[-- Type: application/mbox, Size: 5499 bytes --]

[-- Attachment #3: Type: text/plain, Size: 320 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

[-- Attachment #4: Type: text/plain, Size: 158 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  reply	other threads:[~2008-05-04  4:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04  2:47 [PATCH 1/4] Only select once per-main_loop iteration Anthony Liguori
2008-05-04  2:47 ` [PATCH 2/4] Revert virtio tap hack Anthony Liguori
2008-05-04  4:03   ` Anthony Liguori [this message]
2008-05-04  8:01     ` Avi Kivity
2008-05-04  2:47 ` [PATCH 3/4] Make virtio-net can_receive more accurate Anthony Liguori
2008-05-04  2:47 ` [PATCH 4/4] Stop dropping so many RX packets in tap Anthony Liguori
2008-05-04 13:03 ` [PATCH 1/4] Only select once per-main_loop iteration Avi Kivity

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=481D35A3.5080508@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=mtosatti@redhat.com \
    /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