From: Erwan Velu <e.velu@criteo.com>
To: Brett Creeley <bcreeley@amd.com>, Erwan Velu <erwanaliasr1@gmail.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 iwl-net] i40e: Prevent setting MTU if greater than MFS
Date: Thu, 14 Mar 2024 18:10:52 +0100 [thread overview]
Message-ID: <c0ccaef6-44eb-4851-b336-cdb06647e1d2@criteo.com> (raw)
In-Reply-To: <4e203331-62f7-44e7-acd9-f684c30662de@amd.com>
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,
next prev parent reply other threads:[~2024-03-14 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:07 [PATCH v4 iwl-net] i40e: Prevent setting MTU if greater than MFS Erwan Velu
2024-03-14 16:10 ` Brett Creeley
2024-03-14 17:10 ` Erwan Velu [this message]
2024-03-14 17:55 ` Brett Creeley
2024-03-14 18:04 ` Erwan Velu
2024-03-14 20:31 ` Tony Nguyen
2024-03-15 9:17 ` Erwan Velu
2024-03-15 16:19 ` Brett Creeley
2024-03-18 17:45 ` Simon Horman
2024-03-19 10:26 ` Sunil Kovvuri Goutham
[not found] ` <d33b98de-dfc0-445e-bdd7-0ae76d050ed4@criteo.com>
2024-03-19 12:20 ` Simon Horman
2024-03-19 13:33 ` Erwan Velu
2024-04-19 14:26 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
[not found] ` <CAL2JzuxraP5xCxt4_EK3zbz9kyAyxJFuEadtq4zHsdMjR5PGTw@mail.gmail.com>
2024-04-22 13:19 ` Pucha, HimasekharX Reddy
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=c0ccaef6-44eb-4851-b336-cdb06647e1d2@criteo.com \
--to=e.velu@criteo.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bcreeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=erwanaliasr1@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).