[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e9c820f-070b-409e-ac25-af96b8b962c6@elijahs.space>
Date: Thu, 25 Sep 2025 11:05:16 -0700
From: Elijah <me@...jahs.space>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Elijah Wright <git@...jahs.space>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, Benno Lossin <lossin@...nel.org>,
Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, "Liam R. Howlett"
<Liam.Howlett@...cle.com>, Uladzislau Rezki <urezki@...il.com>,
linux-mm@...ck.org
Subject: Re: [PATCH] rust: slab: add basic slab module
On 9/25/2025 10:43 AM, Danilo Krummrich wrote:
> Anyways, I'd also like to hear some more opinions, especially
regarding (4), as
> mentioned.
ok I just looked it over. I think (4) isn't really viable, the cache
pointer storage overhead is probably too much (in addition to some
complex issues). I don't really like having a macro (so (3) basically)
and I think there are issues with non-static caches, I don't know
specifically though. obviously (1) doesn't work. (2) is exactly what I
was thinking specifically for rbtree. IMO the only useful options are
(2) and (3). I would say maybe implement (2) first and if you want
macro-generated ZST allocators they can wrap whatever that Box ends up
being.
> not having dynamic dispatch for a
kmemcache backed Box is probably not that big of a deal though
I agree
Powered by blists - more mailing lists