linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitaly.wool@konsulko.se>
To: Tamir Duberstein <tamird@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, Uladzislau Rezki <urezki@gmail.com>,
	Danilo Krummrich <dakr@kernel.org>,
	Alice Ryhl <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v9 2/4] mm/slub: allow to set node and align in k[v]realloc
Date: Tue, 1 Jul 2025 11:45:33 +0200	[thread overview]
Message-ID: <5B3F6032-1971-439F-8A4B-344B6136A4A2@konsulko.se> (raw)
In-Reply-To: <CAJ-ks9me9i-zkJcZerixEcyxQK764ubL9KQ22kM6B48du_fBig@mail.gmail.com>



> On Jul 1, 2025, at 1:41 AM, Tamir Duberstein <tamird@gmail.com> wrote:
> 
> On Mon, Jun 30, 2025 at 6:16 PM Vitaly Wool <vitaly.wool@konsulko.se> wrote:
>> 
>> Reimplement k[v]realloc_node() to be able to set node and
>> alignment should a user need to do so. In order to do that while
>> retaining the maximal backward compatibility, add
>> k[v]realloc_node_align() functions and redefine the rest of API
>> using these new ones.
>> 
>> With that change we also provide the ability for the Rust part of
>> the kernel to set node and aligmnent in its K[v]xxx
>> [re]allocations.
>> 
>> Signed-off-by: Vitaly Wool <vitaly.wool@konsulko.se>
> 
> The typo (slub) snuck back in.

Bummer. ;)

Thanks for pointing that out. I’ll fix it in the anniversary patchset, hopefully this will be the only thing to fix.

~Vitaly

  reply	other threads:[~2025-07-01  9:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 22:15 [PATCH v9 0/4] support large align and nid in Rust allocators Vitaly Wool
2025-06-30 22:16 ` [PATCH v9 1/4] mm/vmalloc: allow to set node and align in vrealloc Vitaly Wool
2025-07-01 10:50   ` Uladzislau Rezki
2025-07-01 10:54     ` Vitaly Wool
2025-07-01 11:16       ` Uladzislau Rezki
2025-07-01 11:21         ` Vitaly Wool
2025-06-30 22:16 ` [PATCH v9 2/4] mm/slub: allow to set node and align in k[v]realloc Vitaly Wool
2025-06-30 23:41   ` Tamir Duberstein
2025-07-01  9:45     ` Vitaly Wool [this message]
2025-06-30 22:16 ` [PATCH v9 3/4] rust: add support for NUMA ids in allocations Vitaly Wool
2025-07-01 10:34   ` Alice Ryhl
2025-07-01 11:19     ` Vitaly Wool
2025-07-01 11:52       ` Alice Ryhl
2025-06-30 22:16 ` [PATCH v4 4/4] rust: support large alignments " 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=5B3F6032-1971-439F-8A4B-344B6136A4A2@konsulko.se \
    --to=vitaly.wool@konsulko.se \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@gmail.com \
    --cc=urezki@gmail.com \
    /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