[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210203103739.563c13c2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 3 Feb 2021 10:37:39 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"Rybak, Eryk Roch" <eryk.roch.rybak@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"Topel, Bjorn" <bjorn.topel@...el.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@...el.com>,
"Karlsson, Magnus" <magnus.karlsson@...el.com>,
"Bhandare, KiranX" <kiranx.bhandare@...el.com>
Subject: Re: [PATCH net-next 6/6] i40e: Log error for oversized MTU on
device
On Wed, 3 Feb 2021 09:14:24 +0000 Loktionov, Aleksandr wrote:
> Good day Jakub
Please don't top post.
> We want to be user friendly to help users troubleshoot faster.
> Only dmesg message can have template parameters so we can provide
> exact acceptable maximum bytes. Can you could you take this into
> account?
I was making the same exact point when adding the message for NFP
years ago and it was shot down :)
Today upstream is getting close to removing the page-per-packet
requirement, so this will hopefully become irrelevant soon. Maciej
should have the details on that, he seems to be keeping up the most
with upstream in ITP.
Powered by blists - more mailing lists