From: David Bouyeure <david.bouyeure@fraudbuster.mobi>
To: dev@dpdk.org
Subject: [dpdk-dev] rte_flow ageing
Date: Mon, 29 Mar 2021 10:34:58 +0200 [thread overview]
Message-ID: <26698242-bb7b-baa0-9e61-235ac3725cd7@fraudbuster.mobi> (raw)
Hi,
I've found out the pretty useful experimental brand new flow ageing API
implemented in the mlx5 PMD.
I'm trying it (rte_eth_dev_callback_register(RTE_ETH_EVENT_FLOW_AGED),
RTE_FLOW_ACTION_TYPE_AGE) to recover any flow that I previously offloaded.
The DPDK version is 20.08 and Mellanox(Connect-X6) OFED drivers are
5.1-2.5.8.0.
I eventually don't see the usefulness of the callback since it's
actually triggered indirectly by us(the DPDK application) when calling
rte_flow_get_aged_flows(). If we don't call it, the callback is called
only once.
And, calling rte_flow_get_aged_flows() from the callback won't trigger
it next time(MLX5_AGE_TRIGGER is reset after the callback call)
Furthermore, I don't see the point of computing ageing flows in
mlx5_fow.c::mlx5_flow_aging_check() if the client callback isn't called.
So far, I can handle the flow ageing from the same thread as the one
which is handling the flow direction(rte_flow), it even avoid threads
synchronization. But, in the future, I may need to be noticed as soon as
possible of a single flow ageing, and thus handle this flow logic from
the ageing callback.
I may misunderstand the whole ageing API... Thanks a lot for any
clarification.
next reply other threads:[~2021-03-29 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 8:34 David Bouyeure [this message]
2021-03-29 18:02 ` Asaf Penso
2021-03-30 15:45 ` David Bouyeure
2021-04-05 10:23 ` Matan Azrad
2021-04-07 16:19 ` David Bouyeure
2021-04-07 18:09 ` Matan Azrad
2021-04-08 7:50 ` David Bouyeure
2021-04-08 9:52 ` Matan Azrad
2021-04-08 16:45 ` David Bouyeure
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 10:42 [dpdk-dev] [PATCH v2 1/3] net/iavf: support GTPU inner IPv4 for FDIR Junfeng Guo
2021-03-26 14:29 ` [dpdk-dev] [PATCH v3 0/3] support GTPU inner IPv4/IPv6 for AVF FDIR Junfeng Guo
2021-03-26 14:29 ` [dpdk-dev] [PATCH v3 1/3] net/iavf: support GTPU inner IPv4 for FDIR Junfeng Guo
2021-03-29 7:50 ` [dpdk-dev] rte_flow ageing David Bouyeure
2021-03-29 8:32 ` David Bouyeure
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=26698242-bb7b-baa0-9e61-235ac3725cd7@fraudbuster.mobi \
--to=david.bouyeure@fraudbuster.mobi \
--cc=dev@dpdk.org \
/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).