From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
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>,
Didier Pallard <didier.pallard@6wind.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Francesco Santoro <francesco.santoro@6wind.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix min and max MTU reporting
Date: Mon, 18 Aug 2025 09:27:57 +0300 [thread overview]
Message-ID: <48b66c31-04a9-424d-84de-12d1cc8b2525@nvidia.com> (raw)
In-Reply-To: <20250716102546.1118749-1-dsosnowski@nvidia.com>
Hi,
On 16/07/2025 1:25 PM, Dariusz Sosnowski wrote:
> mlx5 PMD used hardcoded and incorrect values when reporting
> maximum MTU and maximum Rx packet length through rte_eth_dev_info_get().
>
> This patch adds support for querying OS for minimum and maximum
> allowed MTU values. Maximum Rx packet length is then calculated
> based on these values.
>
> On Linux, these values are queried through netlink,
> using IFLA_MIN_MTU and IFLA_MAX_MTU attributes added in Linux 4.18.
>
> Windows API unfortunately does not expose minimum and maximum
> allowed MTU values. In this case, fallback hardcoded values
> (working on currently supported HW) will be used.
>
> Bugzilla ID: 1719
> Fixes: e60fbd5b24fc ("mlx5: add device configure/start/stop")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-08-18 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:25 Dariusz Sosnowski
2025-08-18 6:27 ` 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=48b66c31-04a9-424d-84de-12d1cc8b2525@nvidia.com \
--to=rasland@nvidia.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=didier.pallard@6wind.com \
--cc=dsosnowski@nvidia.com \
--cc=francesco.santoro@6wind.com \
--cc=matan@nvidia.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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;
as well as URLs for NNTP newsgroup(s).