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>,
"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>, "Hui Zhu" <hui.zhu@linux.dev>
Subject: Re: [PATCH v13 0/4] support large align and nid in Rust allocators
Date: Fri, 25 Jul 2025 12:00:07 +0200 [thread overview]
Message-ID: <DBL1R8JJ38M1.21F7MRUUUX4U4@kernel.org> (raw)
In-Reply-To: <20250724135449.2cb6457b90926cce1b903481@linux-foundation.org>
(Cc: Hui)
On Thu Jul 24, 2025 at 10:54 PM CEST, Andrew Morton wrote:
> On Tue, 15 Jul 2025 15:56:45 +0200 Vitaly Wool <vitaly.wool@konsulko.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?
Yes, I think that's what we agreed in v1 -- the bits I maintain should carry my
Acked-by already.
> We're at -rc7 so let's target 6.17. Please resend around the end of
> the upcoming merge window?
Yes, this is too late for this cycle. Given that we target the next one, there's
a patch in my queue [1] that interacts with this series.
It would be good if you could pick up [1] (once ready) after this series lands.
I asked Hui to rebase onto this series and Cc you for subsequent submissions for
this purpose.
[1] https://lore.kernel.org/lkml/da9b2afca02124ec14fc9ac7f2a2a85e5be96bc7.1753423953.git.zhuhui@kylinos.cn/
prev parent reply other threads:[~2025-07-25 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:56 [PATCH v13 0/4] support large align and nid in Rust allocators Vitaly Wool
2025-07-15 13:57 ` [PATCH v13 1/4] :mm/vmalloc: allow to set node and align in vrealloc Vitaly Wool
2025-07-15 14:37 ` Matthew Wilcox
2025-07-30 17:25 ` Vitaly Wool
2025-07-15 13:58 ` [PATCH v13 1/4] mm/vmalloc: " Vitaly Wool
2025-07-15 14:25 ` Liam R. Howlett
2025-07-15 13:58 ` [PATCH v13 2/4] mm/slub: allow to set node and align in k[v]realloc Vitaly Wool
2025-07-15 14:33 ` Danilo Krummrich
2025-07-15 15:34 ` Vlastimil Babka
2025-07-15 15:48 ` Danilo Krummrich
2025-07-15 16:12 ` Danilo Krummrich
2025-07-25 8:47 ` Vlastimil Babka
2025-07-15 13:58 ` [PATCH v13 3/4] rust: add support for NUMA ids in allocations Vitaly Wool
2025-07-24 9:27 ` Alice Ryhl
2025-07-29 8:25 ` Danilo Krummrich
2025-07-15 13:58 ` [PATCH v13 4/4] rust: support large alignments " Vitaly Wool
2025-07-24 9:27 ` Alice Ryhl
2025-07-24 20:54 ` [PATCH v13 0/4] support large align and nid in Rust allocators Andrew Morton
2025-07-25 7:14 ` Alice Ryhl
2025-07-25 8:26 ` Vlastimil Babka
2025-07-25 10:00 ` Danilo Krummrich [this message]
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=DBL1R8JJ38M1.21F7MRUUUX4U4@kernel.org \
--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=hui.zhu@linux.dev \
--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 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).