From: "Morten Brørup" <mb@smartsharesystems.com>
To: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ivan Malov <ivan.malov@arknetworks.am>,
Chengwen Feng <fengchengwen@huawei.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: [PATCH v4 0/3] mbuf: simplify handling of reinitialized mbufs
Date: Thu, 21 Aug 2025 14:25:41 +0000 [thread overview]
Message-ID: <20250821142544.16211-1-mb@smartsharesystems.com> (raw)
This series contains three changes:
- sanity checking a reinitialized mbuf (a.k.a. raw mbuf) was de-inlined
- reinitialized mbuf free and alloc bulk functions were promoted as stable
- resetting fields of reinitialized mbufs was simplified, so fields that
are already reset are not reset again
Morten Brørup (3):
mbuf: de-inline sanity checking a reinitialized mbuf
mbuf: promote raw free and alloc bulk functions as stable
mbuf: no need to reset all fields on reinitialized mbufs
lib/mbuf/rte_mbuf.c | 61 +++++++++++++++++++
lib/mbuf/rte_mbuf.h | 141 ++++++++++++++++++++++++++++----------------
2 files changed, 150 insertions(+), 52 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-21 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 14:25 Morten Brørup [this message]
2025-08-21 14:25 ` [PATCH v4 1/3] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-08-21 14:25 ` [PATCH v4 2/3] promote reinitialized mbuf free and alloc bulk functions as stable Morten Brørup
2025-08-21 14:25 ` [PATCH v4 3/3] mbuf: no need to reset all fields on reinitialized mbufs Morten Brørup
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=20250821142544.16211-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ivan.malov@arknetworks.am \
--cc=konstantin.ananyev@huawei.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).