From: Raslan Darawsheh <rasland@nvidia.com>
To: Haifei Luo <haifeil@nvidia.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"xiaoyun.li@intel.com" <xiaoyun.li@intel.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
Haifei Luo <haifeil@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] support single flow dump on MLX5 PMD
Date: Mon, 19 Apr 2021 09:31:19 +0000 [thread overview]
Message-ID: <DM6PR12MB2748DE887CCA839432331D97CF499@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1618384952-179763-1-git-send-email-haifeil@nvidia.com>
Hi,
> -----Original Message-----
> From: Haifei Luo <haifeil@nvidia.com>
> Sent: Wednesday, April 14, 2021 10:23 AM
> To: ferruh.yigit@intel.com; Slava Ovsiienko <viacheslavo@nvidia.com>;
> Matan Azrad <matan@nvidia.com>; xiaoyun.li@intel.com; NBU-Contact-
> Thomas Monjalon <thomas@monjalon.net>; Ori Kam <orika@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> Xueming(Steven) Li <xuemingl@nvidia.com>; Haifei Luo
> <haifeil@nvidia.com>
> Subject: [PATCH 0/2] support single flow dump on MLX5 PMD
>
> 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.
>
> Depends-on: series=16355 ("support single flow dump")
> http://patchwork.dpdk.org/project/dpdk/list/?series=16355
>
> 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_socket.c | 30 ++++++++++++++++++++++++--
> ----
> drivers/net/mlx5/mlx5_flow.c | 30
> ++++++++++++++++++++++++++++--
> 8 files changed, 87 insertions(+), 10 deletions(-)
>
> --
> 1.8.3.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-04-19 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 7:22 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 ` [dpdk-dev] [PATCH v3 0/2] support single flow dump on MLX5 PMD Haifei Luo
2021-04-15 11:19 ` [dpdk-dev] [PATCH v3 1/2] common/mlx5: add mlx5 APIs for single flow dump feature 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 ` Raslan Darawsheh [this message]
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=DM6PR12MB2748DE887CCA839432331D97CF499@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haifeil@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=xiaoyun.li@intel.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).