From: Stephen Hemminger <stephen@networkplumber.org>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: 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>, <dev@dpdk.org>
Subject: Re: [PATCH v2 0/2] net/mlx5: improvements to link status handling
Date: Mon, 2 Nov 2026 09:07:44 +0100 [thread overview]
Message-ID: <20261102090744.06c8be14@stephen-xps.local> (raw)
In-Reply-To: <20261030172843.2304296-1-dsosnowski@nvidia.com>
On Fri, 30 Oct 2026 18:28:41 +0100
Dariusz Sosnowski <dsosnowski@nvidia.com> wrote:
> This series is a result of splitting patch:
> https://patches.dpdk.org/project/dpdk/patch/20261026160400.1290443-1-dsosnowski@nvidia.com/
>
> Patch 1 - Fix for mlx5 link update function to query current link carrier status,
> bypassing the delay introduced by linkwatch in Linux kernel.
>
> Patch 2 - Move to link status polling, in place of relying on netlink events
> which can be delayed by linkwatch for up to 1s.
Instead of polling is there a way to get the lsc directly from devx or ibv
on mlx5? That would work around the issue and avoid the overhead.
Long term, it would be good if kernel had sysctl to set linkwatch per interface
but it doesn't
prev parent reply other threads:[~2026-11-02 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 16:04 [PATCH] net/mlx5: move to polling for LSC interrupts Dariusz Sosnowski
2026-10-26 17:03 ` Stephen Hemminger
2026-10-29 17:21 ` Dariusz Sosnowski
2026-10-26 17:13 ` Stephen Hemminger
2026-10-29 17:19 ` Dariusz Sosnowski
2026-10-30 17:28 ` [PATCH v2 0/2] net/mlx5: improvements to link status handling Dariusz Sosnowski
2026-10-30 17:28 ` [PATCH v2 1/2] net/mlx5: fix link status query Dariusz Sosnowski
2026-10-30 17:28 ` [PATCH v2 2/2] net/mlx5: move to polling for LSC interrupts Dariusz Sosnowski
2026-11-02 8:07 ` Stephen Hemminger [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=20261102090744.06c8be14@stephen-xps.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--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