* Flow filtering issues : not deleted on NIC at time of call rte_flow_destroy
@ 2022-07-08 7:21 Antoine POLLENUS
0 siblings, 0 replies; only message in thread
From: Antoine POLLENUS @ 2022-07-08 7:21 UTC (permalink / raw)
To: users
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Hello,
We have some issues with the flow filtering API.
When deleting a filter, just after rte_flow_destroy, we clear the received packets by receiving all packet in that mempool.
The issue is that the nic still receive packet in that mempool after the rte_flow_destroy is done.
We than reuse this mempool to receive packet from a different origin, and we see that this mempool still have packet from the previous origin.
The filter we use is simply a queue one based on the IP and the UDP dst and src.
The questions are:
- Is the rte_flow_destroy asynchronous on the NIC ? we see the filter doesn't exist anymore in DPDK.
- If yes, is there a way to know when the filter is effectively deleted on the NIC ?
- Is there a way to reset the mempool in a clean way without deleting it ?
At this stage to avoid this issue the only fix we found is to sleep during one second after the call of rte_flow_destroy and then receiving the remaining packets still present in mempool.
Hope I'll find help here,
Regards,
Antoine Pollenus
[-- Attachment #2: Type: text/html, Size: 9537 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-07-08 7:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-08 7:21 Flow filtering issues : not deleted on NIC at time of call rte_flow_destroy Antoine POLLENUS
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).