From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
Paolo Abeni <pabeni@redhat.com>
Cc: Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jesse Gross <jesse@kernel.org>, Tom Herbert <tom@herbertland.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Jiri Benc <jbenc@redhat.com>
Subject: Re: [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO
Date: Fri, 8 Jul 2016 23:17:34 +0300 [thread overview]
Message-ID: <20160708231734.6258c00b@halley> (raw)
In-Reply-To: <CAKgT0UegKDuP0KHJ+zE1yDTwxxBjtvhESE3WFhTg65UX+CNL0A@mail.gmail.com>
On Fri, 8 Jul 2016 09:21:40 -0700 Alexander Duyck <alexander.duyck@gmail.com> wrote:
> On Thu, Jul 7, 2016 at 8:58 AM, Paolo Abeni <pabeni@redhat.com> wrote:
> > With udp tunnel offload in place, the kernel can do GRO for some udp tunnels
> > at the ingress device level. Currently both the geneve and the vxlan drivers
> > implement an additional GRO aggregation point via gro_cells.
> > The latter takes effect for tunnels using zero checksum udp packets, which are
> > currently explicitly not aggregated by the udp offload layer.
> >
> > This patch series adapts the udp tunnel offload to process also zero checksum
> > udp packets, if the tunnel's socket allow it. Aggregation, if possible is always
> > performed at the ingress device level.
> >
> > Then the gro_cells hooks, in both vxlan and geneve driver are removed.
>
> I think removing the gro_cells hooks may be taking things one step too far.
+1
> I get that there is an impression that it is redundant but there are a
> number of paths that could lead to VXLAN or GENEVE frames being
> received that are not aggregated via GRO.
There's the case where the vxlan/geneve datagrams get IP fragmented, and
IP frags are not GROed.
GRO aggregation at the vxlan/geneve level is beneficial for this case.
Regards,
Shmulik
next prev parent reply other threads:[~2016-07-08 20:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 15:58 [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO Paolo Abeni
2016-07-08 16:21 ` Alexander Duyck
2016-07-08 20:17 ` Shmulik Ladkani [this message]
2016-07-08 20:57 ` Hannes Frederic Sowa
2016-07-08 21:19 ` Shmulik Ladkani
2016-07-08 21:40 ` Hannes Frederic Sowa
2016-07-08 21:27 ` Alexander Duyck
2016-07-08 21:51 ` Hannes Frederic Sowa
2016-07-08 22:11 ` Alexander Duyck
2016-07-08 23:04 ` Hannes Frederic Sowa
2016-07-09 1:27 ` Alexander Duyck
2016-07-09 15:18 ` Shmulik Ladkani
2016-07-09 15:35 ` Hannes Frederic Sowa
2016-07-09 15:56 ` Shmulik Ladkani
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=20160708231734.6258c00b@halley \
--to=shmulik.ladkani@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).