From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: "David S . Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Cc: shmulik.ladkani@ravellosystems.com,
Eric Dumazet <edumazet@google.com>,
shmulik.ladkani@gmail.com,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Florian Westphal <fw@strlen.de>
Subject: [PATCH 0/2] net: Consider fragmentation of udp tunneled skbs in 'ip_finish_output_gso'
Date: Mon, 18 Jul 2016 14:49:32 +0300 [thread overview]
Message-ID: <1468842574-1243-1-git-send-email-shmulik.ladkani@gmail.com> (raw)
Currently IP fragmentation of GSO segments that exceed dst mtu is
considered only in the ipv4 forwarding case.
There are cases where GSO skbs that are bridged and then udp-tunneled
may have gso_size exceeding the egress device mtu.
It makes sense to fragment them, as in the non GSOed code path.
The exact cases where this behavior is needed is described and addressed
in the 2nd patch.
Shmulik Ladkani (2):
net/ipv4: Introduce IPSKB_FRAG_SEGS bit to inet_skb_parm.flags
net: ip_finish_output_gso: If skb_gso_network_seglen exceeds MTU,
allow segmentation for local udp tunneled skbs
include/net/ip.h | 1 +
net/ipv4/ip_forward.c | 2 +-
net/ipv4/ip_output.c | 6 ++++--
net/ipv4/ip_tunnel_core.c | 9 +++++++++
net/ipv4/ipmr.c | 2 +-
5 files changed, 16 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2016-07-18 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:49 Shmulik Ladkani [this message]
2016-07-18 11:49 ` [PATCH 1/2] net/ipv4: Introduce IPSKB_FRAG_SEGS bit to inet_skb_parm.flags Shmulik Ladkani
2016-07-19 7:42 ` Hannes Frederic Sowa
2016-07-18 11:49 ` [PATCH 2/2] net: ip_finish_output_gso: If skb_gso_network_seglen exceeds MTU, allow segmentation for local udp tunneled skbs Shmulik Ladkani
2016-07-19 7:48 ` Hannes Frederic Sowa
2016-07-18 12:08 ` [PATCH 0/2] net: Consider fragmentation of udp tunneled skbs in 'ip_finish_output_gso' Shmulik Ladkani
2016-07-19 23:40 ` 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=1468842574-1243-1-git-send-email-shmulik.ladkani@gmail.com \
--to=shmulik.ladkani@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@ravellosystems.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).