DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>, Bill Zhou <dongz@mellanox.com>,
	"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	"beilei.xing@intel.com" <beilei.xing@intel.com>,
	"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	Ori Kam <orika@mellanox.com>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] app/testpmd: support flow aging
Date: Tue, 5 May 2020 10:23:42 +0100	[thread overview]
Message-ID: <ae7e2f37-1507-762c-2892-20bb0e77f2f9@intel.com> (raw)
In-Reply-To: <AM0PR0502MB4019694EBB1F952C2623C522D2A70@AM0PR0502MB4019.eurprd05.prod.outlook.com>

On 5/5/2020 10:11 AM, Matan Azrad wrote:
> 
> 
> From: Ferruh Yigit:
>> On 5/3/2020 9:59 AM, Bill Zhou wrote:
>>> Currently, there is no way to check the aging event or to get the
>>> current aged flows in testpmd, this patch include those implements, it's
>> included:
>>>
>>> - Add new item "flow_aged" to the current print event command
>> arguments.
>>> - Add new command to list all aged flows, meanwhile, we can set
>> parameter
>>>   to destroy it.
>>>
>>> Signed-off-by: Bill Zhou <dongz@mellanox.com>
>>> ---
>>> v2: Update the way of registering aging event, add new command to
>>> control if the event need be print or not. Update the output of the
>>> delete aged flow command format.
>>> v3: Change the command from only set aged flow output to set one
>>> gloable verbose bitmap for all events output.
>>> v4: Add the event output to current global print event arguments.
>>
>> <...>
>>
>>> @@ -187,9 +187,9 @@ usage(char* progname)
>>>  	printf("  --no-rmv-interrupt: disable device removal interrupt.\n");
>>>  	printf("  --bitrate-stats=N: set the logical core N to perform "
>>>  		"bit-rate calculation.\n");
>>> -	printf("  --print-event
>> <unknown|intr_lsc|queue_state|intr_reset|vf_mbox|macsec|intr_rmv|all
>>> : "
>>> +	printf("  --print-event
>> <unknown|intr_lsc|queue_state|intr_reset|vf_mbox|macsec|intr_rmv|flo
>> w_aged|all>: "
>>>  	       "enable print of designated event or all of them.\n");
>>> -	printf("  --mask-event
>> <unknown|intr_lsc|queue_state|intr_reset|vf_mbox|macsec|intr_rmv|all
>>> : "
>>> +	printf("  --mask-event
>> <unknown|intr_lsc|queue_state|intr_reset|vf_mbox|macsec|intr_rmv|flo
>> w_aged|all>: "
>>
>> +1 to '--print-event', can you please update the documentation for the
>> change?
> 
>  +1
> 
>> <...>
>>
>>> @@ -388,7 +389,8 @@ uint32_t event_print_mask = (UINT32_C(1) <<
>> RTE_ETH_EVENT_UNKNOWN) |
>>>  			    (UINT32_C(1) << RTE_ETH_EVENT_INTR_RESET) |
>>>  			    (UINT32_C(1) << RTE_ETH_EVENT_IPSEC) |
>>>  			    (UINT32_C(1) << RTE_ETH_EVENT_MACSEC) |
>>> -			    (UINT32_C(1) << RTE_ETH_EVENT_INTR_RMV);
>>> +			    (UINT32_C(1) << RTE_ETH_EVENT_INTR_RMV) |
>>> +			    (UINT32_C(1) << RTE_ETH_EVENT_FLOW_AGED);
>>
>> This is enabling the event logging by default, we are turning back to original
>> point, since '--print-event' can be used to enable it, can you please leave it
>> out by default?
> 
> The aged event is triggered only when there is at least one flow which is configured with AGE action,
> Don't you think it should be printed by default if the user requested aging in a flow?
> 
Good point, OK to keep as it is.
So only above doc update please and feel free to keep existing acks.

  reply	other threads:[~2020-05-05  9:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:55 [dpdk-dev] [PATCH] " Bill Zhou
2020-04-24 16:25 ` Ferruh Yigit
2020-04-26  7:23   ` Bill Zhou
2020-04-27 14:13     ` Ferruh Yigit
2020-04-27 15:12       ` Matan Azrad
2020-04-30 22:26         ` Ferruh Yigit
2020-04-30 15:53 ` [dpdk-dev] [PATCH v2] " Bill Zhou
2020-04-30 22:43   ` Ferruh Yigit
2020-05-01  6:51     ` Matan Azrad
2020-05-01  9:27       ` Ferruh Yigit
2020-05-01 11:28         ` Matan Azrad
2020-05-01 11:54           ` Ferruh Yigit
2020-05-01 12:45             ` Matan Azrad
2020-05-01 13:38               ` Ferruh Yigit
2020-05-01 15:14                 ` Matan Azrad
2020-05-01 15:44                   ` Ferruh Yigit
2020-05-02 14:00   ` [dpdk-dev] [PATCH v3] " Bill Zhou
2020-05-03  8:59     ` [dpdk-dev] [PATCH v4] " Bill Zhou
2020-05-03  9:46       ` Matan Azrad
2020-05-03 14:58       ` Ori Kam
2020-05-05  8:37       ` Ferruh Yigit
2020-05-05  9:11         ` Matan Azrad
2020-05-05  9:23           ` Ferruh Yigit [this message]
2020-05-05  9:49       ` [dpdk-dev] [PATCH v5] " Bill Zhou
2020-05-05 10:09         ` Ori Kam
2020-05-05 15:11           ` Ferruh Yigit
2020-05-06  8:04             ` Matan Azrad

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=ae7e2f37-1507-762c-2892-20bb0e77f2f9@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=dongz@mellanox.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=wenzhuo.lu@intel.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).