From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Tetsuya Mukawa <mtetsuyah@gmail.com>,
Vipin Varghese <Vipin.Varghese@amd.com>,
Thiyagarjan P <Thiyagarajan.P@amd.com>,
Ivan Malov <ivan.malov@arknetworks.am>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: Re: [PATCH v4] net/null: Add fast mbuf release TX offload
Date: Mon, 4 Aug 2025 08:39:19 -0700 [thread overview]
Message-ID: <20250804083919.73fc7361@hermes.local> (raw)
In-Reply-To: <20250730140451.622906-1-mb@smartsharesystems.com>
On Wed, 30 Jul 2025 14:04:51 +0000
Morten Brørup <mb@smartsharesystems.com> wrote:
> Added fast mbuf release, re-using the existing mbuf pool pointer
> in the queue structure.
>
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> ---
> v4:
> * Force the generic function called by the separate tx_pkt_burst callbacks
> to be inlined.
> v3:
> * Use separate tx_pkt_burst callbacks depending on per-device TX offload
> configuration. (Ivan Malov, Konstantin Ananyev)
> * Check TX offload configuration for mutually exclusive MBUF_FAST_FREE and
> MULTI_SEGS flags. (Ivan Malov, Konstantin Ananyev)
> * Also announce MULTI_SEGS TX offload as a per-queue capability.
> v2:
> * Also announce the MBUF_FAST_FREE TX offload as a per-queue capability.
> * Added missing test of per-device MBUF_FAST_FREE TX offload configuration
> when configuring the queue.
Queued to next-net for v25.11
prev parent reply other threads:[~2025-08-04 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 18:14 [PATCH] " Morten Brørup
2025-06-26 14:05 ` Stephen Hemminger
2025-06-26 15:44 ` Morten Brørup
2025-06-27 12:07 ` Varghese, Vipin
2025-07-26 4:34 ` Morten Brørup
2025-07-28 8:22 ` Varghese, Vipin
2025-07-26 4:48 ` [PATCH v2] " Morten Brørup
2025-07-26 6:15 ` Ivan Malov
2025-07-28 13:27 ` Morten Brørup
2025-07-28 13:51 ` Ivan Malov
2025-07-28 15:42 ` Konstantin Ananyev
2025-07-28 16:42 ` Morten Brørup
2025-07-30 13:50 ` [PATCH v3] " Morten Brørup
2025-07-30 14:04 ` [PATCH v4] " Morten Brørup
2025-08-04 9:23 ` Varghese, Vipin
2025-08-04 15:39 ` Stephen Hemminger [this message]
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=20250804083919.73fc7361@hermes.local \
--to=stephen@networkplumber.org \
--cc=Thiyagarajan.P@amd.com \
--cc=Vipin.Varghese@amd.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=mtetsuyah@gmail.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).