From: Stephen Hemminger <stephen@networkplumber.org>
To: Sriram Yagnaraman <sriram.yagnaraman@ericsson.com>
Cc: <dev@dpdk.org>, <xavier.guillaume@ovhcloud.com>,
<robin.l.lin@ericsson.com>
Subject: Re: [PATCH v3] net/af_packet: add multi-segment mbuf support for jumbo frames
Date: Thu, 12 Mar 2026 09:34:56 -0700 [thread overview]
Message-ID: <20260312093456.5d4d2f48@phoenix.local> (raw)
In-Reply-To: <20260312073403.4018157-1-sriram.yagnaraman@ericsson.com>
On Thu, 12 Mar 2026 08:34:03 +0100
Sriram Yagnaraman <sriram.yagnaraman@ericsson.com> wrote:
> Enable jumbo frame reception with default mbuf data room size by
> chaining multiple mbufs when packet exceeds single mbuf tailroom.
>
> Scatter Rx is only enabled when RTE_ETH_RX_OFFLOAD_SCATTER is
> requested. Packets are dropped if they exceed single mbuf size
> and scatter is not enabled, or if mbuf allocation fails during
> chaining. Error counter rx_dropped_pkts tracks all drops.
>
> This allows receiving 9KB jumbo frames using standard 2KB mbufs,
> chaining ~5 segments per jumbo packet.
> ---
Project does not accept patches without DCO (ie. Signed-off-by)
next prev parent reply other threads:[~2026-03-12 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 7:34 [PATCH v3] net/af_packet: add multi-segment mbuf support for jumbo frames Sriram Yagnaraman
2026-03-12 16:06 ` Stephen Hemminger
2026-03-12 16:34 ` Stephen Hemminger [this message]
2026-03-13 9:10 ` [PATCH v4] " Sriram Yagnaraman
2026-03-18 9:47 ` [PATCH v5] " Sriram Yagnaraman
2026-03-23 23:42 ` Stephen Hemminger
2026-03-24 16:29 ` [PATCH v6] net/af_packet: add Rx scatter " Sriram Yagnaraman
2026-03-25 17:31 ` Stephen Hemminger
2026-03-26 13:01 ` Sriram Yagnaraman
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=20260312093456.5d4d2f48@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=robin.l.lin@ericsson.com \
--cc=sriram.yagnaraman@ericsson.com \
--cc=xavier.guillaume@ovhcloud.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