From: Asaf Penso <asafp@mellanox.com>
To: Erez Ferber <erezferber@gmail.com>, Gerry Wan <gerryw@stanford.edu>
Cc: "users@dpdk.org" <users@dpdk.org>, Bing Zhao <bingz@mellanox.com>
Subject: Re: [dpdk-users] COUNT action not supported on mlx5
Date: Wed, 29 Jul 2020 15:26:14 +0000 [thread overview]
Message-ID: <AM0PR05MB4289B4081B0AF91598EE4A6FC0700@AM0PR05MB4289.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAF5_M5ijYPLoBhGG0ZKaUtmDQvwPvHQ-EEvQ6uTnSd=5HUeXHw@mail.gmail.com>
Hello Gerry,
Regarding your question about RAW. Can you specify your use case?
In high level planning we'll consider supporting it in 21.02.
Regards,
Asaf Penso
-----Original Message-----
From: users <users-bounces@dpdk.org> On Behalf Of Erez Ferber
Sent: Monday, July 27, 2020 9:25 PM
To: Gerry Wan <gerryw@stanford.edu>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] COUNT action not supported on mlx5
Hi,
One possible condition to get -ENOTSUP is if DevX is disabled on the NIC, Have you verified DevX is enabled ?
Please check here :
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.dpdk.org%2Fguides%2Fnics%2Fmlx5.html&data=02%7C01%7Casafp%40mellanox.com%7C038afadf61c844e6506808d8325a5eed%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C637314711005622085&sdata=B0O%2FBe6TlY%2BCRDPXcAFyAaBS701iLV5BO%2B6kcqCs4b0%3D&reserved=0
---
enable DevX (required by Direct Rules and other features):
UCTX_EN=1
---
With higher log verbosity, you could check in the application initialization if mlx5 PMD returns"DevX is supported" to make sure.
Regards,
Erez
On Mon, 27 Jul 2020 at 21:12, Gerry Wan <gerryw@stanford.edu> wrote:
> Hello,
>
> I'm trying to query per-flow statistics using
> RTE_FLOW_ACTION_TYPE_COUNT on a Mellanox ConnectX-5 port. I tried
> extending the flow_filtering sample application with:
>
> struct rte_flow_query_count count = {
> .reset = 1,
> .hits_set = 1,
> .bytes_set = 1,
> .hits = 0,
> .bytes = 0,
> };
>
> // set attr, pattern, etc.
>
> action[0].type = RTE_FLOW_ACTION_TYPE_COUNT; action[0].conf = &count;
> action[1].type = RTE_FLOW_ACTION_TYPE_QUEUE; action[1].conf = &queue;
> action[2].type = RTE_FLOW_ACTION_TYPE_END;
>
> The call to rte_flow_validate() returns with -ENOTSUP, saying the flow
> cannot be created because the count action is not supported. However,
> mlx5 documentation
> (https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc
> .dpdk.org%2Fguides%2Fnics%2Fmlx5.html%23statistics&data=02%7C01%7C
> asafp%40mellanox.com%7C038afadf61c844e6506808d8325a5eed%7Ca652971c7d2e
> 4d9ba6a4d149256f461b%7C0%7C1%7C637314711005622085&sdata=pQ7pRgytQB
> %2F1IUGV2SZR5IrGNMZyMdseuECjIw7uuOE%3D&reserved=0)
> states that it does indeed support attaching count actions. Without
> the count action the flow rule configuration works fine.
>
> I am using DPDK-20.05 and MLNX_OFED_LINUX-5.0-2.1.8.0, with a
> ConnectX-5 Virtual Function (could the VF be the issue?). What can be
> the cause of this?
>
> On a related note, is there any plan for mlx5 to support
> RTE_FLOW_ITEM_TYPE_RAW?
>
> Thanks,
>
next prev parent reply other threads:[~2020-07-29 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 18:11 Gerry Wan
2020-07-27 18:24 ` Erez Ferber
2020-07-29 15:26 ` Asaf Penso [this message]
2020-07-29 21:52 ` Gerry Wan
-- strict thread matches above, loose matches on Subject: below --
2020-07-23 17:37 Gerry Wan
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=AM0PR05MB4289B4081B0AF91598EE4A6FC0700@AM0PR05MB4289.eurprd05.prod.outlook.com \
--to=asafp@mellanox.com \
--cc=bingz@mellanox.com \
--cc=erezferber@gmail.com \
--cc=gerryw@stanford.edu \
--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).