From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Ivan Malov" <ivan.malov@arknetworks.am>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH v3] mbuf: de-inline sanity checking a reinitialized mbuf
Date: Mon, 11 Aug 2025 08:38:36 -0700 [thread overview]
Message-ID: <20250811083836.7d0e96a7@hermes.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FE21@smartserver.smartshare.dk>
On Mon, 11 Aug 2025 12:06:44 +0200
Morten Brørup <mb@smartsharesystems.com> wrote:
> PING for review.
>
> I think it would be good to get this patch merged early on.
>
> We should also consider upgrading the status of the rte_mbuf_raw_alloc/free_bulk() inline functions from experimental to stable, so they can be used by ethdev drivers instead of rte_mempool_get/put_bulk().
>
> -Morten
Yes.
Actually almost all experimental API's should become stable in 25.11.
Experimental tag is not meant to be permanent.
next prev parent reply other threads:[~2025-08-11 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 10:23 [PATCH] mbuf: de-inline sanity checking a reinitialized mbuf Morten Brørup
2025-07-19 14:14 ` Morten Brørup
2025-07-19 22:30 ` Ivan Malov
2025-07-20 9:25 ` Morten Brørup
2025-07-20 13:09 ` Ivan Malov
2025-07-21 15:00 ` Stephen Hemminger
2025-07-20 20:49 ` [PATCH v2] " Morten Brørup
2025-07-22 9:34 ` [PATCH v3] " Morten Brørup
2025-07-26 12:01 ` Andrew Rybchenko
2025-08-11 10:06 ` Morten Brørup
2025-08-11 15:38 ` Stephen Hemminger [this message]
2025-08-15 14:52 ` Konstantin Ananyev
2025-08-21 14:30 ` 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=20250811083836.7d0e96a7@hermes.local \
--to=stephen@networkplumber.org \
--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=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 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.