From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@nvidia.com>
Subject: [PATCH v3 0/2] net/mlx5: fix indirect RSS reference counting
Date: Wed, 24 Nov 2021 11:40:28 +0200 [thread overview]
Message-ID: <20211124094030.3360057-1-dkozlyuk@nvidia.com> (raw)
In-Reply-To: <20211123223159.3324247-1-dkozlyuk@nvidia.com>
v3:
* No changes, slipped when sending v2.
v2:
* Fix build with GCc on RHEL7 (CI).
* Fix RxQ leak when an indirect RSS had been created before the start
and then modified after the start (Matan).
Dmitry Kozlyuk (2):
net/mlx5: fix indirect RSS creation when port is stopped
net/mlx5: fix RxQ reference counting for indirect RSS
drivers/net/mlx5/mlx5_flow_dv.c | 9 +++-
drivers/net/mlx5/mlx5_rx.h | 6 ++-
drivers/net/mlx5/mlx5_rxq.c | 85 ++++++++++++++++++++-------------
3 files changed, 64 insertions(+), 36 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-11-24 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 22:31 [PATCH 0/2] next/mlx5: " Dmitry Kozlyuk
2021-11-23 22:31 ` [PATCH 1/2] net/mlx5: fix indirect RSS creation when port is stopped Dmitry Kozlyuk
2021-11-23 22:31 ` [PATCH 2/2] net/mlx5: fix RxQ reference counting for indirect RSS Dmitry Kozlyuk
2021-11-24 9:35 ` [PATCH 0/2] next/mlx5: fix indirect RSS reference counting Dmitry Kozlyuk
2021-11-24 9:35 ` [PATCH 1/2] net/mlx5: fix indirect RSS creation when port is stopped Dmitry Kozlyuk
2021-11-24 9:35 ` [PATCH 2/2] net/mlx5: fix RxQ reference counting for indirect RSS Dmitry Kozlyuk
2021-11-24 9:35 ` [PATCH v2 0/2] net/mlx5: fix indirect RSS reference counting Dmitry Kozlyuk
2021-11-24 9:35 ` [PATCH v2 1/2] net/mlx5: fix indirect RSS creation when port is stopped Dmitry Kozlyuk
2021-11-24 9:40 ` Dmitry Kozlyuk [this message]
2021-11-24 9:40 ` [PATCH v3 " Dmitry Kozlyuk
2021-11-24 9:40 ` [PATCH v3 2/2] net/mlx5: fix RxQ reference counting for indirect RSS Dmitry Kozlyuk
2021-11-24 13:04 ` [PATCH v3 0/2] net/mlx5: fix indirect RSS reference counting Raslan Darawsheh
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=20211124094030.3360057-1-dkozlyuk@nvidia.com \
--to=dkozlyuk@nvidia.com \
--cc=dev@dpdk.org \
--cc=rasland@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;
as well as URLs for NNTP newsgroup(s).