From: Raslan Darawsheh <rasland@nvidia.com>
To: Shani Peretz <shperetz@nvidia.com>, dev@dpdk.org
Cc: dsosnowski@nvidia.com, a.schollmeyer@syseleven.de,
stable@dpdk.org, Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Xueming Li <xuemingl@nvidia.com>
Subject: Re: [PATCH v2] net/mlx5: allow MTU mismatch for running shared Rx queues
Date: Sun, 8 Feb 2026 16:37:22 +0200 [thread overview]
Message-ID: <d1bf307d-c0c8-4490-a878-085f4c60bea1@nvidia.com> (raw)
In-Reply-To: <20260129081323.4713-1-shperetz@nvidia.com>
Hi,
On 29/01/2026 10:13 AM, Shani Peretz wrote:
> Previously, mlx5_shared_rxq_match() rejected any MTU mismatch between
> a port and the shared RX queue, even when the queue hardware was already
> running. This caused failures when hot-adding representors after runtime
> MTU changes (new port has default MTU=1500, but running queue was created
> with MTU=9000). It also prevented proper port reconfiguration scenarios.
>
> The fix allows MTU mismatches when rxq_ctrl->obj != NULL (queue is
> running), since runtime MTU changes via rte_eth_dev_set_mtu() only update
> software bookkeeping without recreating hardware resources. Stopped queues
> still enforce MTU matching to trigger proper reconfiguration.
>
> This patch also removes the redundant priv->mtu field and uses
> dev->data->mtu consistently for MTU tracking throughout the driver.
>
> Fixes: 4414eb800708 ("net/mlx5: store MTU at Rx queue allocation time")
> Fixes: 09c2555303be ("net/mlx5: support shared Rx queue")
> Cc: a.schollmeyer@syseleven.de
> Cc: stable@dpdk.org
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-02-08 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 7:39 [PATCH] net/mlx5: update stored Rx queue MTU when port MTU changes Shani Peretz
2025-11-18 9:52 ` Adrian Schollmeyer
2026-01-29 8:13 ` [PATCH v2] net/mlx5: allow MTU mismatch for running shared Rx queues Shani Peretz
2026-02-08 14:37 ` Raslan Darawsheh [this message]
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=d1bf307d-c0c8-4490-a878-085f4c60bea1@nvidia.com \
--to=rasland@nvidia.com \
--cc=a.schollmeyer@syseleven.de \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@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