[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230201091339.61761-6-bhe@redhat.com>
Date: Wed, 1 Feb 2023 17:13:37 +0800
From: Baoquan He <bhe@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, akpm@...ux-foundation.org,
stephen.s.brennan@...cle.com, urezki@...il.com, lstoakes@...il.com,
willy@...radead.org, hch@...radead.org, error27@...il.com,
Baoquan He <bhe@...hat.com>
Subject: [PATCH v4 5/7] mm/vmalloc: skip the uninitilized vmalloc areas
For areas allocated via vmalloc_xxx() APIs, it searches for unmapped area
to reserve and allocates new pages to map into, please see function
__vmalloc_node_range(). During the process, flag VM_UNINITIALIZED is set
in vm->flags to indicate that the pages allocation and mapping haven't
been done, until clear_vm_uninitialized_flag() is called to clear
VM_UNINITIALIZED.
For this kind of area, if VM_UNINITIALIZED is still set, let's ignore
it in vread() because pages newly allocated and being mapped in that
area only contains zero data. reading them out by aligned_vread() is
wasting time.
Signed-off-by: Baoquan He <bhe@...hat.com>
Reviewed-by: Lorenzo Stoakes <lstoakes@...il.com>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@...il.com>
---
mm/vmalloc.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index e515dbacb0cb..504b63606613 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -3667,6 +3667,11 @@ long vread(char *buf, char *addr, unsigned long count)
if (!vm && !flags)
continue;
+ if (vm && (vm->flags & VM_UNINITIALIZED))
+ continue;
+ /* Pair with smp_wmb() in clear_vm_uninitialized_flag() */
+ smp_rmb();
+
vaddr = (char *) va->va_start;
size = vm ? get_vm_area_size(vm) : va_size(va);
--
2.34.1
Powered by blists - more mailing lists