From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: <stable@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>
Subject: [PATCH 20.11 0/3] net/mlx5: fix link state detection
Date: Fri, 11 Mar 2022 09:49:30 +0200 [thread overview]
Message-ID: <20220311074933.1194679-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_nl.c | 105 +++++++++++++++++++++++-
drivers/common/mlx5/linux/mlx5_nl.h | 8 +-
drivers/common/mlx5/version.map | 3 +
drivers/net/mlx5/linux/mlx5_ethdev_os.c | 64 ++++++++++++---
drivers/net/mlx5/linux/mlx5_os.c | 66 ++++++++++++---
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 ++-
drivers/vdpa/mlx5/mlx5_vdpa.c | 2 +-
10 files changed, 238 insertions(+), 28 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-11 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:49 Dmitry Kozlyuk [this message]
2022-03-11 7:49 ` [PATCH 20.11 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-03-11 7:49 ` [PATCH 20.11 2/3] net/mlx5: fix link status change detection Dmitry Kozlyuk
2022-03-11 7:49 ` [PATCH 20.11 3/3] net/mlx5: fix initial link status detection Dmitry Kozlyuk
2022-03-11 12:19 ` [PATCH 20.11 0/3] net/mlx5: fix link state detection Luca Boccassi
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=20220311074933.1194679-1-dkozlyuk@nvidia.com \
--to=dkozlyuk@nvidia.com \
--cc=bluca@debian.org \
--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).