From: "Danilo Krummrich" <dakr@kernel.org>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: <shivamkalra98@zohomail.in>,
"Shivam Kalra via B4 Relay"
<devnull+shivamkalra98.zohomail.in@kernel.org>,
"Uladzislau Rezki" <urezki@gmail.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH v8 0/6] mm/vmalloc: free unused pages on vrealloc() shrink
Date: Fri, 27 Mar 2026 20:31:16 +0100 [thread overview]
Message-ID: <DHDTC0KLR9FH.3F9GCS0Y7FNRY@kernel.org> (raw)
In-Reply-To: <20260327113758.75f04588310a707b4d4b1aac@linux-foundation.org>
On Fri Mar 27, 2026 at 7:37 PM CET, Andrew Morton wrote:
> Are we able to describe how much memory this change might save under
> various scenarios? If the savings are impressively large then that
> would get attention.
We already have a workaround in place for shrinking vmalloc buffers through a
deep copy in Rust alloc.
Given that binder, which motivated this workaround, uses it already, it suggests
that the savings are significant enough to accept this overhead (I assume Alice
has some numbers).
So, I assume the more interesting question would be how badly the deep copy
hurts binder compared to unmapping and freeing spare pages.
prev parent reply other threads:[~2026-03-27 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 9:48 [PATCH v8 0/6] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 1/6] mm/vmalloc: extract vm_area_free_pages() helper from vfree() Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 2/6] mm/vmalloc: fix vrealloc() grow-in-place check Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 3/6] mm/vmalloc: zero newly exposed memory on vrealloc() grow Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 4/6] mm/vmalloc: use READ_ONCE() for vmalloc nr_pages status readers Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 5/6] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra via B4 Relay
2026-03-27 9:48 ` [PATCH v8 6/6] lib/test_vmalloc: add vrealloc test case Shivam Kalra via B4 Relay
2026-03-27 18:37 ` [PATCH v8 0/6] mm/vmalloc: free unused pages on vrealloc() shrink Andrew Morton
2026-03-27 19:31 ` 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=DHDTC0KLR9FH.3F9GCS0Y7FNRY@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=devnull+shivamkalra98.zohomail.in@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shivamkalra98@zohomail.in \
--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