From: Ye Liu <ye.liu@linux.dev>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ye Liu <liuye@kylinos.cn>
Subject: Re: [PATCH 2/3] mm/vmalloc: extract vmap_insert_free_area helper
Date: Tue, 15 Sep 2026 10:25:28 +0800 [thread overview]
Message-ID: <fc999f45-fcbc-4d6c-a0b6-2bea4da98013@linux.dev> (raw)
In-Reply-To: <aqgow3u0GSlj0P1Y@milan>
在 2026/9/15 01:02, Uladzislau Rezki 写道:
> On Mon, Sep 14, 2026 at 11:34:01AM +0800, Ye Liu wrote:
>> From: Ye Liu <liuye@kylinos.cn>
>>
>> The allocation and insertion of a free vmap_area is duplicated
>> between the loop body and the tail of vmap_init_free_space. Factor
>> it into a small helper so the main function only deals with computing
>> the free gaps between busy regions.
>>
>> Signed-off-by: Ye Liu <liuye@kylinos.cn>
>> ---
>> mm/vmalloc.c | 41 ++++++++++++++++++-----------------------
>> 1 file changed, 18 insertions(+), 23 deletions(-)
>>
>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>> index 117483dd048c..797933ba9451 100644
>> --- a/mm/vmalloc.c
>> +++ b/mm/vmalloc.c
>> @@ -5433,11 +5433,23 @@ module_init(proc_vmalloc_init);
>>
>> #endif
>>
>> +static void __init vmap_insert_free_area(unsigned long start, unsigned long end)
>> +{
>> + struct vmap_area *free = kmem_cache_zalloc(vmap_area_cachep, GFP_NOWAIT);
>> +
>> + if (!WARN_ON_ONCE(!free)) {
>> + free->va_start = start;
>> + free->va_end = end;
>> + insert_vmap_area_augment(free, NULL,
>> + &free_vmap_area_root,
>> + &free_vmap_area_list);
>> + }
>> +}
>> +
>> static void __init vmap_init_free_space(void)
>> {
>> unsigned long vmap_start = 1;
>> const unsigned long vmap_end = ULONG_MAX;
>> - struct vmap_area *free;
>> struct vm_struct *busy;
>>
>> /*
>> @@ -5447,32 +5459,15 @@ static void __init vmap_init_free_space(void)
>> * |<--------------------------------->|
>> */
>> for (busy = vmlist; busy; busy = busy->next) {
>> - if ((unsigned long) busy->addr - vmap_start > 0) {
>>
> This line gets removed and then re-added below because of removing space
> after (unsigned long). Maybe it is better to keep that space.
However, the '{' is still there, but I'll add a space anyway.
>
>> - free = kmem_cache_zalloc(vmap_area_cachep, GFP_NOWAIT);
>> - if (!WARN_ON_ONCE(!free)) {
>> - free->va_start = vmap_start;
>> - free->va_end = (unsigned long) busy->addr;
>> -
>> - insert_vmap_area_augment(free, NULL,
>> - &free_vmap_area_root,
>> - &free_vmap_area_list);
>> - }
>> - }
>> + if ((unsigned long)busy->addr - vmap_start > 0)
>> + vmap_insert_free_area(vmap_start,
>> + (unsigned long)busy->addr);
>>
>> vmap_start = (unsigned long) busy->addr + busy->size;
>> }
>>
>> - if (vmap_end - vmap_start > 0) {
>> - free = kmem_cache_zalloc(vmap_area_cachep, GFP_NOWAIT);
>> - if (!WARN_ON_ONCE(!free)) {
>> - free->va_start = vmap_start;
>> - free->va_end = vmap_end;
>> -
>> - insert_vmap_area_augment(free, NULL,
>> - &free_vmap_area_root,
>> - &free_vmap_area_list);
>> - }
>> - }
>> + if (vmap_end - vmap_start > 0)
>> + vmap_insert_free_area(vmap_start, vmap_end);
>> }
>>
>> static void vmap_init_nodes(void)
>>
>> --
>> 2.25.1
>>
> LGTM:
>
> Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
>
> --
> Uladzislau Rezki
--
Thanks,
Ye Liu
next prev parent reply other threads:[~2026-09-15 2:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 3:33 [PATCH 0/3] mm/vmalloc: minor cleanups Ye Liu
2026-09-14 3:34 ` [PATCH 1/3] mm/vmalloc: group xa_init with vbq field initializations Ye Liu
2026-09-14 16:57 ` Uladzislau Rezki
2026-09-15 3:52 ` Dev Jain
2026-09-14 3:34 ` [PATCH 2/3] mm/vmalloc: extract vmap_insert_free_area helper Ye Liu
2026-09-14 17:02 ` Uladzislau Rezki
2026-09-15 2:25 ` Ye Liu [this message]
2026-09-15 3:48 ` Dev Jain
2026-09-14 3:34 ` [PATCH 3/3] mm/vmalloc: extract show_busy_info from vmalloc_info_show Ye Liu
2026-09-14 17:10 ` Uladzislau Rezki
2026-09-15 2:26 ` Ye Liu
2026-09-15 4:38 ` Andrew Morton
2026-09-15 4:23 ` Dev Jain
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=fc999f45-fcbc-4d6c-a0b6-2bea4da98013@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--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
all inboxes | Powered by JetHome®