public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Kohei Enju <kohei@enjuk.jp>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>, <kohei.enju@gmail.com>
Subject: Re: [PATCH v1 iwl-net] iavf: fix netdev->max_mtu to respect actual hardware limit
Date: Tue, 10 Feb 2026 17:37:23 +0100	[thread overview]
Message-ID: <c48f08ad-b402-4cfe-a362-4cb0c3a7801f@intel.com> (raw)
In-Reply-To: <20260210155810.135577-1-kohei@enjuk.jp>

From: Kohei Enju <kohei@enjuk.jp>
Date: Tue, 10 Feb 2026 15:57:14 +0000

> iavf sets LIBIE_MAX_MTU as netdev->max_mtu, ignoring vf_res->max_mtu
> from PF [1]. This allows setting an MTU beyond the actual hardware
> limit, causing TX queue timeouts [2].
> 
> Set correct netdev->max_mtu using vf_res->max_mtu from the PF.
> 
> Note that currently PF drivers such as ice/i40e set the frame size in
> vf_res->max_mtu, not MTU. Convert vf_res->max_mtu to MTU before setting
> netdev->max_mtu.
> 
> [1]
>  # ip -j -d link show $DEV | jq '.[0].max_mtu'
>  16356
> 
> [2]
>  iavf 0000:00:05.0 enp0s5: NETDEV WATCHDOG: CPU: 1: transmit queue 0 timed out 5692 ms
>  iavf 0000:00:05.0 enp0s5: NIC Link is Up Speed is 10 Gbps Full Duplex
>  iavf 0000:00:05.0 enp0s5: NETDEV WATCHDOG: CPU: 6: transmit queue 3 timed out 5312 ms
>  iavf 0000:00:05.0 enp0s5: NIC Link is Up Speed is 10 Gbps Full Duplex
>  ...
> 
> Fixes: 5fa4caff59f2 ("iavf: switch to Page Pool")
> Signed-off-by: Kohei Enju <kohei@enjuk.jp>

Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>

Although I'm not sure the 'Fixes:' tag is correct. Was vs_res->max_mtu
accounted before switching to Page Pool? If so, then yes, my fault.
Otherwise, this issue is older than libie.
I'm asking as IIRC before I did set max_mtu to the libie definition,
there was a hardcoded value already.

> ---
> Ideally we may fix ice/i40e to set max MTU (not frame size) in
> vf_res->max_mtu on the PF side, but this would break PF/VF API
> compatibility between different kernel versions and would need
> modifications on code that treats vf_res->max_mtu as the frame size.
> 
> If it's acceptable to change the PF/VF API, this patch would be simply:
>     netdev->max_mtu = min_not_zero(adapter->vf_res->max_mtu, 
>                                    LIBIE_MAX_MTU);
> ---
>  drivers/net/ethernet/intel/iavf/iavf_main.c | 17 ++++++++++++++++-
>  1 file changed, 16 insertions(+), 1 deletion(-)
Thanks,
Olek

  reply	other threads:[~2026-02-10 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 15:57 [PATCH v1 iwl-net] iavf: fix netdev->max_mtu to respect actual hardware limit Kohei Enju
2026-02-10 16:37 ` Alexander Lobakin [this message]
2026-02-10 17:05   ` [PATCH v1 iwl-net] iavf: fix netdev->max_mtu to respect actual Kohei Enju
2026-02-12 18:15     ` Simon Horman
2026-02-23 15:56   ` [Intel-wired-lan] [PATCH v1 iwl-net] iavf: fix netdev->max_mtu to respect actual hardware limit Romanowski, Rafal

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=c48f08ad-b402-4cfe-a362-4cb0c3a7801f@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kohei.enju@gmail.com \
    --cc=kohei@enjuk.jp \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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