DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: [PATCH 0/5] net/mlx5: some counter fixes
Date: Mon, 31 Oct 2022 18:08:19 +0200	[thread overview]
Message-ID: <20221031160824.330200-1-michaelba@nvidia.com> (raw)

Some fixes for HW/SW steering counters.

Michael Baum (5):
  net/mlx5: fix race condition in counter pool resizing
  net/mlx5: fix accessing the wrong counter
  net/mlx5: fix missing counter elements copies in r2r cases
  net/mlx5: add assertions in counter get/put
  net/mlx5: assert for enough space in counter rings

 drivers/net/mlx5/mlx5.c            |  28 ++++++-
 drivers/net/mlx5/mlx5.h            |   7 +-
 drivers/net/mlx5/mlx5_flow.c       |  24 +++---
 drivers/net/mlx5/mlx5_flow_dv.c    |  53 +++----------
 drivers/net/mlx5/mlx5_flow_hw.c    |   2 +-
 drivers/net/mlx5/mlx5_flow_verbs.c |  23 ++----
 drivers/net/mlx5/mlx5_hws_cnt.c    |  25 +++---
 drivers/net/mlx5/mlx5_hws_cnt.h    | 117 ++++++++++++++++-------------
 8 files changed, 131 insertions(+), 148 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-10-31 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 16:08 Michael Baum [this message]
2022-10-31 16:08 ` [PATCH 1/5] net/mlx5: fix race condition in counter pool resizing Michael Baum
2022-10-31 16:08 ` [PATCH 2/5] net/mlx5: fix accessing the wrong counter Michael Baum
2022-10-31 16:08 ` [PATCH 3/5] net/mlx5: fix missing counter elements copies in r2r cases Michael Baum
2022-10-31 16:08 ` [PATCH 4/5] net/mlx5: add assertions in counter get/put Michael Baum
2022-10-31 16:08 ` [PATCH 5/5] net/mlx5: assert for enough space in counter rings Michael Baum
2022-11-03 11:40 ` [PATCH 0/5] net/mlx5: some counter fixes 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=20221031160824.330200-1-michaelba@nvidia.com \
    --to=michaelba@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@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;
as well as URLs for NNTP newsgroup(s).