patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: <stable@dpdk.org>
Cc: Kevin Traynor <ktraynor@redhat.com>
Subject: [PATCH 21.11 0/3] net/mlx5: fix link state detection
Date: Tue, 8 Mar 2022 17:10:41 +0200	[thread overview]
Message-ID: <20220308151044.1012413-1-dkozlyuk@nvidia.com> (raw)

[ backport of https://inbox.dpdk.org/dev/20220301121514.41497-1-dkozlyuk@nvidia.com ]

This patchset fixes two related issues:
* In rare occasions with any HW link state change to UP was missed.
* If a port was DOWN before startup, its netdev would come UP,
  but appear DOWN in DPDK (especially probable with ConnectX-4).

Dmitry Kozlyuk (3):
  common/mlx5: add Netlink event helpers
  net/mlx5: fix link status change detection
  net/mlx5: fix initial link status detection

 drivers/common/mlx5/linux/mlx5_common_os.c |   2 +-
 drivers/common/mlx5/linux/mlx5_nl.c        | 102 ++++++++++++++++++++-
 drivers/common/mlx5/linux/mlx5_nl.h        |   8 +-
 drivers/common/mlx5/version.map            |   2 +
 drivers/net/mlx5/linux/mlx5_ethdev_os.c    |  63 ++++++++++---
 drivers/net/mlx5/linux/mlx5_os.c           |  74 +++++++++++++--
 drivers/net/mlx5/linux/mlx5_vlan_os.c      |   2 +-
 drivers/net/mlx5/mlx5.c                    |   1 +
 drivers/net/mlx5/mlx5.h                    |   3 +
 drivers/net/mlx5/mlx5_trigger.c            |  12 ++-
 10 files changed, 241 insertions(+), 28 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-03-08 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 15:10 Dmitry Kozlyuk [this message]
2022-03-08 15:10 ` [PATCH 21.11 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-03-08 15:10 ` [PATCH 21.11 2/3] net/mlx5: fix link status change detection Dmitry Kozlyuk
2022-03-08 15:10 ` [PATCH 21.11 3/3] net/mlx5: fix initial link status detection Dmitry Kozlyuk
2022-03-10 12:19 ` [PATCH 21.11 0/3] net/mlx5: fix link state detection Kevin Traynor

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=20220308151044.1012413-1-dkozlyuk@nvidia.com \
    --to=dkozlyuk@nvidia.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    /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).