[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+h21hrf_FbnGYt1f_7Nqom1ab7CGMVGHpuje3O7t2kxazFPtQ@mail.gmail.com>
Date: Thu, 26 Mar 2020 14:34:13 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Ido Schimmel <idosch@...sch.org>
Cc: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
murali.policharla@...adcom.com,
Stephen Hemminger <stephen@...workplumber.org>,
Jiri Pirko <jiri@...nulli.us>,
Jakub Kicinski <kuba@...nel.org>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 net-next 10/10] net: bridge: implement
auto-normalization of MTU for hardware datapath
On Thu, 26 Mar 2020 at 13:54, Ido Schimmel <idosch@...sch.org> wrote:
>
> On Thu, Mar 26, 2020 at 01:44:51PM +0200, Vladimir Oltean wrote:
> > On Thu, 26 Mar 2020 at 13:35, Ido Schimmel <idosch@...sch.org> wrote:
> > >
> > > Also, I think that having the kernel change MTU
> > > of port A following MTU change of port B is a bit surprising and not
> > > intuitive.
> > >
> >
> > It already changes the MTU of br0, this just goes along the same path.
>
> Yea, but this is an established behavior already. And it applies
> regardless if the data path is offloaded or not, unlike this change.
>
I don't understand the 'established behavior' argument.
And I need to make a correction regarding the fact that it applies
regardless of whether the data path is offloaded or not.
If the data path is offloaded, it applies, sure, but it has no effect.
That is my issue with it.
Regards,
-Vladimir
Powered by blists - more mailing lists