From: Stefano Brivio <sbrivio@redhat.com>
To: Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
Kaustubh Pandey <quic_kapandey@quicinc.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<yoshfuji@linux-ipv6.org>, <kuba@kernel.org>,
<netdev@vger.kernel.org>,
Sean Tranchetti <quic_stranche@quicinc.com>
Subject: Re: [PATCH net v2 1/2] ipv6: Honor route mtu if it is within limit of dev mtu
Date: Tue, 14 Jun 2022 14:27:37 +0200 [thread overview]
Message-ID: <20220614142737.73fffc9d@elisabeth> (raw)
In-Reply-To: <1655182915-12897-2-git-send-email-quic_subashab@quicinc.com>
Hi Kaustubh,
On Mon, 13 Jun 2022 23:01:54 -0600
Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com> wrote:
> From: Kaustubh Pandey <quic_kapandey@quicinc.com>
>
> When netdevice MTU is increased via sysfs, NETDEV_CHANGEMTU is raised.
>
> addrconf_notify -> rt6_mtu_change -> rt6_mtu_change_route ->
> fib6_nh_mtu_change
>
> As part of handling NETDEV_CHANGEMTU notification we land up on a
> condition where if route mtu is less than dev mtu and route mtu equals
> ipv6_devconf mtu, route mtu gets updated.
>
> Due to this v6 traffic end up using wrong MTU then configured earlier.
I read this a few times but I still fail to understand what issue
you're actually fixing -- what makes this new MTU "wrong"?
The idea behind the original implementation is that, when an interface
MTU is administratively updated, we should allow PMTU updates, if the
old PMTU was matching the interface MTU, because the old MTU setting
might have been the one limiting the MTU on the whole path.
That is, if you lower the MTU on an interface, and then increase it
back, a permanently lower PMTU is somewhat unexpected. As far as I can
see, this behaviour persists with this patch, but:
> This commit fixes this by removing comparison with ipv6_devconf
> and updating route mtu only when it is greater than incoming dev mtu.
...I'm not sure what you really mean by "incoming dev mtu". Is it the
newly configured one?
--
Stefano
next prev parent reply other threads:[~2022-06-14 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 5:01 [PATCH net v2 0/2] net: ipv6: Update route MTU behavior Subash Abhinov Kasiviswanathan
2022-06-14 5:01 ` [PATCH net v2 1/2] ipv6: Honor route mtu if it is within limit of dev mtu Subash Abhinov Kasiviswanathan
2022-06-14 12:27 ` Stefano Brivio [this message]
2022-06-14 18:34 ` Subash Abhinov Kasiviswanathan (KS)
2022-06-16 0:35 ` Jakub Kicinski
2022-06-16 1:21 ` Maciej Żenczykowski
2022-06-16 5:36 ` Subash Abhinov Kasiviswanathan (KS)
2022-06-16 7:33 ` Maciej Żenczykowski
2022-06-16 16:42 ` Jakub Kicinski
2022-06-16 17:08 ` Maciej Żenczykowski
2022-06-16 13:39 ` Stefano Brivio
2022-06-14 5:01 ` [PATCH net v2 2/2] tools: selftests: Update tests for new IPv6 route MTU behavior Subash Abhinov Kasiviswanathan
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=20220614142737.73fffc9d@elisabeth \
--to=sbrivio@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quic_kapandey@quicinc.com \
--cc=quic_stranche@quicinc.com \
--cc=quic_subashab@quicinc.com \
--cc=yoshfuji@linux-ipv6.org \
/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).