From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 535] mlx5: vlan/qinq packets are not matched by eth/ipv4 RTE_FLOW
Date: Wed, 09 Sep 2020 08:46:21 +0000 [thread overview]
Message-ID: <bug-535-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=535
Bug ID: 535
Summary: mlx5: vlan/qinq packets are not matched by eth/ipv4
RTE_FLOW
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: maxime.leroy@6wind.com
Target Milestone: ---
With dpdk 19.11.0, the following rte_flow created in test pmd:
> flow create 0 ingress pattern eth type spec 0 type mask 0 / ipv4 / end
actions mark id 2 / queue index 0 / end
was able to match ipv4 whatever if the packets has 0 or N vlan headers.
With dpdk 19.11.4, it's not anymore possible.
Only packets without vlan header are matched. It means that packet having the
type field in the ethernet header not equal to 0x800 are not matched. But in
the RTE_FLOW, the mask of the type field of the Ethernet item is set to 0.
By the way, I can also reproduce the issue with the master branch.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-09-09 8:46 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-535-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).