From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, techboard@dpdk.org,
Bruce Richardson <bruce.richardson@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
stable@dpdk.org
Subject: Re: [PATCH] ethdev: fix mbuf fast release requirements description
Date: Thu, 5 Feb 2026 09:41:09 -0800 [thread overview]
Message-ID: <20260205094109.07193182@phoenix.local> (raw)
In-Reply-To: <20260205092848.36435-1-mb@smartsharesystems.com>
On Thu, 5 Feb 2026 09:28:48 +0000
Morten Brørup <mb@smartsharesystems.com> wrote:
> It was unclear if mbuf fast release could support segmented packets, or if
> mbuf fast release required non-segmented packets.
> This has now been investigated in detail, and it was concluded that
> segmented packets can be supported with mbuf fast release still achieving
> the enhanced performance.
> So the description of the mbuf fast release Tx offload flag was fixed.
>
> Furthermore, the general descriptions of the Rx and Tx offloads were
> improved, to reflect that they are not only for device capability
> reporting, but also for device and queue configuration purposes.
>
> NB: If a driver does not support segmented packets with mbuf fast release,
> it can check the multi segment send flag when selecting transmit function.
>
> Fixes: 55624173bacb ("mbuf: add raw free and alloc bulk functions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> ---
> The other description improvements were taken from patch-155635 ("[v3,2/3]
> ethdev: Improve descriptions of RX and TX offloads").
> ---
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
I wonder if it would be good to point the AI documentation review
tool at the docbook comments in ethdev. There are some grammar
and clarity errors there.
next prev parent reply other threads:[~2026-02-05 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 9:28 [PATCH] ethdev: fix mbuf fast release requirements description Morten Brørup
2026-02-05 17:41 ` Stephen Hemminger [this message]
2026-02-17 6:56 ` Andrew Rybchenko
2026-02-10 0:13 ` Stephen Hemminger
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=20260205094109.07193182@phoenix.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--cc=techboard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.