From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1621] In packets provided by the PMD, some flags are missing
Date: Mon, 27 Jan 2025 05:57:33 +0000 [thread overview]
Message-ID: <bug-1621-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1621
Bug ID: 1621
Summary: In packets provided by the PMD, some flags are missing
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: ---
Description:
In packets provided by the PMD, some flags are missing. The application does
not have access to information provided by the hardware (packet is broadcast,
packet is multicast, packet is IPv4 and so on).
Implication:
The ol_flags field in the rte_mbuf structure is not correct and should not be
used.
Resolution/Workaround:
The application has to parse the Ethernet header itself to get the information,
which is slower.
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: 2973 bytes --]
reply other threads:[~2025-01-27 5:57 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-1621-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).