virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: dor.laor@qumranet.com
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] virtio_net tx performance fix
Date: Mon, 28 Jan 2008 22:09:48 -0600	[thread overview]
Message-ID: <479EA70C.1080108@us.ibm.com> (raw)
In-Reply-To: <1201535954.2457.11.camel@localhost.localdomain>

Dor Laor wrote:
> On Mon, 2008-01-28 at 09:32 -0600, Anthony Liguori wrote:
>   
>> Hi Dor,
>>
>> How are you measuring performance?  The numbers I've gotten with netperf 
>> before and after your patch are:
>>
>> tx - 647.27mbit
>> rx - 89.22
>>
>> tx - 27.82
>> rx - 79.93
>>
>>     
>
> I've been testing with iperf (patched with Ingo's fix).
> I also tested tcp/udp (udp tx is only 550Mbps with the patch, w/o it's
> only 220Mbps)
>   

FWIW, I repeated with an scp test copying a 200mb file from /dev/shm on 
the host to the guest and vice versa.  rx performance is around 3-4 
MB/sec.  Without your patch, tx performance is around 40 MB/sec whereas 
with your patch performance is around 30 MB/sec.  So the tx drop is 
definitely exaggerated by netperf.  I'm definitely not seeing an 
increase in throughput though.

Could you try a similar scp test?  What sort of networking setup are you 
using?

My guest kernel and host kernel are both 2.6.24 (from Ubuntu Hardy).

Regards,

Anthony Liguori

  parent reply	other threads:[~2008-01-29  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1201479224.3047.37.camel@localhost.localdomain>
2008-01-28 15:32 ` [PATCH] virtio_net tx performance fix Anthony Liguori
     [not found] ` <479DF5A8.8050103@us.ibm.com>
2008-01-28 15:59   ` Dor Laor
     [not found]   ` <1201535954.2457.11.camel@localhost.localdomain>
2008-01-28 16:11     ` Anthony Liguori
2008-01-29  4:09     ` Anthony Liguori [this message]
2008-01-28  0:13 Dor Laor

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=479EA70C.1080108@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=dor.laor@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).