From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Aisenur Yoldaş" <aisenur.yoldas@b-ulltech.com>
Cc: users@dpdk.org
Subject: Re: Rte_flow function
Date: Mon, 22 May 2023 17:05:50 +0300 [thread overview]
Message-ID: <20230522170550.630a0c3c@sovereign> (raw)
In-Reply-To: <1989053041.4731986.1684762501124.JavaMail.zimbra@b-ulltech.com>
2023-05-22 16:35 (UTC+0300), Aisenur Yoldaş:
> I am trying to use the rte_flow_query function to find all the flow rules in a port, but when it comes the action parameter i cannot find the right way because when I use count action like in the ipsec example
>
> [...]
>
> What is the correct way to use this function in order to reach all the flows of the port.
There is no API to query the list of flow rules of a port.
rte_flow_query() is to query the state a specific single flow rule.
For example, if the action list on flow rule creation included COUNT,
then rte_flow_query() would allow to get the counter value
(how many packets have hit the rule).
Your action list doesn't have a COUNT action (or any stateful action)
so there is nothing to query.
prev parent reply other threads:[~2023-05-22 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 13:35 Aisenur Yoldaş
2023-05-22 14:05 ` Dmitry Kozlyuk [this message]
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=20230522170550.630a0c3c@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=aisenur.yoldas@b-ulltech.com \
--cc=users@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).