From: "Morten Brørup" <mb@smartsharesystems.com>
To: dev@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: [PATCH] mbuf: optimize detach direct buffer
Date: Sat, 3 Jan 2026 17:34:54 +0000 [thread overview]
Message-ID: <20260103173454.121220-1-mb@smartsharesystems.com> (raw)
doesn't write the fields that already have the required values. This
saves a memory store operation when all the fields already have the
required values.
This patch adds the same optimization to __rte_pktmbuf_free_direct(),
to improve the performance for freeing a direct buffer being detached from
a packet mbuf, i.e. saving a memory store operation when all the fields
(of the buffer being freed) already have the required values.
Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
---
lib/mbuf/rte_mbuf.h | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/lib/mbuf/rte_mbuf.h b/lib/mbuf/rte_mbuf.h
index 2004391f57..592af2388c 100644
--- a/lib/mbuf/rte_mbuf.h
+++ b/lib/mbuf/rte_mbuf.h
@@ -1334,17 +1334,23 @@ static inline void
__rte_pktmbuf_free_direct(struct rte_mbuf *m)
{
struct rte_mbuf *md;
+ bool refcnt_not_one;
RTE_ASSERT(RTE_MBUF_CLONED(m));
md = rte_mbuf_from_indirect(m);
- if (rte_mbuf_refcnt_update(md, -1) == 0) {
- md->next = NULL;
- md->nb_segs = 1;
+ refcnt_not_one = unlikely(rte_mbuf_refcnt_read(md) != 1);
+ if (refcnt_not_one && __rte_mbuf_refcnt_update(md, -1) != 0)
+ return;
+
+ if (refcnt_not_one)
rte_mbuf_refcnt_set(md, 1);
- rte_mbuf_raw_free(md);
- }
+ if (md->nb_segs != 1)
+ md->nb_segs = 1;
+ if (md->next != NULL)
+ md->next = NULL;
+ rte_mbuf_raw_free(md);
}
/**
--
2.43.0
next reply other threads:[~2026-01-03 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 17:34 Morten Brørup [this message]
2026-01-03 17:41 ` Morten Brørup
2026-01-03 17:40 Morten Brørup
2026-01-05 10:31 ` Bruce Richardson
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=20260103173454.121220-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=dev@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 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).