From: Rick Jones <rick.jones2@hp.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next] virtio_net: add gro capability
Date: Mon, 03 Aug 2015 09:22:48 -0700 [thread overview]
Message-ID: <55BF9558.3020501@hp.com> (raw)
In-Reply-To: <20150803162529-mutt-send-email-mst@redhat.com>
On 08/03/2015 06:37 AM, Michael S. Tsirkin wrote:
> Ideally this needs to also be tested on non-vxlan configs with gro in
> host, to make sure this doesn't cause regressions.
Measured with the same instances on the same hardware and software,
taking a path through the stack (public rather than private IPs, with
Distributed Virtual Router (DVR) enabled) which gives them GRO:
Throughput
Min Median Average Max
4.2.0-rc3+_hostGRO 6713 8351 8232 9102
4.2.0-rc3+flush1k_hostGRO 6539 8267 8206 8982
As singletons, Mins and Maxes probably have rather high variability, I'd
focus on the Median and Average and those are within 1%.
Send Service Demand
Min Median Average Max
4.2.0-rc3+_hostGRO 0.332 0.496 0.490 0.651
4.2.0-rc3+flush1k_hostGRO 0.328 0.493 0.488 0.678
Receive Service Demand
Min Median Average Max
4.2.0-rc3+_hostGRO 0.386 0.469 0.485 0.677
4.2.0-rc3+flush1k_hostGRO 0.369 0.466 0.477 0.665
happy benchmarking,
rick
next prev parent reply other threads:[~2015-08-03 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 16:25 [PATCH net-next] virtio_net: add gro capability Eric Dumazet
2015-07-31 23:57 ` David Miller
2015-08-02 8:48 ` Michael S. Tsirkin
2015-08-03 13:37 ` Michael S. Tsirkin
2015-08-03 16:22 ` Rick Jones [this message]
2015-08-03 21:23 ` David Miller
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=55BF9558.3020501@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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).