public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 2/4] Revert virtio tap hack
Date: Sun, 04 May 2008 11:01:07 +0300	[thread overview]
Message-ID: <481D6D43.6040703@qumranet.com> (raw)
In-Reply-To: <481D35A3.5080508@codemonkey.ws>

Anthony Liguori wrote:
> 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.

Zero copy is important when the guest is zero copy, and when we are not 
doing any extra copying on the host.  This doesn't fit the way we benchmark.

I expect zero copy to show improvements on things like apachebench  
(with a file size > 50K) with an external client.  The improvements will 
also show up on SMP, where the likelihood of the copy happening on the 
wrong cpu increase.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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

  reply	other threads:[~2008-05-04  8:01 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
2008-05-04  8:01     ` Avi Kivity [this message]
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=481D6D43.6040703@qumranet.com \
    --to=avi@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --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