rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Elijah" <me@elijahs.space>
Cc: "Elijah Wright" <git@elijahs.space>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Uladzislau Rezki" <urezki@gmail.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] rust: slab: add basic slab module
Date: Thu, 25 Sep 2025 20:15:23 +0200	[thread overview]
Message-ID: <DD234804U7YK.3S2MBUJSFHF8J@kernel.org> (raw)
In-Reply-To: <6e9c820f-070b-409e-ac25-af96b8b962c6@elijahs.space>

On Thu Sep 25, 2025 at 8:05 PM CEST, Elijah wrote:
> 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).

Probably, given that kmemcache is meant to be used when we have a lot of (small)
allocations.

However, I'd like to hear from the MM folks, if there may be options in the
existing infrastructure, or if it's really a dead end.

What are the other complex issues you are referring to?

> 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.

I'm not sold on duplicating the Box code just yet. What issues are you referring
to?

  reply	other threads:[~2025-09-25 18:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 19:36 [PATCH] rust: slab: add basic slab module Elijah Wright
2025-09-25  2:17 ` John Hubbard
2025-09-25  8:01 ` Benno Lossin
2025-09-25  9:54 ` Danilo Krummrich
2025-09-25 17:20   ` Elijah
2025-09-25 17:43     ` Danilo Krummrich
2025-09-25 18:02       ` Liam R. Howlett
2025-09-25 18:08         ` Danilo Krummrich
2025-09-25 18:11         ` Boqun Feng
2025-09-25 18:05       ` Elijah
2025-09-25 18:15         ` Danilo Krummrich [this message]
2025-09-25 18:17           ` Danilo Krummrich
     [not found]           ` <74b3ef24-a307-4d3c-891a-8c5283448b20@elijahs.space>
2025-09-25 18:52             ` Elijah
2025-09-25 17:54   ` Alice Ryhl
2025-09-26 15:00   ` Vlastimil Babka
2025-09-26 15:33     ` Danilo Krummrich
2025-09-26 15:55       ` Danilo Krummrich
2025-09-26 16:32         ` Vlastimil Babka
2025-09-26 16:58           ` Danilo Krummrich
2025-09-26 17:11             ` Vlastimil Babka
2025-09-26 19:01               ` Danilo Krummrich
2025-09-28 14:47   ` Danilo Krummrich
2025-09-29  7:14     ` Vlastimil Babka
2025-09-29 14:11     ` Elijah
2025-09-29 20:32       ` Danilo Krummrich
2025-10-01  4:44 ` [PATCH v2] " Elijah Wright
2025-11-06  7:53   ` Alice Ryhl

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=DD234804U7YK.3S2MBUJSFHF8J@kernel.org \
    --to=dakr@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=git@elijahs.space \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lossin@kernel.org \
    --cc=me@elijahs.space \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=urezki@gmail.com \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).