From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, shm@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 00/11] net: Convert vrf to tx hook
Date: Sat, 10 Sep 2016 23:13:17 -0700 (PDT) [thread overview]
Message-ID: <20160910.231317.431318504608631938.davem@davemloft.net> (raw)
In-Reply-To: <1473534602-23602-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Sat, 10 Sep 2016 12:09:51 -0700
> The motivation for this series is that ICMP Unreachable - Fragmentation
> Needed packets are not handled properly for VRFs. Specifically, the
> FIB lookup in __ip_rt_update_pmtu fails so no nexthop exception is
> created with the reduced MTU. As a result connections stall if packets
> larger than the smallest MTU in the path are generated.
>
> While investigating that problem I also noticed that the MSS for all
> connections in a VRF is based on the VRF device's MTU and not the
> route the packets ultimately go through. VRF currently uses a dst
> to direct packets to the device. The first FIB lookup returns this dst
> and then the lookup in the VRF driver gets the actual output route. A
> side effect of this design is that the VRF dst is cached on sockets
> and then used for calculations like the MSS.
>
> This series fixes this problem by removing the hook in the FIB lookups
> that returns the dst pointing to the VRF device to the VRF and always
> doing the actual FIB lookup. This allows the real dst to be used
> throughout the stack (for example the MSS). Packets are diverted to
> the VRF device on Tx using an l3mdev hook in the output path similar to
> to what is done for Rx. The end result is a simpler implementation for
> VRF with fewer intrusions into the network stack and symmetrical packet
> handling for Rx and Tx paths.
...
Series applied, thanks David.
prev parent reply other threads:[~2016-09-11 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 19:09 [PATCH net-next v2 00/11] net: Convert vrf to tx hook David Ahern
2016-09-10 19:09 ` [PATCH net-next 01/11] net: flow: Add l3mdev flow update David Ahern
2016-09-10 19:09 ` [PATCH net-next 02/11] net: l3mdev: Add hook to output path David Ahern
2016-09-10 19:09 ` [PATCH net-next 03/11] net: l3mdev: Allow the l3mdev to be a loopback David Ahern
2016-09-10 19:09 ` [PATCH net-next 04/11] net: vrf: Flip IPv4 output path from FIB lookup hook to out hook David Ahern
2016-09-10 19:09 ` [PATCH net-next 05/11] net: vrf: Flip IPv6 " David Ahern
2016-09-10 19:09 ` [PATCH net-next 06/11] net: l3mdev: remove redundant calls David Ahern
2016-11-07 10:13 ` Lorenzo Colitti
2016-11-07 15:48 ` David Ahern
2016-09-10 19:09 ` [PATCH net-next 07/11] net: ipv4: Remove l3mdev_get_saddr David Ahern
2016-09-10 19:09 ` [PATCH net-next 08/11] net: ipv6: Remove l3mdev_get_saddr6 David Ahern
2016-09-10 19:10 ` [PATCH net-next 09/11] net: l3mdev: Remove l3mdev_fib_oif David Ahern
2016-09-10 19:10 ` [PATCH net-next 10/11] net: l3mdev: remove get_rtable method David Ahern
2016-09-10 19:10 ` [PATCH net-next 11/11] net: flow: Remove FLOWI_FLAG_L3MDEV_SRC flag David Ahern
2016-09-11 6:13 ` David Miller [this message]
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=20160910.231317.431318504608631938.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=shm@cumulusnetworks.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).