From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1640] Ethertype filter could receive other packets (non-assigned) in Niantic
Date: Mon, 03 Feb 2025 03:08:46 +0000 [thread overview]
Message-ID: <bug-1640-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1640
Bug ID: 1640
Summary: Ethertype filter could receive other packets
(non-assigned) in Niantic
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
On Intel® Ethernet Controller 82599EB When Ethertype filter (priority enable)
was set, unmatched packets also could be received on the assigned queue, such
as ARP packets without 802.1q tags or with the user priority not equal to set
value. Launch the testpmd by disabling RSS and with multiply queues, then add
the ethertype filter like the following and then start forwarding:
add_ethertype_filter 0 ethertype 0x0806 priority enable 3 queue 2 index 1
When sending ARP packets without 802.1q tag and with user priority as non-3 by
tester, all the ARP packets can be received on the assigned queue.
Implication:
The user priority comparing in Ethertype filter cannot work probably. It is a
NIC’s issue due to the following: “In fact, ETQF.UP is not functional, and the
information will be added in errata of 82599 and X540.”
Resolution/Workaround:
None
Affected Environment/Platform:
All.
Driver/Module:
Poll Mode Driver (PMD).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3438 bytes --]
reply other threads:[~2025-02-03 3:08 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-1640-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).