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>,
Vlastimil Babka <vbabka@suse.cz>,
rust-for-linux@vger.kernel.org,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-bcachefs@vger.kernel.org, bpf@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>
Subject: Re: [PATCH v12 3/4] rust: add support for NUMA ids in allocations
Date: Wed, 9 Jul 2025 22:58:16 +0200 [thread overview]
Message-ID: <aG7X6Htx0I6cUqYD@cassiopeiae> (raw)
In-Reply-To: <20250709172458.1032040-1-vitaly.wool@konsulko.se>
On Wed, Jul 09, 2025 at 07:24:58PM +0200, Vitaly Wool wrote:
> Add a new type to support specifying NUMA identifiers in Rust
> allocators and extend the allocators to have NUMA id as a
> parameter. Thus, modify ReallocFunc to use the new extended realloc
> primitives from the C side of the kernel (i. e.
> k[v]realloc_node_align/vrealloc_node_align) and add the new function
> alloc_node to the Allocator trait while keeping the existing one
> (alloc) for backward compatibility.
>
> This will allow to specify node to use for allocation of e. g.
> {KV}Box, as well as for future NUMA aware users of the API.
>
> Signed-off-by: Vitaly Wool <vitaly.wool@konsulko.se>
> +/// Non Uniform Memory Access (NUMA) node identifier
Please end with a period.
> +#[derive(Clone, Copy, PartialEq)]
> +pub struct NumaNode(i32);
> +
> +impl NumaNode {
> + /// create a new NUMA node identifer (non-negative integer)
s/identifer/identifier/
Please also add an empty line in between those two.
> + /// returns EINVAL if a negative id or an id exceeding MAX_NUMNODES is specified
Please start with a capital letter, use markdown and end with a period.
> + pub fn new(node: i32) -> Result<Self> {
> + // SAFETY: MAX_NUMNODES never exceeds 2**10 because NODES_SHIFT is 0..10
This must not be a safety comment, but a normal one. Please use markdown and end
the sentence with a period.
> + if node < 0 || node >= bindings::MAX_NUMNODES as i32 {
> + return Err(EINVAL);
> + }
> + Ok(Self(node))
> + }
> +}
With that fixed,
Acked-by: Danilo Krummrich <dakr@kernel.org>
next prev parent reply other threads:[~2025-07-09 20:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 17:23 [PATCH v12 0/4] support large align and nid in Rust allocators Vitaly Wool
2025-07-09 17:24 ` [PATCH v12 1/4] mm/vmalloc: allow to set node and align in vrealloc Vitaly Wool
2025-07-09 19:01 ` Liam R. Howlett
2025-07-10 6:21 ` Vitaly Wool
2025-07-10 15:09 ` Liam R. Howlett
2025-07-10 15:19 ` Lorenzo Stoakes
2025-07-10 18:57 ` Vitaly Wool
2025-07-10 14:07 ` Vitaly Wool
2025-07-09 22:53 ` Alexei Starovoitov
2025-07-09 22:57 ` Danilo Krummrich
2025-07-09 23:14 ` Alexei Starovoitov
2025-07-09 23:26 ` Danilo Krummrich
2025-07-10 0:39 ` Alexei Starovoitov
2025-07-10 6:16 ` Vitaly Wool
2025-07-10 9:57 ` Danilo Krummrich
2025-07-09 17:24 ` [PATCH v12 2/4] mm/slub: allow to set node and align in k[v]realloc Vitaly Wool
2025-07-10 7:45 ` Vlastimil Babka
2025-07-11 8:58 ` Harry Yoo
2025-07-11 11:11 ` Kent Overstreet
2025-07-11 15:43 ` Vlastimil Babka
2025-07-12 12:43 ` Vitaly Wool
2025-07-14 8:14 ` Vlastimil Babka
2025-07-14 15:27 ` Vitaly Wool
2025-07-15 7:03 ` Alice Ryhl
2025-07-09 17:24 ` [PATCH v12 3/4] rust: add support for NUMA ids in allocations Vitaly Wool
2025-07-09 20:58 ` Danilo Krummrich [this message]
2025-07-09 17:25 ` [PATCH v12 4/4] rust: support large alignments " Vitaly Wool
2025-07-09 21:00 ` Danilo Krummrich
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=aG7X6Htx0I6cUqYD@cassiopeiae \
--to=dakr@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=bpf@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jannh@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=rust-for-linux@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--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.