From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "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: [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO
Date: Thu, 7 Jul 2016 17:58:46 +0200 [thread overview]
Message-ID: <cover.1467895623.git.pabeni@redhat.com> (raw)
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.
Paolo Abeni (4):
udp_offload: simplify error path
udp offload: allow GRO on 0 checksum packets
vxlan: remove gro_cell support
geneve: remove gro_cell support
drivers/net/geneve.c | 12 +-----------
drivers/net/vxlan.c | 9 ++-------
include/net/vxlan.h | 1 -
net/ipv4/udp_offload.c | 12 +++++++-----
4 files changed, 10 insertions(+), 24 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-07-07 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 15:58 Paolo Abeni [this message]
2016-07-08 16:21 ` [PATCH net-next 0/4] net: cleanup for UDP tunnel's GRO Alexander Duyck
2016-07-08 20:17 ` Shmulik Ladkani
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=cover.1467895623.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=jesse@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).