From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Haifei Luo <haifeil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Ori Kam <orika@nvidia.com>, Shahaf Shuler <shahafs@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: support flow dump value
Date: Mon, 5 Jul 2021 07:38:05 +0000 [thread overview]
Message-ID: <DM6PR12MB3753D869B3B5D474F0B11E64DF1C9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210531022208.11962-1-haifeil@nvidia.com>
> -----Original Message-----
> From: Haifei Luo <haifeil@nvidia.com>
> Sent: Monday, May 31, 2021 5:22
> To: Matan Azrad <matan@nvidia.com>; Ori Kam <orika@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Shahaf Shuler <shahafs@nvidia.com>
> Cc: dev@dpdk.org; NBU-Contact-Thomas Monjalon <thomas@monjalon.net>;
> Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH] net/mlx5: support flow dump value
>
> Currently the flow dump provides few information about actions
> - just the pointers. Add implementations to display details for counter,
> modify_hdr and encap_decap actions.
>
> For counter, the regular flow operation query is engaged and the counter
> content information is provided, including hits and bytes values.For modify_hdr,
> encap_and decap actions, the information stored in the ipool objects is dumped.
>
> There are the formats of information presented in the dump:
> 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>
next prev parent reply other threads:[~2021-07-05 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 2:22 Haifei Luo
2021-07-05 7:38 ` Slava Ovsiienko [this message]
2021-07-06 9:33 ` 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=DM6PR12MB3753D869B3B5D474F0B11E64DF1C9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=haifeil@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shahafs@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).