From: Haifei Luo <haifeil@nvidia.com>
To: dev@dpdk.org
Cc: orika@nvidia.com, viacheslavo@nvidia.com, rasland@nvidia.com,
xuemingl@nvidia.com, haifeil@nvidia.com
Subject: [dpdk-dev] [PATCH v3 0/2] support single flow dump on MLX5 PMD
Date: Thu, 15 Apr 2021 14:19:22 +0300 [thread overview]
Message-ID: <1618485564-128533-1-git-send-email-haifeil@nvidia.com> (raw)
In-Reply-To: <1618384952-179763-1-git-send-email-haifeil@nvidia.com>
Dump information for all flows are supported and it is
useful to dump one flow.
Add single flow dump support on MLX5 PMD.
Modify API mlx5_flow_dev_dump to support.Modify mlx5_socket
since one extra arg flow_ptr is added.
The data structure sent to DPDK application from the utility triggering
the flow dumps should be packed and endianness must be specified.
The native host endianness can be used, all exchange happens within
the same host (we use sendmsg aux data and share the file handle,
remote approach is not applicable, no inter-host communication happens).
The message structure to dump one/all flow(s):
struct mlx5_flow_dump_req {
uint32_t port_id;
uint64_t flow_ptr;
} __rte_packed;
If flow_ptr is 0, all flows for the specified port will be dumped.
Depends-on: series=16367 ("single flow dump")
http://patchwork.dpdk.org/project/dpdk/list/?series=16367
V2: Rebase to fix apply patch failure.
V3: Fix commments. Modify data structures sent to DPDK application.
Haifei Luo (2):
common/mlx5: add mlx5 APIs for single flow dump feature
net/mlx5: add mlx5 APIs for single flow dump feature
drivers/common/mlx5/linux/meson.build | 6 +++--
drivers/common/mlx5/linux/mlx5_glue.c | 13 ++++++++++
drivers/common/mlx5/linux/mlx5_glue.h | 1 +
drivers/common/mlx5/mlx5_devx_cmds.c | 14 +++++++++++
drivers/common/mlx5/mlx5_devx_cmds.h | 2 ++
drivers/common/mlx5/version.map | 1 +
drivers/net/mlx5/linux/mlx5_os.h | 3 +++
drivers/net/mlx5/linux/mlx5_socket.c | 47 +++++++++++++++++++++++++++--------
drivers/net/mlx5/mlx5.h | 10 ++++++++
drivers/net/mlx5/mlx5_flow.c | 30 ++++++++++++++++++++--
10 files changed, 113 insertions(+), 14 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2021-04-15 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 7:22 [dpdk-dev] [PATCH " Haifei Luo
2021-04-14 7:22 ` [dpdk-dev] [PATCH 1/2] common/mlx5: add mlx5 APIs for single flow dump feature Haifei Luo
2021-04-14 7:22 ` [dpdk-dev] [PATCH 2/2] net/mlx5: " Haifei Luo
2021-04-14 8:56 ` [dpdk-dev] [PATCH v2 0/2] support single flow dump on MLX5 PMD Haifei Luo
2021-04-14 8:56 ` [dpdk-dev] [PATCH v2 1/2] common/mlx5: add mlx5 APIs for single flow dump feature Haifei Luo
2021-04-14 8:56 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: " Haifei Luo
2021-04-15 11:19 ` Haifei Luo [this message]
2021-04-15 11:19 ` [dpdk-dev] [PATCH v3 1/2] common/mlx5: " Haifei Luo
2021-04-15 11:19 ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: " Haifei Luo
2021-04-15 11:28 ` Slava Ovsiienko
2021-04-19 9:31 ` [dpdk-dev] [PATCH 0/2] support single flow dump on MLX5 PMD 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=1618485564-128533-1-git-send-email-haifeil@nvidia.com \
--to=haifeil@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@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).