From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Ivan Malov <ivan.malov@oktetlabs.ru>, dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC PATCH] ethdev: add support for testpmd-compliant flow rule dumping
Date: Thu, 17 Jun 2021 13:41:09 +0530 [thread overview]
Message-ID: <44267d3b-b496-59da-02bb-df84176bbf90@intel.com> (raw)
In-Reply-To: <97d647fc-011a-d99b-4cf6-c2d35350a8bc@intel.com>
Hi Ivan,
Another option is to log these structures values (rte_flow_attr ,
rte_flow_item, rte_flow_action) as it is.
Latter run a parsing script on these logs, to convets them into
meaningful flow items.
The completeness of the solution will depend on how well script is
maintained.
Regards
Aman
next prev parent reply other threads:[~2021-06-17 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 8:25 Ivan Malov
2021-05-30 7:27 ` Ori Kam
2021-05-31 2:28 ` Stephen Hemminger
2021-06-01 14:17 ` Ivan Malov
2021-06-01 15:10 ` Stephen Hemminger
2021-06-01 14:08 ` Ivan Malov
2021-06-02 13:32 ` Ori Kam
2021-06-02 13:49 ` Andrew Rybchenko
2021-06-03 8:25 ` Ori Kam
2021-06-03 8:43 ` Andrew Rybchenko
2021-06-03 9:27 ` Ori Kam
2023-03-23 12:54 ` Ferruh Yigit
2021-06-02 20:48 ` Stephen Hemminger
2021-06-14 12:42 ` Singh, Aman Deep
2021-06-17 8:11 ` Singh, Aman Deep [this message]
2021-07-02 10:20 ` Andrew Rybchenko
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=44267d3b-b496-59da-02bb-df84176bbf90@intel.com \
--to=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
/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).