From: Stephen Hemminger <stephen@networkplumber.org>
To: 钟 <gdsgsx2002@163.com>
Cc: dev@dpdk.org
Subject: Re: why DPDK reassembles IP fragment packets with AF_PACKET
Date: Mon, 8 Jan 2024 08:42:32 -0800 [thread overview]
Message-ID: <20240108084232.09500487@hermes.local> (raw)
In-Reply-To: <731d30bf.7034.18ce8c16f15.Coremail.gdsgsx2002@163.com>
On Mon, 8 Jan 2024 19:07:20 +0800 (CST)
钟 <gdsgsx2002@163.com> wrote:
> Hi All,
>
>
> Recently I debug ovs-dpdk with AF_PACKET mode. When IP fragment packets are received via DPDK, the IP fragment packets are reassembled by DPDK. After reassembly, the packet length is over 1518. They are discarded by OVS because of oversize packets.
>
>
> I don't understandy why PACKET_FLAG_DEFRAG is set for AF_PACKET mode.
>
>
Not sure, but it looks like the af_packet wants to hash packets for fanout.
Hashin of fragments won't work correctly, and packet will arrive on different queues if fragmented.
next prev parent reply other threads:[~2024-01-08 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:07 钟
2024-01-08 16:42 ` Stephen Hemminger [this message]
2024-01-09 1:00 ` 钟
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=20240108084232.09500487@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=gdsgsx2002@163.com \
/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).