From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1578] Observed Inconsistencies In Device Allow-list Pools.
Date: Thu, 14 Nov 2024 22:17:19 +0000 [thread overview]
Message-ID: <bug-1578-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1578
Bug ID: 1578
Summary: Observed Inconsistencies In Device Allow-list Pools.
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: npratte@iol.unh.edu
Target Milestone: ---
Vendor NICs allow for a set amount of mac addresses to be stored as an
allow-list for general address filtering. The exact amount of mac addresses to
be added can be discovered through the ethdev api, but when creating universal,
vendor-agnostic tests for this functionality, some vendors may allow for the
listed amount of addresses not including the device's vendor-given mac address
(so if the device claims it can support 128 addresses, it can actually support
129). Some other vendors take a different approach and allow for the list total
of addresses including the vendor-provided address (so a device that supports
128 addresses can only add 127 extra before throwing an error).
There are ways to avoid this problem from coming up by creating an upper bound
that no device should ever reasonably cross, but it might be best to discuss
what is suitable for testing this functionality in the long-term.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3355 bytes --]
reply other threads:[~2024-11-14 22:17 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-1578-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).