All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riccardo Veraldi <Riccardo.Veraldi@cnaf.infn.it>
To: Benjamin Schweikert <b.schweikert@googlemail.com>
Cc: kvm@vger.kernel.org, Andrea Chierici <andrea.chierici@cnaf.infn.it>
Subject: Re: Very bad Speed with Virtio-net
Date: Thu, 07 Jan 2010 12:21:56 +0100	[thread overview]
Message-ID: <4B45C3D4.8010800@cnaf.infn.it> (raw)
In-Reply-To: <4B45BCEA.1040709@googlemail.com>

I have similar results, like yours, using CentOS 5.4 x86_64
I do not think it is possible to gain more than this right now... or 
better I wish it could be possible

If you can get better result please let me know

Rick

Benjamin Schweikert wrote:
> Hello everybody,
> this is my first post on a mailing list, so i hope everything works fine.
>
> My host is a AMD X2 4850e with a 64bit Gentoo (unstable). I have 
> tested qemu-kvm 0.11, 0.12.x and the git version from the 6. jan.
> I created my own bridges, so i dont need the option from libvirt. I 
> bridged a 1 Gb lan card for my VMs. When I use the virtio net driver,
> i get something about 200-300 mbit form my desktop to one if my VMs. 
> If iI use the e1000 driver instead of the virtio I get about
> 500 - 600 mbit.
> I tested this with the following kernels:
> Host: 2.6.31.6, 2.6.32.1, 2.6.32.2
> Guests: 2.6.26, 2.6.30, 2.6.32 (debian)
> 2.6.32 (gentoo)
>
> Here is a default result, virtio vs. e1000:
>
> iperf -c 192.168.0.3 -w 512k -l 512k
> ------------------------------------------------------------
> Client connecting to 192.168.0.3, TCP port 5001
> TCP window size:   256 KByte (WARNING: requested   512 KByte)
> ------------------------------------------------------------
> [  3] local 192.168.0.2 port 52968 connected with 192.168.0.3 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [  3]  0.0-10.0 sec    438 MBytes    267 Mbits/sec
>
>
> iperf -c 192.168.0.3 -w 512k -l 512k
> ------------------------------------------------------------
> Client connecting to 192.168.0.3, TCP port 5001
> TCP window size:   256 KByte (WARNING: requested   512 KByte)
> ------------------------------------------------------------
> [  3] local 192.168.0.2 port 52995 connected with 192.168.0.3 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [  3]  0.0-10.0 sec    602 MBytes    505 Mbits/sec
>
> Any ideas what this could be? I attach a dmesg output of my host.
> Thx.
>
> Ben


  reply	other threads:[~2010-01-07 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 10:52 Very bad Speed with Virtio-net Benjamin Schweikert
2010-01-07 11:21 ` Riccardo Veraldi [this message]
2010-01-08 20:10   ` Thomas Fjellstrom

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=4B45C3D4.8010800@cnaf.infn.it \
    --to=riccardo.veraldi@cnaf.infn.it \
    --cc=andrea.chierici@cnaf.infn.it \
    --cc=b.schweikert@googlemail.com \
    --cc=kvm@vger.kernel.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.