From: Raslan Darawsheh <rasland@nvidia.com>
To: Haifei Luo <haifeil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: enhancement for flow dump value
Date: Thu, 28 Oct 2021 15:02:46 +0000 [thread overview]
Message-ID: <DM4PR12MB5312DEE5EE2FD0E22A9C07F9CF869@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211026035632.11840-1-haifeil@nvidia.com>
Hi,
> -----Original Message-----
> From: Haifei Luo <haifeil@nvidia.com>
> Sent: Tuesday, October 26, 2021 6:57 AM
> To: Matan Azrad <matan@nvidia.com>; Ori Kam <orika@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; ferruh.yigit@intel.com
> Cc: dev@dpdk.org; NBU-Contact-Thomas Monjalon
> <thomas@monjalon.net>; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH] net/mlx5: enhancement for flow dump value
>
> Multiple rules could use the same encap_decap/modify_hdr/counter action.
> The flow dump data could be duplicated.
>
> To avoid redundancy, flow dump value is based on the actions' pointer
> instead of previous rules' pointer.
>
> For counter, the data is stored in cmng of priv->sh.
> For encap_decap/modify_hdr, the data stored in
> encaps_decaps/modify_cmds.
> Traverse the fields and get action's pointer and information.
>
> Formats are same for information in the dump except "id" stands for
> actions' pointer:
> Counter: rec_type,id,hits,bytes
> Modify_hdr: rec_type,id,actions_number,actions
> Encap_decap: rec_type,id,buf
>
> Signed-off-by: Haifei Luo <haifeil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-10-28 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 3:56 Haifei Luo
2021-10-28 15:02 ` 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=DM4PR12MB5312DEE5EE2FD0E22A9C07F9CF869@DM4PR12MB5312.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 \
/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).