From: Uladzislau Rezki <urezki@gmail.com>
To: Shivam Kalra <shivamkalra98@zohomail.in>
Cc: Danilo Krummrich <dakr@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
aliceryhl@google.com
Subject: Re: [RFC] mm/vmalloc: vrealloc() shrink TODO - seeking direction before implementing
Date: Mon, 2 Mar 2026 10:12:12 +0100 [thread overview]
Message-ID: <aaVUbJ8is-9hYeEe@pc636> (raw)
In-Reply-To: <7d65b7a0-9bc3-4fb6-b25f-58b0e07c2ad8@zohomail.in>
Hello, Shivam!
> On 19/02/26 22:31, Danilo Krummrich wrote:
> > (Cc: Alice)
> >
> > On Thu Feb 19, 2026 at 5:57 PM CET, Uladzislau Rezki wrote:
> >> I think we have 0 users of vrealloc(). It was added because of Rust folk
> >> wanted this.
> >
> > We just gained a user with the Rust binder driver.
> Hi Uladzislau,
>
> You mentioned concerns about there being no users and added complexity.
> The Rust binder driver has a user of kvrealloc for long-lived resizable
> arrays. I also have a patch series adding shrink_to support for these
> allocations, which is now in char-misc-testing [1].
>
> Given that there's now an active use case, I'd like to go ahead with
> implementing the vrealloc shrink as described in the RFC- in-place tail
> page freeing, skipping huge-page allocations. Happy to adjust the
> approach based on your input.
>
> [1]
> https://lore.kernel.org/all/20260216-binder-shrink-vec-v3-v6-0-ece8e8593e53@zohomail.in/
>
Go ahead. Send out a path then we will see what we have.
--
Uladzislau Rezki
prev parent reply other threads:[~2026-03-02 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 23:06 Shivam Kalra
2026-02-19 16:57 ` Uladzislau Rezki
2026-02-19 17:01 ` Danilo Krummrich
2026-02-20 8:01 ` Alice Ryhl
2026-02-27 17:20 ` Shivam Kalra
2026-03-02 9:12 ` Uladzislau Rezki [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=aaVUbJ8is-9hYeEe@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=linux-mm@kvack.org \
--cc=shivamkalra98@zohomail.in \
/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