From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Neal Cardwell <ncardwell@google.com>, Pravin Shelar <pshelar@nicira.com>
Cc: alexander.duyck@gmail.com, netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
"H.K. Jerry Chu" <hkchu@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net] gre: Fix regression in gretap TSO support
Date: Thu, 30 Oct 2014 07:30:02 -0700 [thread overview]
Message-ID: <54524B6A.3000503@redhat.com> (raw)
In-Reply-To: <CADVnQykSY_Q3HL0T1uNO4iUheWTpTsLLF7gCnM4SbJyGp3x6Wg@mail.gmail.com>
On 10/30/2014 06:51 AM, Neal Cardwell wrote:
> On Thu, Oct 30, 2014 at 1:14 AM, Pravin Shelar <pshelar@nicira.com> wrote:
>> On Wed, Oct 29, 2014 at 8:26 PM, <alexander.duyck@gmail.com> wrote:
>>> From: Alexander Duyck <alexander.h.duyck@redhat.com>
>>>
>>> On recent kernels I found that TSO on gretap interfaces didn't work. After
>>> bisecting it I found that commit b884b1a4 had introduced a regression in
>>> which the Ethernet header was being included in the GRE header length.
>>>
>>> This change corrects that by basing the GRE header length on the inner mac
>>> header in the case of GRE tunnels using transparent Ethernet bridging, and
>>> uses the network header for all other GRE tunnel types.
>>>
>>> Fixes: b884b1a4 ("gre_offload: simplify GRE header length calculation in gre_gso_segment()")
> Hmm. There may be other protocols, either now or in the future, where
> we want to be able to have a mac header inside the GRE header, rather
> than a network header. AFAICT it would be safer to revert b884b1a4,
> and go back to the previous code (from c50cd357), where we parse the
> GRE header to figure out its length.
>
> neal
The change is consistent with how we handle this in other spots
throughout the kernel. If nothing else you can just search for
ETH_P_TEB and you will find multiple spots in the kernel where IP
tunnels differentiate between transparent Ethernet bridging and regular
IP in IP tunnels by checking for the protocol ETH_P_TEB.
Thanks,
Alex
next prev parent reply other threads:[~2014-10-30 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 3:26 [PATCH net] gre: Fix regression in gretap TSO support alexander.duyck
2014-10-30 5:14 ` Pravin Shelar
2014-10-30 13:51 ` Neal Cardwell
2014-10-30 14:30 ` Alexander Duyck [this message]
2014-10-30 15:00 ` Eric Dumazet
2014-10-30 15:05 ` Tom Herbert
2014-10-30 15:32 ` Tom Herbert
2014-10-30 15:32 ` Alexander Duyck
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=54524B6A.3000503@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkchu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.