From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 563] mlx5 silently fails to create an ethernet rte_flow rule
Date: Thu, 22 Oct 2020 20:39:37 +0000 [thread overview]
Message-ID: <bug-563-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=563
Bug ID: 563
Summary: mlx5 silently fails to create an ethernet rte_flow
rule
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: barbette@kth.se
Target Milestone: ---
With 20.11-rc1 (since at least -rc0 but maybe before), a rule such as:
flow create 0 ingress pattern eth type is 0x0800 / end actions drop / end
will say "Flow rule #0 created". But nothing is actually programmed in the NIC,
and ipv4 packets are not dropped.
But also ones matching mac addresses (anything except eth alone according to my
tests). It's also not linked to the action, eg queue index 0 on table 1 to
un-drop packets sent to table 1 does not work either.
I also verified with the mlx_steering_dump/mlx_steering_dump_parser.py tool and
the rule is indeed not there.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-10-22 20:39 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=bug-563-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).