From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Yogaraj Baskaravel" <yogaraj.baskaravel@ericsson.com>
Subject: Re: [RFC 0/3] lib/fastmem: fast small-object allocator
Date: Mon, 25 May 2026 07:30:29 -0700 [thread overview]
Message-ID: <20260525073029.235b4d40@phoenix.local> (raw)
In-Reply-To: <20260525103642.55255-1-hofors@lysator.liu.se>
On Mon, 25 May 2026 12:36:39 +0200
Mattias Rönnblom <hofors@lysator.liu.se> wrote:
> This RFC introduces fastmem, a general-purpose small-object allocator
> for DPDK. It is intended to replace per-type mempools with a single
> allocator that handles arbitrary sizes, grows on demand, and matches
> mempool-level performance on the hot path.
Makes sense, what a simple wrapper inline to allow full replacement
testing/performance A/B comparison?
next prev parent reply other threads:[~2026-05-25 14:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 10:36 [RFC 0/3] lib/fastmem: fast small-object allocator Mattias Rönnblom
2026-05-25 10:36 ` [RFC 1/3] doc: add fastmem programming guide Mattias Rönnblom
2026-05-25 10:36 ` [RFC 2/3] lib: add fastmem library Mattias Rönnblom
2026-05-27 14:22 ` Stephen Hemminger
2026-05-27 17:25 ` Mattias Rönnblom
2026-05-25 10:36 ` [RFC 3/3] app/test: add fastmem test suite Mattias Rönnblom
2026-05-26 8:57 ` [RFC v2 0/3] lib/fastmem: fast small-object allocator Mattias Rönnblom
2026-05-26 8:57 ` [RFC v2 1/3] doc: add fastmem programming guide Mattias Rönnblom
2026-05-26 8:57 ` [RFC v2 2/3] lib: add fastmem library Mattias Rönnblom
2026-05-26 13:23 ` Stephen Hemminger
2026-05-27 10:12 ` Mattias Rönnblom
2026-05-27 10:18 ` Bruce Richardson
2026-05-27 11:17 ` Mattias Rönnblom
2026-05-27 11:17 ` Morten Brørup
2026-05-27 11:29 ` Mattias Rönnblom
2026-05-27 12:03 ` Morten Brørup
2026-05-26 8:57 ` [RFC v2 3/3] app/test: add fastmem test suite Mattias Rönnblom
2026-05-27 17:30 ` [RFC v3 0/3] lib/fastmem: fast small-object allocator Mattias Rönnblom
2026-05-27 17:30 ` [RFC v3 1/3] doc: add fastmem programming guide Mattias Rönnblom
2026-05-30 9:26 ` [RFC v4 0/3] lib/fastmem: fast small-object allocator Mattias Rönnblom
2026-05-30 9:26 ` [RFC v4 1/3] doc: add fastmem programming guide Mattias Rönnblom
2026-05-30 9:26 ` [RFC v4 2/3] lib: add fastmem library Mattias Rönnblom
2026-05-30 9:26 ` [RFC v4 3/3] app/test: add fastmem test suite Mattias Rönnblom
2026-05-27 17:30 ` [RFC v3 2/3] lib: add fastmem library Mattias Rönnblom
2026-05-28 9:11 ` Morten Brørup
2026-05-28 14:45 ` Varghese, Vipin
2026-05-28 19:56 ` Morten Brørup
2026-05-29 14:29 ` Varghese, Vipin
2026-05-30 16:22 ` Mattias Rönnblom
2026-05-27 17:30 ` [RFC v3 3/3] app/test: add fastmem test suite Mattias Rönnblom
2026-05-28 9:02 ` [RFC v3 0/3] lib/fastmem: fast small-object allocator Morten Brørup
2026-05-25 14:30 ` Stephen Hemminger [this message]
2026-05-25 19:39 ` [RFC " Mattias Rönnblom
2026-05-25 22:18 ` Stephen Hemminger
2026-05-26 7:01 ` Mattias Rönnblom
2026-05-25 18:36 ` Stephen Hemminger
2026-05-25 19:43 ` Mattias Rönnblom
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=20260525073029.235b4d40@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=konstantin.ananyev@huawei.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mb@smartsharesystems.com \
--cc=yogaraj.baskaravel@ericsson.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.