From: <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Michael Baum <michaelba@oss.nvidia.com>
Subject: [dpdk-dev] [PATCH 0/3] mlx5: fix performance degradation
Date: Wed, 3 Nov 2021 12:17:04 +0200 [thread overview]
Message-ID: <20211103101707.1418097-1-michaelba@nvidia.com> (raw)
From: Michael Baum <michaelba@oss.nvidia.com>
Due to sharing MR management in common, Tx performance is dropped.
This series back improves performance in a variety of ways.
Michael Baum (3):
common/mlx5: fix MR search non inline function
common/mlx5: fix redundant parameter in search MR function
common/mlx5: make MR managmant port-agnostic for MP
drivers/common/mlx5/mlx5_common.c | 10 +-
drivers/common/mlx5/mlx5_common.h | 7 -
drivers/common/mlx5/mlx5_common_mp.c | 38 ++--
drivers/common/mlx5/mlx5_common_mp.h | 44 +++--
drivers/common/mlx5/mlx5_common_mr.c | 210 ++++++-----------------
drivers/common/mlx5/mlx5_common_mr.h | 70 ++++++--
drivers/common/mlx5/version.map | 4 +-
drivers/compress/mlx5/mlx5_compress.c | 4 +-
drivers/crypto/mlx5/mlx5_crypto.c | 24 ++-
drivers/net/mlx5/linux/mlx5_mp_os.c | 39 ++---
drivers/net/mlx5/mlx5_rx.h | 10 +-
drivers/net/mlx5/mlx5_rxq.c | 6 +-
drivers/net/mlx5/mlx5_trigger.c | 4 +-
drivers/net/mlx5/mlx5_tx.h | 27 +--
drivers/net/mlx5/mlx5_txq.c | 3 +-
drivers/regex/mlx5/mlx5_regex_control.c | 3 +-
drivers/regex/mlx5/mlx5_regex_fastpath.c | 29 +---
17 files changed, 204 insertions(+), 328 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-03 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 10:17 michaelba [this message]
2021-11-03 10:17 ` [dpdk-dev] [PATCH 1/3] common/mlx5: fix MR search non inline function michaelba
2021-11-03 10:17 ` [dpdk-dev] [PATCH 2/3] common/mlx5: fix redundant parameter in search MR function michaelba
2021-11-03 10:17 ` [dpdk-dev] [PATCH 3/3] common/mlx5: make MR managmant port-agnostic for MP michaelba
2021-11-07 13:17 ` [dpdk-dev] [PATCH 0/3] mlx5: fix performance degradation Thomas Monjalon
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=20211103101707.1418097-1-michaelba@nvidia.com \
--to=michaelba@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@oss.nvidia.com \
--cc=thomas@monjalon.net \
/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).