DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, 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>
Subject: Re: [PATCH v8 0/3] mbuf: simplify handling of reinitialized mbufs
Date: Sun, 19 Oct 2025 22:42:21 +0200	[thread overview]
Message-ID: <5540762.F8r316W7xa@thomas> (raw)
In-Reply-To: <20250823063002.24326-1-mb@smartsharesystems.com>

23/08/2025 08:29, Morten Brørup:
> 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 optimized, making the reset
>   operation write-only of the mbuf, instead of read-modify-write
> 
> Morten Brørup (3):
>   mbuf: de-inline sanity checking a reinitialized mbuf
>   mbuf: promote raw free and alloc bulk functions as stable
>   mbuf: optimize reset of reinitialized mbufs

Applied, thanks.

2 notes:
- do you know how much it improves performance?
- it is adding (more or less) new functions directly as stable



      parent reply	other threads:[~2025-10-19 20:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 15:02 [PATCH v5 " Morten Brørup
2025-08-21 15:02 ` [PATCH v5 1/3] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-08-21 15:02 ` [PATCH v5 2/3] promote reinitialized mbuf free and alloc bulk functions as stable Morten Brørup
2025-08-21 15:02 ` [PATCH v5 3/3] mbuf: no need to reset all fields on reinitialized mbufs Morten Brørup
2025-08-22 12:47 ` [PATCH v6 0/3] mbuf: simplify handling of " Morten Brørup
2025-08-22 12:47   ` [PATCH v6 1/3] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-08-22 14:26     ` Morten Brørup
2025-08-22 12:47   ` [PATCH v6 2/3] mbuf: promote raw free and alloc bulk functions as stable Morten Brørup
2025-08-22 12:47   ` [PATCH v6 3/3] mbuf: no need to reset all fields on reinitialized mbufs Morten Brørup
2025-08-22 23:45 ` [PATCH v7 0/3] mbuf: simplify handling of " Morten Brørup
2025-08-22 23:45   ` [PATCH v7 1/3] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-08-22 23:45   ` [PATCH v7 2/3] mbuf: promote raw free and alloc bulk functions as stable Morten Brørup
2025-08-22 23:45   ` [PATCH v7 3/3] mbuf: optimize reset of reinitialized mbufs Morten Brørup
2025-08-23  6:29 ` [PATCH v8 0/3] mbuf: simplify handling " Morten Brørup
2025-08-23  6:30   ` [PATCH v8 1/3] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-10-09 16:49     ` Bruce Richardson
2025-10-09 17:12       ` Morten Brørup
2025-10-09 17:29         ` Thomas Monjalon
2025-10-09 17:55           ` Morten Brørup
2025-10-19 20:22             ` Thomas Monjalon
2025-08-23  6:30   ` [PATCH v8 2/3] mbuf: promote raw free and alloc bulk functions as stable Morten Brørup
2025-10-09 16:53     ` Bruce Richardson
2025-08-23  6:30   ` [PATCH v8 3/3] mbuf: optimize reset of reinitialized mbufs Morten Brørup
2025-08-23 14:28     ` Stephen Hemminger
2025-10-09 17:15     ` Bruce Richardson
2025-10-09 17:35       ` Morten Brørup
2025-10-10  7:43         ` Bruce Richardson
2025-10-10  9:22           ` Morten Brørup
2025-10-19 16:59         ` Thomas Monjalon
2025-10-19 18:45           ` Morten Brørup
2025-10-19 20:45       ` Stephen Hemminger
2025-10-06 14:43   ` [PATCH v8 0/3] mbuf: simplify handling " Morten Brørup
2025-10-19 20:42   ` Thomas Monjalon [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=5540762.F8r316W7xa@thomas \
    --to=thomas@monjalon.net \
    --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=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.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).