From: Eric Dumazet <eric.dumazet@gmail.com>
To: Eran Ben Elisha <eranlinuxmellanox@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: Tariq Toukan <tariqt@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Eran Ben Elisha <eranbe@mellanox.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next] net: ipv6/gre: Add GRO support
Date: Mon, 2 Apr 2018 08:19:55 -0700 [thread overview]
Message-ID: <e6b0bbf7-559e-e86a-aaf7-c64b713dfaa8@gmail.com> (raw)
In-Reply-To: <CAKHjkjm8JE_N_v5HCmqokmzxmfYDd=T4cwqaBSRAXNezg-hNYg@mail.gmail.com>
On 04/02/2018 08:00 AM, Eran Ben Elisha wrote:
>>>> Seems good, but why isn't this handled directly in GRO native layer ?
>>> ip6_tunnel and ip6_gre do not share initialization flow functions (unlike ipv4).
>>> Changing the ipv6 init infrastructure should not be part of this
>>> patch. we prefer to keep this one minimal, simple and safe.
>>
>>
>>
>> Looking at gre_gro_receive() and gre_gro_complete() I could not see why they
>> could not be copied/pasted to IPv6.
>
> These functions to handle GRO over GRE are already assigned in
> gre_offload_init() (in net/ipv4/gre_offload.c under CONFIG_IPV6).
> However without initializing the gro_cells, the receive path will not
> go via napi_gro_receive path, but directly to netif_rx.
> So AFAIU, only gcells->cells was missing for gro_cells_receive to
> really go via GRO flow.
>
>>
>> Maybe give more details on the changelog, it is really not obvious.
> Hopefully the above filled this request.
>>
Not really :/
gro_cells_receive() is not really useful with native GRO, since packet is already
a GRO packet by the time it reaches ip_tunnel_rcv() or __ip6_tnl_rcv()
Sure, it might be usefull if native GRO (happening on eth0 if you prefer) did not
handle a particular encapsulation.
gro_cell was a work around before we extended GRO to be able to decap some tunnel headers.
It seems we have to extend this to also support GRE6.
next prev parent reply other threads:[~2018-04-02 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 13:17 [PATCH net-next] net: ipv6/gre: Add GRO support Tariq Toukan
2018-04-01 16:35 ` Eric Dumazet
2018-04-02 12:40 ` Eran Ben Elisha
2018-04-02 14:42 ` Eric Dumazet
2018-04-02 15:00 ` Eran Ben Elisha
2018-04-02 15:19 ` Eric Dumazet [this message]
2018-04-02 15:45 ` Tariq Toukan
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=e6b0bbf7-559e-e86a-aaf7-c64b713dfaa8@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eranbe@mellanox.com \
--cc=eranlinuxmellanox@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.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