From: "Morten Brørup" <mb@smartsharesystems.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, dev@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: [RFC PATCH 0/2] mempool: de-inline get/put objects unlikely code
Date: Mon, 16 Feb 2026 11:58:11 +0000 [thread overview]
Message-ID: <20260216115813.103515-1-mb@smartsharesystems.com> (raw)
Reduced compiled code footprint by de-inlining unlikely
code paths.
Morten Brørup (2):
mempool: simplify get objects
mempool: de-inline get/put objects unlikely code paths
lib/mempool/rte_mempool.c | 153 +++++++++++++++++++++++++
lib/mempool/rte_mempool.h | 229 +++++++++++++++++---------------------
2 files changed, 258 insertions(+), 124 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-16 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:58 Morten Brørup [this message]
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
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=20260216115813.103515-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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