DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] rte_flow error after upgrading
Date: Mon, 1 Oct 2018 21:20:09 -0700	[thread overview]
Message-ID: <CA+Gp1nazTUrhKzfvyHU5oL6TqXJsKXiWrJf_FHX2WaV=yZy-tw@mail.gmail.com> (raw)

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+?

             reply	other threads:[~2018-10-02  4:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  4:20 Cliff Burdick [this message]
2018-10-02  4:27 ` Arvind Narayanan
2018-10-02  4:36   ` Cliff Burdick

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='CA+Gp1nazTUrhKzfvyHU5oL6TqXJsKXiWrJf_FHX2WaV=yZy-tw@mail.gmail.com' \
    --to=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).