From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>, dev@dpdk.org
Cc: "Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Yogaraj Baskaravel" <yogaraj.baskaravel@ericsson.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Bruce Richardson" <bruce.richardson@intel.com>
Subject: RE: [RFC v4 0/3] lib/fastmem: fast small-object allocator
Date: Mon, 10 Aug 2026 18:09:59 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F659D1@smartserver.smartshare.dk> (raw)
In-Reply-To: <20260530092634.46218-1-hofors@lysator.liu.se>
> 3. Per-lcore caches: bounded LIFO stacks (no locks on the hot
> path). Cache misses trigger bulk transfers to/from the shared
> bin under a spinlock.
I haven't looked at the v4 code in detail, so forgive me if my concern is already addressed.
I am worried that a non-EAL thread can be preempted while holding a fastmem lock.
Could this cause an EAL thread to stall in the fastmem lib under the wrong circumstances?
If so, can this be avoided in any way?
The Lock-Free Stack has a solution using single-linked lists and a 128-bit CAS operation.
The solution is quite slow (due to linked list traversal with retry on collision), but progress is practically guaranteed.
next prev parent reply other threads:[~2026-08-10 16:10 UTC|newest]
Thread overview: 39+ 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-06-10 12:35 ` [RFC v4 0/3] lib/fastmem: fast small-object allocator Konstantin Ananyev
2026-08-10 16:09 ` Morten Brørup [this message]
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 ` [RFC " Stephen Hemminger
2026-05-25 19:39 ` 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=98CBD80474FA8B44BF855DF32C47DC35F659D1@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=konstantin.ananyev@huawei.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=stephen@networkplumber.org \
--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.