DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: 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>
Cc: <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/2] net/mlx5: improvements to link status handling
Date: Fri, 30 Oct 2026 18:28:41 +0100	[thread overview]
Message-ID: <20261030172843.2304296-1-dsosnowski@nvidia.com> (raw)
In-Reply-To: <20261026160400.1290443-1-dsosnowski@nvidia.com>

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.

Dariusz Sosnowski (2):
  net/mlx5: fix link status query
  net/mlx5: move to polling for LSC interrupts

 .mailmap                                 |   1 +
 drivers/common/mlx5/linux/mlx5_nl.c      |  29 ---
 drivers/common/mlx5/linux/mlx5_nl.h      |   2 -
 drivers/net/mlx5/linux/meson.build       |   1 +
 drivers/net/mlx5/linux/mlx5_ethdev_os.c  | 147 ++++--------
 drivers/net/mlx5/linux/mlx5_lsc_intr.c   | 294 +++++++++++++++++++++++
 drivers/net/mlx5/linux/mlx5_os.c         |  23 --
 drivers/net/mlx5/mlx5.c                  |   7 -
 drivers/net/mlx5/mlx5.h                  |   4 +-
 drivers/net/mlx5/mlx5_lsc_intr.h         |  13 +
 drivers/net/mlx5/mlx5_trigger.c          |  20 +-
 drivers/net/mlx5/windows/meson.build     |   1 +
 drivers/net/mlx5/windows/mlx5_lsc_intr.c |  20 ++
 13 files changed, 385 insertions(+), 177 deletions(-)
 create mode 100644 drivers/net/mlx5/linux/mlx5_lsc_intr.c
 create mode 100644 drivers/net/mlx5/mlx5_lsc_intr.h
 create mode 100644 drivers/net/mlx5/windows/mlx5_lsc_intr.c

--
2.43.0


  parent reply	other threads:[~2026-10-30 17:29 UTC|newest]

Thread overview: 8+ 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 ` Dariusz Sosnowski [this message]
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

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=20261030172843.2304296-1-dsosnowski@nvidia.com \
    --to=dsosnowski@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stephen@networkplumber.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