From: Uladzislau Rezki <urezki@gmail.com>
To: Baoquan He <bhe@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, urezki@gmail.com,
shivankg@amd.com, vishal.moola@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] mm/vmalloc.c: code cleanup and improvements
Date: Tue, 22 Apr 2025 10:53:10 +0200 [thread overview]
Message-ID: <aAdY9o8TeNi8G8bN@pc638.lan> (raw)
In-Reply-To: <20250418223653.243436-1-bhe@redhat.com>
On Sat, Apr 19, 2025 at 06:36:48AM +0800, Baoquan He wrote:
> These were made from code inspection in mm/vmalloc.c.
>
> v1->v2:
> =======
> - In patch 3:
> - made change to improve code according to Uladzislau's suggestion;
> - use WRITE_ONCE() to assign the value to vn->pool[i].len finally,
> according to Shivank's suggestion.
> In patch 5:
> - add back the WARN_ON_ONCE() on returned value from va_clip()
> invocation, and also add back the code comment. These are pointed
> out by Uladzislau.
>
> - Add reviewers' tag from Uladzislau, Shivank and Vishal. And I only add
> Shivank's tag in patch 1, 2, 4 according to his comment because patch 3
> and 5 are changed in v2.
>
> Baoquan He (5):
> mm/vmalloc.c: change purge_ndoes as local static variable
> mm/vmalloc.c: find the vmap of vmap_nodes in reverse order
> mm/vmalloc.c: optimize code in decay_va_pool_node() a little bit
> mm/vmalloc: optimize function vm_unmap_aliases()
> mm/vmalloc.c: return explicit error value in alloc_vmap_area()
>
> mm/vmalloc.c | 61 ++++++++++++++++++++++++----------------------------
> 1 file changed, 28 insertions(+), 33 deletions(-)
>
> --
> 2.41.0
>
LGTM for whole series:
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Uladzislau Rezki
prev parent reply other threads:[~2025-04-22 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 22:36 Baoquan He
2025-04-18 22:36 ` [PATCH v2 1/5] mm/vmalloc.c: change purge_ndoes as local static variable Baoquan He
2025-04-18 22:36 ` [PATCH v2 2/5] mm/vmalloc.c: find the vmap of vmap_nodes in reverse order Baoquan He
2025-04-18 22:36 ` [PATCH v2 3/5] mm/vmalloc.c: optimize code in decay_va_pool_node() a little bit Baoquan He
2025-04-18 22:36 ` [PATCH v2 4/5] mm/vmalloc: optimize function vm_unmap_aliases() Baoquan He
2025-04-18 22:36 ` [PATCH v2 5/5] mm/vmalloc.c: return explicit error value in alloc_vmap_area() Baoquan He
2025-04-21 4:47 ` Shivank Garg
2025-04-22 8:53 ` 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=aAdY9o8TeNi8G8bN@pc638.lan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shivankg@amd.com \
--cc=vishal.moola@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