DPDK patches and discussions
 help / color / mirror / Atom feed
From: george.dit@gmail.com
To: dev@dpdk.org
Subject: [dpdk-dev] Some flow rules not supported by igb_uio
Date: Tue, 30 Jan 2018 10:20:29 +0100	[thread overview]
Message-ID: <CAN9HtFD+W_RqBoZu+Hoe=vOATzQVm4+zqm84H__xh_wLU=M_zg@mail.gmail.com> (raw)

Hi,

I am testing rte flow API across different DPDK-based NICs using some rules.
I noticed that flow rules that match L2 information, such as rule:

flow create 0 ingress pattern eth type is 0x800 / end actions queue index 6
/ end

does not work on an Intel 82599ES (igb_uio driver), while a
Mellanox ConnectX-4 (mlx5_core driver) accepts this rule.
Is there any reason behind this or could be a bug?

I am testing using DPDK v17.11.

Thanks,
Georgios
-- 
Georgios Katsikas
Industrial Ph.D. Student
Network Intelligence Group
Decision, Networks, and Analytics (DNA) Lab
RISE SICS
E-Mail:  georgios.katsikas@ri.se

                 reply	other threads:[~2018-01-30  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAN9HtFD+W_RqBoZu+Hoe=vOATzQVm4+zqm84H__xh_wLU=M_zg@mail.gmail.com' \
    --to=george.dit@gmail.com \
    --cc=dev@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).