[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aFxnAjUQ2n14D7Ya@cassiopeiae>
Date: Wed, 25 Jun 2025 23:15:46 +0200
From: Danilo Krummrich <dakr@...nel.org>
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>,
Alice Ryhl <aliceryhl@...gle.com>, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v3 0/2] support large align and nid in Rust allocators
On Wed, Jun 25, 2025 at 02:10:22PM -0700, Andrew Morton wrote:
> On Wed, 25 Jun 2025 08:29:17 +0200 Vitaly Wool <vitaly.wool@...sulko.se> wrote:
>
> > The coming patches provide the ability for Rust allocators to set
> > NUMA node and large alignment.
>
> Including a diffstat would be nice.
>
> include/linux/vmalloc.h | 8 +++---
> mm/nommu.c | 3 +-
> mm/vmalloc.c | 16 ++++++++++--
> rust/helpers/slab.c | 8 ++++--
> rust/helpers/vmalloc.c | 4 +--
> rust/kernel/alloc.rs | 28 ++++++++++++++++++++-
> rust/kernel/alloc/allocator.rs | 40 +++++++++++++++++--------------
> rust/kernel/alloc/kvec.rs | 3 +-
> 8 files changed, 79 insertions(+), 31 deletions(-)
>
> What is the preferred merge path for this series?
I can take it through my Rust alloc tree, but I think it would probably be
better you take it through the mm tree, since I don't expect this to conflict
with anything else in my tree anyways.
The Rust changes gonna need some more discussion though.
- Danilo
Powered by blists - more mailing lists