From: Jacob Keller <jacob.e.keller@intel.com>
To: Tariq Toukan <tariqt@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Gal Pressman <gal@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Cosmin Ratiu <cratiu@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>
Subject: Re: [PATCH net-next V2 1/2] net/mlx5e: RX, Drop oversized packets in non-linear mode
Date: Wed, 4 Feb 2026 14:55:56 -0800 [thread overview]
Message-ID: <9d3d6128-41fb-4f72-acca-3bb9d6798e3c@intel.com> (raw)
In-Reply-To: <20260203072130.1710255-2-tariqt@nvidia.com>
On 2/2/2026 11:21 PM, Tariq Toukan wrote:
> From: Dragos Tatulea <dtatulea@nvidia.com>
>
> Currently the driver has an inconsistent behaviour between modes when it
> comes to oversized packets that are not dropped through the physical MTU
> check in HW. This can happen for Multi Host configurations where each
> port has a different MTU.
>
> Current behavior:
>
> 1) Striding RQ in linear mode drops the packet in SW and counts it
> with oversize_pkts_sw_drop.
>
> 2) Striding RQ in non-linear mode allows it like a normal packet.
>
> 3) Legacy RQ can't receive oversized packets by design:
> the RX WQE uses MTU sized packet buffers.
>
> This inconsistency is not a violation of the netdev policy [1]
> but it is better to be consistent across modes.
>
> This patch aligns (2) with (1) and (3). One exception is added for
> LRO: don't drop the oversized packet if it is an LRO packet.
>
The doc also says that the preference is to drop packets, so this makes
sense.
> As now rq->hw_mtu always needs to be updated during the MTU change flow,
> drop the reset avoidance optimization from mlx5e_change_mtu().
>
> Extract the CQE LRO segments reading into a helper function as it
> is used twice now.
>
> [1] Documentation/networking/netdevices.rst#L205
>
> Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
> ---
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2026-02-04 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 7:21 [PATCH net-next V2 0/2] net/mlx5e: RX datapath enhancements Tariq Toukan
2026-02-03 7:21 ` [PATCH net-next V2 1/2] net/mlx5e: RX, Drop oversized packets in non-linear mode Tariq Toukan
2026-02-04 22:55 ` Jacob Keller [this message]
2026-02-03 7:21 ` [PATCH net-next V2 2/2] net/mlx5e: SHAMPO, Improve allocation recovery Tariq Toukan
2026-02-04 22:57 ` Jacob Keller
2026-02-05 5:30 ` [PATCH net-next V2 0/2] net/mlx5e: RX datapath enhancements patchwork-bot+netdevbpf
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=9d3d6128-41fb-4f72-acca-3bb9d6798e3c@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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