From: Ramu Ramamurthy <sramamur@linux.vnet.ibm.com>
To: Jesse Gross <jesse@nicira.com>
Cc: Tom Herbert <tom@herbertland.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Jerry Chu <hkchu@google.com>, Netdev <netdev@vger.kernel.org>,
Davem <davem@davemloft.net>, J Kidambi <jkidambi@us.ibm.com>,
manand@us.ibm.com
Subject: Re: [PATCH] - gre: add eth_p_teb gro-handler for OVS with gre tunnels
Date: Mon, 12 Oct 2015 17:49:13 -0700 [thread overview]
Message-ID: <603f81c3c472530ca28263a78576130f@imap.linux.ibm.com> (raw)
In-Reply-To: <CAEP_g=9YKT0hcTBmg2AcJb8+uQCVNd1YHEPoT+M3LA4k-cPFPw@mail.gmail.com>
On 2015-10-12 16:47, Jesse Gross wrote:
> On Mon, Oct 12, 2015 at 3:26 PM, Ramu Ramamurthy
> <sramamur@linux.vnet.ibm.com> wrote:
>>
>> Problem:
>> --------
>>
>> When using OVS with GRE tunnels, and GRO is enabled on the nic,
>> We find that GRO doesnt really take effect. As a result, TCP stream
>> performance on a 10G nic is around 2-3Gbps.
>>
>> Root Cause:
>> -----------
>>
>> The protocol field set in GRE (by OVS) is ETH_P_TEB.
>> The code in gre_gro_receive() (gre_offload.c) calls
>> gro_find_receive_by_type() to determine a gro handler for the
>> ETH_P_TEB protocol. However, no such protocol is registered
>> at the device layer (only ETH_P_IP, ETH_P_IPV6, and mpls related
>> protocols are registered). Hence, GRO is skipped.
>
> Why doesn't this work?
>
> commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
> Author: Jesse Gross <jesse@nicira.com>
> Date: Tue Dec 30 19:10:15 2014 -0800
>
> net: Add Transparent Ethernet Bridging GRO support.
>
> Currently the only tunnel protocol that supports GRO with
> encapsulated
> Ethernet is VXLAN. This pulls out the Ethernet code into a proper
> layer
> so that it can be used by other tunnel protocols such as GRE and
> Geneve.
>
> Signed-off-by: Jesse Gross <jesse@nicira.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
Thanks, your commit fixes the same problem in the 4.x kernels. So the
patch above is redundant.
We are using the 3.x kernels and thats why I could not see your fix in
my tests.
We/distros would need to backport your fix to 3.x for us to consume it.
next prev parent reply other threads:[~2015-10-13 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 22:26 [PATCH] - gre: add eth_p_teb gro-handler for OVS with gre tunnels Ramu Ramamurthy
2015-10-12 23:47 ` Jesse Gross
2015-10-13 0:49 ` Ramu Ramamurthy [this message]
2015-10-13 1:54 ` 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=603f81c3c472530ca28263a78576130f@imap.linux.ibm.com \
--to=sramamur@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hkchu@google.com \
--cc=jesse@nicira.com \
--cc=jkidambi@us.ibm.com \
--cc=manand@us.ibm.com \
--cc=netdev@vger.kernel.org \
--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