From: Rick Jones <rick.jones2@hp.com>
To: Ramu Ramamurthy <sramamur@linux.vnet.ibm.com>
Cc: Tom Herbert <tom@herbertland.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH RFC net-next] vxlan: GRO support at tunnel layer
Date: Mon, 29 Jun 2015 08:45:57 -0700 [thread overview]
Message-ID: <55916835.8030809@hp.com> (raw)
In-Reply-To: <df94e5b8a0ed7a9146063908e3001ef3@imap.linux.ibm.com>
On 06/28/2015 10:20 AM, Ramu Ramamurthy wrote:
> Rick, in your test, are you seeing gro becoming effective on the
> vxlan interface with the 82599ES nic ? (ie, tcpdump on the vxlan
> interface shows larger frames than the mtu of that interface, and
> kernel trace shows vxlan_gro_receive() being hit)
>
> Throughputs of 5.5 Gbps (or the improved 7Gbs) leads me to suspect
> that gro is still not effective in your test on the vxlan interface
> with the 82588ES nic - Because, when vxlan gro became effective with
> the patch I suggested earlier, I could see throughput of ~8.5 Gbps on
> that nic.
For the 5.X gbit/s test, where I am not getting GRO, I am seeing 1398
byte data packets when I trace vxlan0.
For the other direction, at 7ish Gbit/s I am seeing 64XXX byte packets
on vxlan0, with the occasional 25XXX byte packet. If I disable gro on
that receiving vxlan0 interface, the throughput is more like 4.X Gbit/s
happy benchmarking,
rick
next prev parent reply other threads:[~2015-06-29 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 23:09 [PATCH RFC net-next] vxlan: GRO support at tunnel layer Tom Herbert
2015-06-27 0:46 ` Rick Jones
2015-06-28 17:20 ` Ramu Ramamurthy
2015-06-28 21:31 ` Tom Herbert
2015-06-29 15:40 ` Rick Jones
2015-06-29 15:45 ` Rick Jones [this message]
2015-06-29 20:04 ` Rick Jones
2015-06-30 1:06 ` Jesse Gross
2015-06-30 5:06 ` Eric Dumazet
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=55916835.8030809@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sramamur@linux.vnet.ibm.com \
--cc=tom@herbertland.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 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).