From: Raslan Darawsheh <rasland@mellanox.com>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: "katsikas.gp@gmail.com" <katsikas.gp@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] Problem installing rules with counters on MLX5
Date: Mon, 15 Oct 2018 11:02:40 +0000 [thread overview]
Message-ID: <DB5PR05MB1254E57085897AE25934C16EC2FD0@DB5PR05MB1254.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CA+Gp1nZpvdJ-C7_EDD+7yCd+PAMPYmmMLejFrF8uz8ssTSey+w@mail.gmail.com>
I would recommend using testpmd to test that since I didn’t get the chance to test this example application.
And if you are using testpmd it would for sure work, but if it didn’t work for you let me know what errors you are getting.
Kindest regards,
Raslan Darawsheh
From: Cliff Burdick <shaklee3@gmail.com>
Sent: Sunday, October 14, 2018 4:26 PM
To: Raslan Darawsheh <rasland@mellanox.com>
Cc: katsikas.gp@gmail.com; users <users@dpdk.org>
Subject: Re: [dpdk-users] Problem installing rules with counters on MLX5
Hi Raslan, I was seeing that error, but after filling in that field, it would not classify in any queue other than zero. Since the rte_flow code in the examples directory does not set the vlan fields properly for the mlx5 driver, it also gives the error:
http://doc.dpdk.org/api/examples_2flow_filtering_2flow_blocks_8c-example.html<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fapi%2Fexamples_2flow_filtering_2flow_blocks_8c-example.html&data=02%7C01%7Crasland%40mellanox.com%7Ce3977aa09e3d42029e5408d631d8a3ac%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636751203881163503&sdata=JgGjVj69wdu9e6x6jSPxcwcxXQhq8u8I%2FEEk9DfzSB0%3D&reserved=0>
My plan was to fix the problem, test it, and submit a patch for the example. However, despite being able to get the error to go away with the correct mask, I was never able to get the flow to direct into anything other than queue 1 on dpdk 18.
On Sun, Oct 14, 2018, 00:43 Raslan Darawsheh <rasland@mellanox.com<mailto:rasland@mellanox.com>> wrote:
Hi Cliff,
Can you please send me what exactly you are seeing?
As for the email that you are referring this is a limitation for MLX5 that it can’t have empty vlan you need to specify vid in order for it to work.
Kindest regards,
Raslan Darawsheh
From: Cliff Burdick <shaklee3@gmail.com<mailto:shaklee3@gmail.com>>
Sent: Friday, October 12, 2018 7:11 PM
To: Raslan Darawsheh <rasland@mellanox.com<mailto:rasland@mellanox.com>>
Cc: katsikas.gp@gmail.com<mailto:katsikas.gp@gmail.com>; users <users@dpdk.org<mailto:users@dpdk.org>>
Subject: Re: [dpdk-users] Problem installing rules with counters on MLX5
Hi Raslan, can you confirm if rte_flow is partially broken in dpdk 18 on mlx5? The example code for rte_flow is broken, and I didn't see any responses here:
http://mails.dpdk.org/archives/users/2018-October/003510.html<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmails.dpdk.org%2Farchives%2Fusers%2F2018-October%2F003510.html&data=02%7C01%7Crasland%40mellanox.com%7Ce3977aa09e3d42029e5408d631d8a3ac%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636751203881163503&sdata=wVQWfT%2FGb0MKPiMV2Ew1pNeMxn2WfeX7Of4HJ43E03Q%3D&reserved=0>
On Thu, Oct 11, 2018 at 5:16 AM Raslan Darawsheh <rasland@mellanox.com<mailto:rasland@mellanox.com>> wrote:
Hi Georgios,
You are trying to create the same rule with three different actions.
I would suggest that you change your mask to be proto is 1/6/17
This way you'll have three different rules
Kindest regards,
Raslan Darawsheh
> -----Original Message-----
> From: users <users-bounces@dpdk.org<mailto:users-bounces@dpdk.org>> On Behalf Of Georgios Katsikas
> Sent: Thursday, October 11, 2018 3:01 PM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: [dpdk-users] Problem installing rules with counters on MLX5
>
> Dear all,
>
> I am trying to install 3 simple rules (to match ICMP, TCP, and UDP flows) on a
> Mellanox ConnectX-5 100 GbE NIC using DPDK's flow API.
> The rules are as follows:
>
> 1. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 1
> proto mask 0x0 / end actions queue index 0 / count / end
> 2. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 6
> proto mask 0x0 / end actions queue index 0 / count / end
> 3. flow create 0 ingress pattern eth type is 2048 / ipv4 proto spec 17
> proto mask 0x0 / end actions queue index 0 / count / end
>
> Only the first rule gets properly installed. The remaining 2 rules throw the
> following error:
> Caught error type 1 (cause unspecified): hardware refuses to create flow
>
> If I try to incorporate 'count identifier <index> shared 0', I still get error (with
> or without shared).
> If I try to install the same rules without action count, then everything works
> as expected.
> Action count on rules that match src/dst IP addresses works fine.
> Could you please shed some light on this?
>
> I am using DPDK 18.08 with Mellanox OFED 4.4-2.0.7.0 (latest).
>
> Thanks,
> Georgios
prev parent reply other threads:[~2018-10-15 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 12:00 Georgios Katsikas
2018-10-11 12:16 ` Raslan Darawsheh
2018-10-11 12:21 ` Georgios Katsikas
2018-10-12 16:11 ` Cliff Burdick
2018-10-14 7:43 ` Raslan Darawsheh
2018-10-14 13:26 ` Cliff Burdick
2018-10-15 11:02 ` Raslan Darawsheh [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=DB5PR05MB1254E57085897AE25934C16EC2FD0@DB5PR05MB1254.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=katsikas.gp@gmail.com \
--cc=shaklee3@gmail.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).