[dpdk-dev] rte_flow ageing
Matan Azrad
matan at nvidia.com
Wed Apr 7 20:09:12 CEST 2021
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.bouyeure at fraudbuster.mobi>
Sent: Wednesday, April 7, 2021 7:19:34 PM
To: Matan Azrad <matan at nvidia.com>; Asaf Penso <asafp at nvidia.com>; dev at dpdk.org <dev at dpdk.org>
Cc: Jack Min <jackmin at 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:
More information about the dev
mailing list