From: Danilo Krummrich <dakr@kernel.org>
To: Vitaly Wool <vitaly.wool@konsulko.se>
Cc: linux-mm@kvack.org, akpm@linux-foundation.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 2/2] rust: support align and NUMA id in allocations
Date: Wed, 25 Jun 2025 23:20:45 +0200 [thread overview]
Message-ID: <aFxoLQnfZ8LbNpYF@cassiopeiae> (raw)
In-Reply-To: <C349F54D-348D-44FE-A02F-E75C78608734@konsulko.se>
On Wed, Jun 25, 2025 at 10:22:36PM +0200, Vitaly Wool wrote:
> I can move this logic to the Rust part, too. My point here is, for Kvrealloc with a large alignment we’ll just make the decision to use vmalloc, period. We can indeed do that on the Rust side.
That's fine with me.
But please also make sure to properly support NUMA nodes for all allocator
backends.
next prev parent reply other threads:[~2025-06-25 21:20 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 [this message]
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
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=aFxoLQnfZ8LbNpYF@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 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).