DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] rte_flow error after upgrading
@ 2018-10-02  4:20 Cliff Burdick
  2018-10-02  4:27 ` Arvind Narayanan
  0 siblings, 1 reply; 3+ messages in thread
From: Cliff Burdick @ 2018-10-02  4:20 UTC (permalink / raw)
  To: users

Hi, I upgraded to DPDK 18.05 from 17.11 and a previously-working rte_flow
code now fails. I'm using the mlx5 driver, and when I do something similar
to the rte_flow example code, the following error shows:

"VLAN cannot be empty"

I looked at the code in .drivers/net/mlx5/mlx5_flow.c, and it looks like it
now complains when the mask isn't set on a VLAN flow layer. I tried setting
the mask to 0xffff, and the error no longer shows, but packets are not
classified properly either, and they all go to queue 0. Has anyone been
able to get a working rte_flow queue classifier working with 18.05+?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] rte_flow error after upgrading
  2018-10-02  4:20 [dpdk-users] rte_flow error after upgrading Cliff Burdick
@ 2018-10-02  4:27 ` Arvind Narayanan
  2018-10-02  4:36   ` Cliff Burdick
  0 siblings, 1 reply; 3+ messages in thread
From: Arvind Narayanan @ 2018-10-02  4:27 UTC (permalink / raw)
  To: shaklee3; +Cc: users

It is because of a recent patch http://patchwork.dpdk.org/patch/36068/

If you don't care about VLAN action, just remove that action all together
and check the correctness of your code.
If all of them are going to q0 (and assuming isolation mode is not
enabled), then it is most likely because packets don't match any of the
rte_flow rules you created.

A

On Mon, Oct 1, 2018 at 11:20 PM Cliff Burdick <shaklee3@gmail.com> wrote:

> Hi, I upgraded to DPDK 18.05 from 17.11 and a previously-working rte_flow
> code now fails. I'm using the mlx5 driver, and when I do something similar
> to the rte_flow example code, the following error shows:
>
> "VLAN cannot be empty"
>
> I looked at the code in .drivers/net/mlx5/mlx5_flow.c, and it looks like it
> now complains when the mask isn't set on a VLAN flow layer. I tried setting
> the mask to 0xffff, and the error no longer shows, but packets are not
> classified properly either, and they all go to queue 0. Has anyone been
> able to get a working rte_flow queue classifier working with 18.05+?
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] rte_flow error after upgrading
  2018-10-02  4:27 ` Arvind Narayanan
@ 2018-10-02  4:36   ` Cliff Burdick
  0 siblings, 0 replies; 3+ messages in thread
From: Cliff Burdick @ 2018-10-02  4:36 UTC (permalink / raw)
  To: Arvind Narayanan; +Cc: users

Thanks, I will try that. I saw that patch, but couldn't find any working
examples with vlan. In the other layers, such as Ethernet, zeroing out the
source and dest has the effect of allowing all. However, the vlan on
mellanox cards breaks that it seems because of the IB compatibility. I
think the flow filtering example needs to be updated, since it will no
longer work on these cards. If I get it working I'll submit a PR.

On Mon, Oct 1, 2018, 21:28 Arvind Narayanan <webguru2688@gmail.com> wrote:

> It is because of a recent patch http://patchwork.dpdk.org/patch/36068/
>
> If you don't care about VLAN action, just remove that action all together
> and check the correctness of your code.
> If all of them are going to q0 (and assuming isolation mode is not
> enabled), then it is most likely because packets don't match any of the
> rte_flow rules you created.
>
> A
>
> On Mon, Oct 1, 2018 at 11:20 PM Cliff Burdick <shaklee3@gmail.com> wrote:
>
>> Hi, I upgraded to DPDK 18.05 from 17.11 and a previously-working rte_flow
>> code now fails. I'm using the mlx5 driver, and when I do something similar
>> to the rte_flow example code, the following error shows:
>>
>> "VLAN cannot be empty"
>>
>> I looked at the code in .drivers/net/mlx5/mlx5_flow.c, and it looks like
>> it
>> now complains when the mask isn't set on a VLAN flow layer. I tried
>> setting
>> the mask to 0xffff, and the error no longer shows, but packets are not
>> classified properly either, and they all go to queue 0. Has anyone been
>> able to get a working rte_flow queue classifier working with 18.05+?
>>
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-10-02  4:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-02  4:20 [dpdk-users] rte_flow error after upgrading Cliff Burdick
2018-10-02  4:27 ` Arvind Narayanan
2018-10-02  4:36   ` Cliff Burdick

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).