From: Bing Zhao <bingz@nvidia.com>
To: <viacheslavo@nvidia.com>, <matan@nvidia.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <dsosnowski@nvidia.com>,
<suanmingm@nvidia.com>, <rasland@nvidia.com>
Subject: [PATCH v5 0/5] Use consecutive Tx queues' memory
Date: Sun, 29 Jun 2025 20:22:58 +0300 [thread overview]
Message-ID: <20250629172303.72049-1-bingz@nvidia.com> (raw)
In-Reply-To: <20250629170709.69960-1x-bingz@nvidia.com>
This patchset will move all the mlx5 Tx queues memory to a
consecutive memory area. All the WQEBBs will be allocated based
on the offset of this memory area.
---
v2:
1. add a new fix for legacy code of WQE calculation
2. fix the style
v3:
1. change the devarg and add description.
2. reorganize the code with different commits order.
v4:
1. fix building failure on Windows and OSes with different compilers
2. update the rst
3. addressing comments and fix bugs
v5:
1. solve one size_t coverity warning
---
Bing Zhao (5):
net/mlx5: add new devarg for Tx queue consecutive memory
net/mlx5: calculate the memory length for all Tx queues
net/mlx5: allocate and release unique resources for Tx queues
net/mlx5: pass the information in Tx queue start
net/mlx5: use consecutive memory for Tx queue creation
doc/guides/nics/mlx5.rst | 25 ++++
drivers/common/mlx5/mlx5_common_devx.c | 160 +++++++++++++++--------
drivers/common/mlx5/mlx5_common_devx.h | 2 +
drivers/common/mlx5/mlx5_devx_cmds.h | 10 ++
drivers/net/mlx5/mlx5.c | 36 +++++
drivers/net/mlx5/mlx5.h | 15 ++-
drivers/net/mlx5/mlx5_devx.c | 26 +++-
drivers/net/mlx5/mlx5_trigger.c | 173 +++++++++++++++++++------
drivers/net/mlx5/mlx5_tx.h | 2 +
drivers/net/mlx5/mlx5_txq.c | 67 +++++++++-
10 files changed, 418 insertions(+), 98 deletions(-)
--
2.34.1
next parent reply other threads:[~2025-06-29 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250629170709.69960-1x-bingz@nvidia.com>
2025-06-29 17:22 ` Bing Zhao [this message]
2025-06-29 17:22 ` [PATCH v5 1/5] net/mlx5: add new devarg for Tx queue consecutive memory Bing Zhao
2025-06-29 17:23 ` [PATCH v5 2/5] net/mlx5: calculate the memory length for all Tx queues Bing Zhao
2025-06-29 17:23 ` [PATCH v5 3/5] net/mlx5: allocate and release unique resources for " Bing Zhao
2025-06-29 17:23 ` [PATCH v5 4/5] net/mlx5: pass the information in Tx queue start Bing Zhao
2025-06-29 17:23 ` [PATCH v5 5/5] net/mlx5: use consecutive memory for Tx queue creation Bing Zhao
2025-06-29 18:11 ` [PATCH v5 0/5] Use consecutive Tx queues' memory 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=20250629172303.72049-1-bingz@nvidia.com \
--to=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--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).