HI Thomas,
#1, okay , will modify title as " ethdev: dump single flow rule " .
#2, yes, it can pass NULL. Will modify as you described.
Thank you so much for the comments.
-----Original Message-----
From: Thomas Monjalon <[email protected]>
Sent: Wednesday, April 14, 2021 4:58 PM
To: Haifei Luo <[email protected]>
Cc: [email protected]; Ori Kam <[email protected]>; Slava Ovsiienko
<[email protected]>; Raslan Darawsheh <[email protected]>;
Xueming(Steven) Li <[email protected]>; Haifei Luo <[email protected]>;
[email protected]; Xiaoyun Li <[email protected]>; Matan Azrad
<[email protected]>; Shahaf Shuler <[email protected]>; Jerin Jacob
<[email protected]>; Nithin Dabilpuram <[email protected]>; Kiran Kumar
K <[email protected]>; Ferruh Yigit <[email protected]>; Andrew
Rybchenko <[email protected]>
Subject: Re: [PATCH v4 1/3] ethdev: modify rte API for single flow dump
External email: Use caution opening links or attachments
About the title, what is "rte API"?
I guess you mean DPDK API with rte prefix.
But given all DPDK API have rte prefix,
and this patch is for DPDK,
you can just say "API".
So the title can be:
ethdev: modify API for single flow dump
But it can look as single flow dump was possible before, which is wrong because
it is a new feature.
Another idea is wrong:
The packets of the flow are not dumped,
it is only dumping the HW representation of the flow rule.
I propose to simply describe the new feature:
ethdev: dump single flow rule
> + * @param[in] flow
> + * The pointer of rte flow.
Please replace "rte flow" with 'flow rule".
Is it allowed to pass NULL? Will it dump all?
If yes, you can change to:
Flow rule to dump.
Dump all rules if NULL.
