From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] mbuf: optimize detach direct buffer
Date: Tue, 10 Feb 2026 16:57:37 +0100 [thread overview]
Message-ID: <3780603.PYKUYFuaPT@thomas> (raw)
In-Reply-To: <aVuTD6Ex9k9kXxMu@bricha3-mobl1.ger.corp.intel.com>
05/01/2026 11:31, Bruce Richardson:
> On Sat, Jan 03, 2026 at 05:40:54PM +0000, Morten Brørup wrote:
> > When rte_pktmbuf_prefree_seg() resets an mbuf about to be freed, it
> > 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(-)
> >
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Applied, thanks.
next prev parent reply other threads:[~2026-02-10 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 17:40 [PATCH] mbuf: optimize detach direct buffer Morten Brørup
2026-01-05 10:31 ` Bruce Richardson
2026-02-10 15:57 ` Thomas Monjalon [this message]
2026-01-11 16:01 ` Konstantin Ananyev
-- strict thread matches above, loose matches on Subject: below --
2026-01-03 17:34 Morten Brørup
2026-01-03 17:41 ` 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=3780603.PYKUYFuaPT@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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 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.