From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 19.11 0/3] net/mlx5: fix link state detection
Date: Fri, 11 Mar 2022 11:06:01 +0100 [thread overview]
Message-ID: <CAATJJ0+M_eXHqW6d3WNedYznd5eShNTo_XLm3EBpdKTLhTGNTA@mail.gmail.com> (raw)
In-Reply-To: <20220311080627.1195847-1-dkozlyuk@nvidia.com>
On Fri, Mar 11, 2022 at 9:06 AM Dmitry Kozlyuk <dkozlyuk@nvidia.com> wrote:
>
> [ 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
All three applied, thank you
> drivers/net/mlx5/mlx5.c | 59 +++++++++++++++---
> drivers/net/mlx5/mlx5.h | 10 ++-
> drivers/net/mlx5/mlx5_ethdev.c | 63 +++++++++++++++----
> drivers/net/mlx5/mlx5_nl.c | 107 +++++++++++++++++++++++++++++++-
> drivers/net/mlx5/mlx5_trigger.c | 12 +++-
> 5 files changed, 224 insertions(+), 27 deletions(-)
>
> --
> 2.25.1
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-03-11 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:06 Dmitry Kozlyuk
2022-03-11 8:06 ` [PATCH 19.11 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-03-11 8:06 ` [PATCH 19.11 2/3] net/mlx5: fix link status change detection Dmitry Kozlyuk
2022-03-11 8:06 ` [PATCH 19.11 3/3] net/mlx5: fix initial link status detection Dmitry Kozlyuk
2022-03-11 10:06 ` Christian Ehrhardt [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=CAATJJ0+M_eXHqW6d3WNedYznd5eShNTo_XLm3EBpdKTLhTGNTA@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=dkozlyuk@nvidia.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).