From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>,
dev@dpdk.org, matan@nvidia.com, viacheslavo@nvidia.com,
orika@nvidia.com, suanmingm@nvidia.com, thomas@monjalon.net
Cc: stable@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>
Subject: Re: [PATCH v2] net/mlx5: fix probe optimization race condition
Date: Tue, 2 Sep 2025 11:03:50 +0300 [thread overview]
Message-ID: <81366236-396a-417e-ae09-530b752bc550@nvidia.com> (raw)
In-Reply-To: <20250829053532.445865-1-rongweil@nvidia.com>
Hi,
On 29/08/2025 8:35 AM, Rongwei Liu wrote:
> With dedicated RDMA link monitor, there are two threads
> which can update the IB device port information.
>
> Add a new flag to avoid the race condition. Update should
> go through RDMA link monitor once ready.
>
> Current logic is:
> 1. Update all port information in probing thread.
> 2. Probe thread initiates the dedicated rdma monitor thread.
> Once ready, port information update will be handled by this thread.
> 3. Next probing won't trigger PMD port information update.
>
> No lock is required.
>
> Fixes: 51fb5c40c826 ("common/mlx5: optimize device probing")
> Cc: rongweil@nvidia.com
> Cc: stable@dpdk.org
> Signed-off-by: Rongwei Liu <rongweil@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-09-02 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 3:21 [PATCH v1] " Rongwei Liu
2025-08-28 4:40 ` Stephen Hemminger
2025-08-28 4:49 ` rongwei liu
2025-08-28 13:37 ` Thomas Monjalon
2025-08-29 5:35 ` [PATCH v2] " Rongwei Liu
2025-09-02 8:03 ` 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=81366236-396a-417e-ae09-530b752bc550@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--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).