From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1443] net/af_packet: defragmented packet will be truncated when exceed the frame size
Date: Fri, 17 May 2024 09:39:35 +0000 [thread overview]
Message-ID: <bug-1443-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1443
Bug ID: 1443
Summary: net/af_packet: defragmented packet will be truncated
when exceed the frame size
Product: DPDK
Version: 23.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: 1204565380@qq.com
Target Milestone: ---
af_packet use packet fanout, set flag: PACKET_FANOUT_FLAG_DEFRAG, if set,
causes packets to be defragmented before fanout is applied, the packets that
read from AF_PACKET socket maybe larger than the frame size and the mbuf size,
so the packet will be truncated.
In PACKET_FANOUT mode, each matching packet is enqueued onto only one socket in
the group. But when af_packet use one rx queue, there is no need to set packet
fanout.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2919 bytes --]
reply other threads:[~2024-05-17 9: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-1443-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).