[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c0ccaef6-44eb-4851-b336-cdb06647e1d2@criteo.com>
Date: Thu, 14 Mar 2024 18:10:52 +0100
From: Erwan Velu <e.velu@...teo.com>
To: Brett Creeley <bcreeley@....com>, Erwan Velu <erwanaliasr1@...il.com>
Cc: Jesse Brandeburg <jesse.brandeburg@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 iwl-net] i40e: Prevent setting MTU if greater than MFS
Le 14/03/2024 à 17:10, Brett Creeley a écrit :
[...]
> If this is how the max_mtu is determined, does it make sense to set this
> before registering the netdev, i.e. netdev->max_mtu in
> i40e_config_netdev()?
The absolute max is properly set but I think that's only true if we
ensure the value of the MFS.
So if with another patch to set the MFS to the right value when asking a
bigger MTU, having this value makes sense this is the absolute max for
this device.
Erwan,
Powered by blists - more mailing lists