From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Balachandar <bala1486@gmail.com>
Cc: Sridhar Samudrala <samudrala.sridhar@gmail.com>, kvm@vger.kernel.org
Subject: Re: Virtio network performance poorer than emulated e1000
Date: Fri, 23 Jul 2010 09:11:23 +0200 [thread overview]
Message-ID: <4C49409B.5000505@redhat.com> (raw)
In-Reply-To: <AANLkTimS6XVWgxJS0YIJfnQOy_f0-WRExbdkkyMyGMJ1@mail.gmail.com>
On 07/23/10 03:31, Balachandar wrote:
> On Thu, Jul 22, 2010 at 8:18 PM, Sridhar Samudrala
> I tried this one also but not much improvement. Actually i get a some
> improvement if i disabled the tx timeout timer in the virtio_net.h in
> qemu-kvm. I read that with vhost the data flow path differs from
> normal operation. So is the timeout applicable when we use vhost
> also? Actually i dont see any improvement with vhost. I am just
> wondering what am i missing? The thing that worries me is that
> emulated nic offers much greater performance than virtio with vhost.
> So i feel i am doing something wrong but unable to find it.
Could you try measuring something meaningful instead of ping please?
netperf or some other benchmark?
Jes
next prev parent reply other threads:[~2010-07-23 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 23:53 Virtio network performance poorer than emulated e1000 Balachandar
2010-07-23 0:18 ` Sridhar Samudrala
2010-07-23 1:31 ` Balachandar
2010-07-23 7:11 ` Jes Sorensen [this message]
2010-07-24 15:04 ` Balachandar
2010-07-26 8:26 ` Jes Sorensen
2010-07-26 13:44 ` Michael Tokarev
2010-07-26 14:39 ` Balachandar
-- strict thread matches above, loose matches on Subject: below --
2010-07-22 20:13 Balachandar
2010-07-22 21:28 ` Freddie Cash
2010-07-23 13:37 ` Sebastian Hetze
[not found] ` <20100723133731.32ED2B0016@mail.linux-ag.de>
2010-07-23 14:47 ` Balachandar
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=4C49409B.5000505@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=bala1486@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=samudrala.sridhar@gmail.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 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.