[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgjatYenX_xPvRW11BnRw1wP_G19eY-7AqUctnuZ3rGBYA@mail.gmail.com>
Date: Fri, 25 Jul 2025 09:14:05 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Vitaly Wool <vitaly.wool@...sulko.se>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Uladzislau Rezki <urezki@...il.com>,
Danilo Krummrich <dakr@...nel.org>, Vlastimil Babka <vbabka@...e.cz>, rust-for-linux@...r.kernel.org,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, "Liam R . Howlett" <Liam.Howlett@...cle.com>,
Kent Overstreet <kent.overstreet@...ux.dev>, linux-bcachefs@...r.kernel.org,
bpf@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>,
Jann Horn <jannh@...gle.com>, Pedro Falcato <pfalcato@...e.de>
Subject: Re: [PATCH v13 0/4] support large align and nid in Rust allocators
On Thu, Jul 24, 2025 at 10:54 PM Andrew Morton
<akpm@...ux-foundation.org> wrote:
>
> On Tue, 15 Jul 2025 15:56:45 +0200 Vitaly Wool <vitaly.wool@...sulko.se> wrote:
>
> > The coming patches provide the ability for Rust allocators to set
> > NUMA node and large alignment.
> >
> > ...
> >
> > fs/bcachefs/darray.c | 2 -
> > fs/bcachefs/util.h | 2 -
> > include/linux/bpfptr.h | 2 -
> > include/linux/slab.h | 39 ++++++++++++++++++++++---------------
> > include/linux/vmalloc.h | 12 ++++++++---
> > lib/rhashtable.c | 4 +--
> > mm/nommu.c | 3 +-
> > mm/slub.c | 64 +++++++++++++++++++++++++++++++++++++++++--------------------
> > mm/vmalloc.c | 29 ++++++++++++++++++++++-----
> > rust/helpers/slab.c | 10 +++++----
> > rust/helpers/vmalloc.c | 5 ++--
> > rust/kernel/alloc.rs | 54 ++++++++++++++++++++++++++++++++++++++++++++++-----
> > rust/kernel/alloc/allocator.rs | 49 +++++++++++++++++++++-------------------------
> > rust/kernel/alloc/kbox.rs | 4 +--
> > rust/kernel/alloc/kvec.rs | 11 ++++++++--
> > 15 files changed, 200 insertions(+), 90 deletions(-)
>
> I assume we're looking for a merge into mm.git?
>
> We're at -rc7 so let's target 6.17. Please resend around the end of
> the upcoming merge window?
I think it would make sense for this to land through mm.git, so yes
that sounds like a good plan.
Alice
Powered by blists - more mailing lists