From: Suanming Mou <suanmingm@nvidia.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/8] net/mlx5: make counter thread safe
Date: Tue, 20 Oct 2020 11:02:20 +0800 [thread overview]
Message-ID: <1603162949-150001-1-git-send-email-suanmingm@nvidia.com> (raw)
In-Reply-To: <1601984333-304464-1-git-send-email-suanmingm@nvidia.com>
The mlx5 PMD is going to support multiple-thread flow operations.
This patchset makes the counter action to be thread safe.
Suanming Mou (8):
net/mlx5: locate aging pools in the general container
net/mlx5: optimize shared counter memory
net/mlx5: remove single counter container
net/mlx5: synchronize flow counter pool creation
net/mlx5: make three level table thread safe
net/mlx5: make shared counters thread safe
net/mlx5: rename flow counter macro
net/mlx5: optimize counter extend memory
--
v2:
- Optimize the fallback non-batch counter memory.
- Add MLX5_ prefix to counter macro.
- Rebase on top of the latest code.
--
drivers/net/mlx5/linux/mlx5_os.c | 53 ++-
drivers/net/mlx5/mlx5.c | 51 ++-
drivers/net/mlx5/mlx5.h | 146 ++++----
drivers/net/mlx5/mlx5_flow.c | 183 ++++++----
drivers/net/mlx5/mlx5_flow.h | 1 +
drivers/net/mlx5/mlx5_flow_dv.c | 706 ++++++++++++++-----------------------
drivers/net/mlx5/mlx5_flow_verbs.c | 130 ++++---
drivers/net/mlx5/mlx5_utils.c | 191 ++++++++--
drivers/net/mlx5/mlx5_utils.h | 81 ++++-
9 files changed, 824 insertions(+), 718 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2020-10-20 3:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 11:38 [dpdk-dev] [PATCH 0/6] " Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 1/6] net/mlx5: locate aging pools in the general container Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 2/6] net/mlx5: optimize shared counter memory Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 3/6] net/mlx5: remove single counter container Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 4/6] net/mlx5: synchronize flow counter pool creation Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 5/6] net/mlx5: make three level table thread safe Suanming Mou
2020-10-06 11:38 ` [dpdk-dev] [PATCH 6/6] net/mlx5: make shared counters " Suanming Mou
2020-10-20 3:02 ` Suanming Mou [this message]
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 1/8] net/mlx5: locate aging pools in the general container Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 2/8] net/mlx5: optimize shared counter memory Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 3/8] net/mlx5: remove single counter container Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 4/8] net/mlx5: synchronize flow counter pool creation Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 5/8] net/mlx5: make three level table thread safe Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 6/8] net/mlx5: make shared counters " Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 7/8] net/mlx5: rename flow counter macro Suanming Mou
2020-10-20 3:02 ` [dpdk-dev] [PATCH v2 8/8] net/mlx5: optimize counter extend memory Suanming Mou
2020-10-20 22:59 ` [dpdk-dev] [PATCH v2 0/8] net/mlx5: make counter thread safe 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=1603162949-150001-1-git-send-email-suanmingm@nvidia.com \
--to=suanmingm@nvidia.com \
--cc=dev@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).