From: Uladzislau Rezki <urezki@gmail.com>
To: shivamkalra98@zohomail.in
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alice Ryhl <aliceryhl@google.com>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v5 1/3] mm/vmalloc: extract vm_area_free_pages() helper from vfree()
Date: Wed, 18 Mar 2026 18:53:07 +0100 [thread overview]
Message-ID: <abrmgwxireNnqra6@milan> (raw)
In-Reply-To: <20260317-vmalloc-shrink-v5-1-bbfbf54c5265@zohomail.in>
On Tue, Mar 17, 2026 at 01:47:33PM +0530, Shivam Kalra via B4 Relay wrote:
> From: Shivam Kalra <shivamkalra98@zohomail.in>
>
> Extract the page-freeing loop and NR_VMALLOC stat accounting from
> vfree() into a reusable vm_area_free_pages() helper. The helper operates
> on a range [start, end) of pages from a vm_struct, making it suitable
> for both full free (vfree) and partial free (upcoming vrealloc shrink).
>
> Freed page pointers in vm->pages[] are set to NULL to prevent stale
> references when the vm_struct outlives the free (as in vrealloc shrink).
>
> Signed-off-by: Shivam Kalra <shivamkalra98@zohomail.in>
> ---
> mm/vmalloc.c | 47 +++++++++++++++++++++++++++++++++--------------
> 1 file changed, 33 insertions(+), 14 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index c607307c657a..b29bf58c0e3f 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -3416,6 +3416,38 @@ void vfree_atomic(const void *addr)
> schedule_work(&p->wq);
> }
>
> +/*
> + * vm_area_free_pages - free a range of pages from a vmalloc allocation
> + * @vm: the vm_struct containing the pages
> + * @start: first page index to free (inclusive)
> + * @end: last page index to free (exclusive)
> + *
> + * Free pages [start, end) updating NR_VMALLOC stat accounting.
> + * Freed vm->pages[] entries are set to NULL.
> + * Caller is responsible for unmapping (vunmap_range) and KASAN
> + * poisoning before calling this.
> + */
> +static void vm_area_free_pages(struct vm_struct *vm, unsigned int start,
> + unsigned int end)
> +{
> + unsigned int i;
> +
> + for (i = start; i < end; i++) {
> + struct page *page = vm->pages[i];
> +
> + BUG_ON(!page);
> + /*
> + * High-order allocs for huge vmallocs are split, so
> + * can be freed as an array of order-0 allocations
> + */
> + if (!(vm->flags & VM_MAP_PUT_PAGES))
> + mod_lruvec_page_state(page, NR_VMALLOC, -1);
> + __free_page(page);
> + vm->pages[i] = NULL;
> + cond_resched();
> + }
> +}
> +
>
Since you will update second patch, probably you can also improve this
one. To me start/end variables sound like a VA range whereas it is
indices in the array.
Any thoughts?
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-03-18 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 8:17 [PATCH v5 0/3] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra
2026-03-17 8:17 ` Shivam Kalra via B4 Relay
2026-03-17 8:17 ` [PATCH v5 1/3] mm/vmalloc: extract vm_area_free_pages() helper from vfree() Shivam Kalra
2026-03-17 8:17 ` Shivam Kalra via B4 Relay
2026-03-17 14:16 ` Alice Ryhl
2026-03-18 17:53 ` Uladzislau Rezki [this message]
2026-03-20 9:42 ` Shivam Kalra
2026-03-21 8:02 ` Shivam Kalra
2026-03-17 8:17 ` [PATCH v5 2/3] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra
2026-03-17 8:17 ` Shivam Kalra via B4 Relay
2026-03-17 14:39 ` Alice Ryhl
2026-03-17 14:45 ` Danilo Krummrich
2026-03-17 16:01 ` Shivam Kalra
2026-03-17 8:17 ` [PATCH v5 3/3] lib/test_vmalloc: add vrealloc test case Shivam Kalra
2026-03-17 8:17 ` Shivam Kalra via B4 Relay
2026-03-17 21:11 ` [PATCH v5 0/3] mm/vmalloc: free unused pages on vrealloc() shrink Andrew Morton
2026-03-18 8:00 ` Shivam Kalra
2026-03-21 8:15 ` Shivam Kalra
2026-03-21 18:04 ` Andrew Morton
2026-03-22 12:48 ` Alice Ryhl
2026-03-22 14:32 ` Uladzislau Rezki
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=abrmgwxireNnqra6@milan \
--to=urezki@gmail.com \
--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=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 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.