From: Baoquan He <bhe@redhat.com>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2 06/10] mm/vmalloc: Handle non-blocking GFP in __vmalloc_area_node()
Date: Thu, 18 Sep 2025 11:01:37 +0800 [thread overview]
Message-ID: <aMt2EUYD75Wqz1p6@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250915134041.151462-7-urezki@gmail.com>
On 09/15/25 at 03:40pm, Uladzislau Rezki (Sony) wrote:
> Make __vmalloc_area_node() respect non-blocking GFP masks such
> as GFP_ATOMIC and GFP_NOWAIT.
>
> - Add memalloc_apply_gfp_scope()/memalloc_restore_scope()
> helpers to apply a proper scope.
> - Apply memalloc_apply_gfp_scope()/memalloc_restore_scope()
> around vmap_pages_range() for page table setup.
> - Set "nofail" to false if a non-blocking mask is used, as
> they are mutually exclusive.
>
> This is particularly important for page table allocations that
> internally use GFP_PGTABLE_KERNEL, which may sleep unless such
> scope restrictions are applied. For example:
>
> <snip>
> __pte_alloc_kernel()
> pte_alloc_one_kernel(&init_mm);
> pagetable_alloc_noprof(GFP_PGTABLE_KERNEL & ~__GFP_HIGHMEM, 0);
> <snip>
>
> Note: in most cases, PTE entries are established only up to the
> level required by current vmap space usage, meaning the page tables
> are typically fully populated during the mapping process.
>
> Acked-by: Michal Hocko <mhocko@suse.com>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---
> include/linux/vmalloc.h | 2 ++
> mm/vmalloc.c | 52 +++++++++++++++++++++++++++++++++--------
> 2 files changed, 44 insertions(+), 10 deletions(-)
Reviewed-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2025-09-18 3:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 13:40 [PATCH v2 00/10] __vmalloc() and no-block support(v2) Uladzislau Rezki (Sony)
2025-09-15 13:40 ` [PATCH v2 01/10] lib/test_vmalloc: add no_block_alloc_test case Uladzislau Rezki (Sony)
2025-09-15 13:40 ` [PATCH v2 02/10] lib/test_vmalloc: Remove xfail condition check Uladzislau Rezki (Sony)
2025-09-15 13:40 ` [PATCH v2 03/10] mm/vmalloc: Support non-blocking GFP flags in alloc_vmap_area() Uladzislau Rezki (Sony)
2025-09-18 2:56 ` Baoquan He
2025-09-15 13:40 ` [PATCH v2 04/10] mm/vmalloc: Avoid cond_resched() when blocking is not permitted Uladzislau Rezki (Sony)
2025-09-15 17:11 ` Michal Hocko
2025-09-16 15:28 ` Uladzislau Rezki
2025-09-16 18:08 ` Michal Hocko
2025-09-17 5:22 ` Uladzislau Rezki
2025-09-18 2:57 ` Baoquan He
2025-09-15 13:40 ` [PATCH v2 05/10] mm/vmalloc: Defer freeing partly initialized vm_struct Uladzislau Rezki (Sony)
2025-09-18 2:59 ` Baoquan He
2025-09-15 13:40 ` [PATCH v2 06/10] mm/vmalloc: Handle non-blocking GFP in __vmalloc_area_node() Uladzislau Rezki (Sony)
2025-09-18 3:01 ` Baoquan He [this message]
2025-09-15 13:40 ` [PATCH v2 07/10] mm/kasan: Support non-blocking GFP in kasan_populate_vmalloc() Uladzislau Rezki (Sony)
2025-09-18 3:02 ` Baoquan He
2025-09-18 14:56 ` Andrey Ryabinin
2025-09-15 13:40 ` [PATCH v2 08/10] kmsan: Remove hard-coded GFP_KERNEL flags Uladzislau Rezki (Sony)
2025-09-15 13:40 ` [PATCH v2 09/10] mm: Skip might_alloc() warnings when PF_MEMALLOC is set Uladzislau Rezki (Sony)
2025-09-15 17:16 ` Michal Hocko
2025-09-16 15:23 ` Uladzislau Rezki
2025-09-15 13:40 ` [PATCH v2 10/10] mm/vmalloc: Update __vmalloc_node_range() documentation Uladzislau Rezki (Sony)
2025-09-15 17:13 ` Michal Hocko
2025-09-16 15:34 ` Uladzislau Rezki
2025-09-16 0:34 ` kernel test robot
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=aMt2EUYD75Wqz1p6@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--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