All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vitaly Wool <vitaly.wool@konsulko.se>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Uladzislau Rezki <urezki@gmail.com>,
	Alice Ryhl <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v3 0/2] support large align and nid in Rust allocators
Date: Wed, 25 Jun 2025 23:15:46 +0200	[thread overview]
Message-ID: <aFxnAjUQ2n14D7Ya@cassiopeiae> (raw)
In-Reply-To: <20250625141022.e65e4a9b8377d4879ad7065e@linux-foundation.org>

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

  reply	other threads:[~2025-06-25 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  6:29 [PATCH v3 0/2] support large align and nid in Rust allocators Vitaly Wool
2025-06-25  6:30 ` [PATCH v3 1/2] mm/vmalloc: allow to set node and align in vrealloc Vitaly Wool
2025-06-25  9:58   ` Uladzislau Rezki
2025-06-25  6:30 ` [PATCH v3 2/2] rust: support align and NUMA id in allocations Vitaly Wool
2025-06-25 13:12   ` Boqun Feng
2025-06-25 16:07     ` Uladzislau Rezki
2025-06-25 16:12       ` Boqun Feng
2025-06-25 16:45         ` Uladzislau Rezki
2025-06-25 18:56   ` Danilo Krummrich
2025-06-25 19:07     ` Danilo Krummrich
2025-06-25 20:22       ` Vitaly Wool
2025-06-25 21:20         ` Danilo Krummrich
2025-06-25 21:10 ` [PATCH v3 0/2] support large align and nid in Rust allocators Andrew Morton
2025-06-25 21:15   ` Danilo Krummrich [this message]
2025-06-25 21:34     ` Andrew Morton
2025-06-25 21:36       ` Vitaly Wool

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=aFxnAjUQ2n14D7Ya@cassiopeiae \
    --to=dakr@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=urezki@gmail.com \
    --cc=vitaly.wool@konsulko.se \
    /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.