From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, dev@dpdk.org
Subject: Re: [RFC PATCH v3 2/2] mempool: de-inline get/put unlikely code paths
Date: Mon, 16 Feb 2026 09:35:42 -0800 [thread overview]
Message-ID: <20260216093542.5dec7c28@phoenix.local> (raw)
In-Reply-To: <20260216152320.105312-3-mb@smartsharesystems.com>
On Mon, 16 Feb 2026 15:23:20 +0000
Morten Brørup <mb@smartsharesystems.com> wrote:
> +/**
> + * @warning
> + * @b EXPERIMENTAL: this API may change without prior notice.
> + *
> + * @internal
> + * Put several objects back in the mempool, more than the cache has room for; used internally.
> + *
> + * @param mp
> + * A pointer to the mempool structure.
> + * @param obj_table
> + * A pointer to a table of void * pointers (objects).
> + * @param n
> + * The number of objects to store back in the mempool, must be strictly
> + * positive.
> + * @param cache
> + * A pointer to a mempool cache structure.
> + */
> +__rte_experimental
> +void
> +_rte_mempool_do_generic_put_more(struct rte_mempool *mp, void * const *obj_table,
> + unsigned int n, struct rte_mempool_cache *cache);
> +
Don't you want internal not experimental on this.
You don't want or expect direct callers.
next prev parent reply other threads:[~2026-02-16 17:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:58 [RFC PATCH 0/2] mempool: de-inline get/put objects unlikely code Morten Brørup
2026-02-16 11:58 ` [RFC PATCH 1/2] mempool: simplify get objects Morten Brørup
2026-02-16 11:58 ` [RFC PATCH 2/2] mempool: de-inline get/put objects unlikely code paths Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 0/2] mempool: de-inline get/put objects unlikely code Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 1/2] mempool: simplify get objects Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 2/2] mempool: de-inline get/put objects unlikely code paths Morten Brørup
2026-02-16 15:23 ` [RFC PATCH v3 0/2] mempool: de-inline get/put " Morten Brørup
2026-02-16 15:23 ` [RFC PATCH v3 1/2] mempool: simplify get objects Morten Brørup
2026-02-17 6:19 ` Andrew Rybchenko
2026-03-13 15:36 ` Morten Brørup
2026-02-16 15:23 ` [RFC PATCH v3 2/2] mempool: de-inline get/put unlikely code paths Morten Brørup
2026-02-16 17:35 ` Stephen Hemminger [this message]
2026-02-16 19:59 ` Morten Brørup
2026-02-17 6:37 ` Andrew Rybchenko
2026-03-13 15:27 ` 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=20260216093542.5dec7c28@phoenix.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox