From: Anthony Liguori <anthony@codemonkey.ws>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: alacrityvm-devel@lists.sourceforge.net,
alacrityvm-users@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org
Subject: Re: AlacrityVM numbers updated for 31-rc4
Date: Wed, 12 Aug 2009 18:05:31 -0500 [thread overview]
Message-ID: <4A834ABB.4010801@codemonkey.ws> (raw)
In-Reply-To: <4A83296B.3080606@gmail.com>
Gregory Haskins wrote:
> I re-ran the numbers on 10GE against the actual alacrityvm v0.1 release
> available in git on kernel.org.
>
> I tried to include the newly announced "vhost" driver (Michael Tsirkin)
> for virtio acceleration, but ran into issues getting the patches to apply.
>
> For now, this includes native, virtio-u (virtio-userspace), and venet
> all running on 31-rc4. If I can resolve the issue with Michaels
> patches, I will add "virtio-k" (virtio-kernel) to the mix as well. For
> now, here are the results for 1500mtu:
>
> native: 7388Mb/s, 29.8us rtt (33505 tps udp-rr)
> venet: 3654Mb/s, 56.8us rtt (17600 tps udp-rr)
> virtio-u: 1955Mb/s, 4016.0us rtt ( 249 tps udp-rr)
>
Just FYI, the numbers quoted are wrong for virtio-u. Greg's machine
didn't have high res timers enabled in the kernel. He'll post newer
numbers later but they're much better than these (venet is still ahead
though).
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-12 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:43 AlacrityVM numbers updated for 31-rc4 Gregory Haskins
2009-08-12 21:33 ` Javier Guerra
2009-08-12 22:05 ` Michael S. Zick
2009-08-12 23:05 ` Anthony Liguori [this message]
2009-08-12 23:21 ` Gregory Haskins
2009-08-13 12:05 ` Gregory Haskins
2009-08-14 19:50 ` Gregory Haskins
2009-08-17 11:06 ` Michael S. Tsirkin
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=4A834ABB.4010801@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=alacrityvm-users@lists.sourceforge.net \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@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 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).