From: Andrew Theurer <habanero@linux.vnet.ibm.com>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: rusty@rustcorp.com.au, davem@davemloft.net, mst@redhat.com,
eric.dumazet@gmail.com, arnd@arndb.de, netdev@vger.kernel.org,
horms@verge.net.au, avi@redhat.com, anthony@codemonkey.ws,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] [RFC] Implement multiqueue (RX & TX) virtio-net
Date: Thu, 03 Mar 2011 13:01:24 -0600 [thread overview]
Message-ID: <1299178884.13202.50.camel@localhost.localdomain> (raw)
In-Reply-To: <20110228063427.24908.63561.sendpatchset@krkumar2.in.ibm.com>
On Mon, 2011-02-28 at 12:04 +0530, Krishna Kumar wrote:
> This patch series is a continuation of an earlier one that
> implemented guest MQ TX functionality. This new patchset
> implements both RX and TX MQ. Qemu changes are not being
> included at this time solely to aid in easier review.
> Compatibility testing with old/new combinations of qemu/guest
> and vhost was done without any issues.
>
> Some early TCP/UDP test results are at the bottom of this
> post, I plan to submit more test results in the coming days.
>
> Please review and provide feedback on what can improve.
>
> Thanks!
>
> Signed-off-by: Krishna Kumar <krkumar2@in.ibm.com>
> ---
>
>
> Test configuration:
> Host: 8 Intel Xeon, 8 GB memory
> Guest: 4 cpus, 2 GB memory
>
> Each test case runs for 60 secs, results below are average over
> two runs. Bandwidth numbers are in gbps. I have used default
> netperf, and no testing/system tuning other than taskset each
> vhost to 0xf (cpus 0-3). Comparison is testing original kernel
> vs new kernel with #txqs=8 ("#" refers to number of netperf
> sessions).
>
> _______________________________________________________________________
> TCP: Guest -> Local Host (TCP_STREAM)
> TCP: Local Host -> Guest (TCP_MAERTS)
> UDP: Local Host -> Guest (UDP_STREAM)
Any reason why the tests don't include a guest-to-guest on same host, or
on different hosts? Seems like those would be a lot more common that
guest-to/from-localhost.
Thanks,
-Andrew
next prev parent reply other threads:[~2011-03-03 19:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 6:34 [PATCH 0/3] [RFC] Implement multiqueue (RX & TX) virtio-net Krishna Kumar
2011-02-28 6:34 ` [PATCH 1/3] [RFC] Change virtqueue structure Krishna Kumar
2011-02-28 6:34 ` [PATCH 2/3] [RFC] Changes for MQ virtio-net Krishna Kumar
2011-02-28 9:43 ` Michael S. Tsirkin
2011-03-01 16:02 ` Krishna Kumar2
2011-03-02 10:06 ` Michael S. Tsirkin
2011-03-08 15:32 ` Krishna Kumar2
2011-03-08 15:41 ` Michael S. Tsirkin
2011-03-09 6:01 ` Krishna Kumar2
2011-02-28 6:34 ` [PATCH 3/3] [RFC] Changes for MQ vhost Krishna Kumar
2011-02-28 10:04 ` Michael S. Tsirkin
2011-03-01 16:04 ` Krishna Kumar2
2011-03-02 10:11 ` Michael S. Tsirkin
2011-02-28 7:35 ` [PATCH 0/3] [RFC] Implement multiqueue (RX & TX) virtio-net Michael S. Tsirkin
2011-02-28 15:35 ` Krishna Kumar2
2011-03-03 19:01 ` Andrew Theurer [this message]
2011-03-04 12:22 ` Krishna Kumar2
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=1299178884.13202.50.camel@localhost.localdomain \
--to=habanero@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).