Yes you can call it from the event callback.
Yes, MLX5_AGE_TRIGGER probably means that event was sent and no need to send it again in the next aged-out flow. Erasing it cause new event to be sent in the next aged-out flow... I don't understand what is the issue for you in option 1... השג את Outlook עבור Android<https://aka.ms/AAb9ysg> ________________________________ From: David Bouyeure <david.bouye...@fraudbuster.mobi> Sent: Wednesday, April 7, 2021 7:19:34 PM To: Matan Azrad <ma...@nvidia.com>; Asaf Penso <as...@nvidia.com>; dev@dpdk.org <dev@dpdk.org> Cc: Jack Min <jack...@nvidia.com> Subject: Re: [dpdk-dev] rte_flow ageing External email: Use caution opening links or attachments Hi Matan, and thanks a lot, regarding the mode 1, I still have a doubt: 1. Register the AGE event -> in event time to query the aged-out flows by the rte_flow_get_aged_flows API, this call will trigger a new event when new aged-out flow will be detected for the port.(if you don’t call rte_flow_get_aged_flows the event will not be retriggered.) You meant calling rte_flow_get_aged_flows() from the event callback I guess...? I think this is not working because MLX5_AGE_TRIGGER is erased when the callback returns. Anyway, the polling mode is enough to me so far. Thanks again. Regards. On 4/5/21 12:23 PM, Matan Azrad wrote:
