From: Baoquan He <bhe@redhat.com>
To: Adrian Huang <adrianhuang0701@gmail.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Uladzislau Rezki <urezki@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Adrian Huang <ahuang12@lenovo.com>,
Jiwei Sun <sunjw10@lenovo.com>
Subject: Re: [PATCH 1/1] mm/vmalloc: Combine all TLB flush operations of KASAN shadow virtual address into one operation
Date: Mon, 29 Jul 2024 16:30:35 +0800 [thread overview]
Message-ID: <ZqdTK+i9fH/hxB2A@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240726165246.31326-1-ahuang12@lenovo.com>
On 07/27/24 at 12:52am, Adrian Huang wrote:
......
> If we combine all TLB flush operations of the KASAN shadow virtual
> address into one operation in the call path
> 'purge_vmap_node()->kasan_release_vmalloc()', the running time of
> drain_vmap_area_work() can be saved greatly. The idea is from the
> flush_tlb_kernel_range() call in __purge_vmap_area_lazy(). And, the
> soft lockup won't not be triggered.
~~~~~~~~~~~
typo
>
> Here is the test result based on 6.10:
>
> [6.10 wo/ the patch]
> 1. ftrace latency profiling (record a trace if the latency > 20s).
> echo 20000000 > /sys/kernel/debug/tracing/tracing_thresh
> echo drain_vmap_area_work > /sys/kernel/debug/tracing/set_graph_function
> echo function_graph > /sys/kernel/debug/tracing/current_tracer
> echo 1 > /sys/kernel/debug/tracing/tracing_on
>
......
> The worst execution time of drain_vmap_area_work() is about 1 second.
>
> Link: https://lore.kernel.org/lkml/ZqFlawuVnOMY2k3E@pc638.lan/
> Fixes: 282631cb2447 ("mm: vmalloc: remove global purge_vmap_area_root rb-tree")
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> Co-developed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> Tested-by: Jiwei Sun <sunjw10@lenovo.com>
> ---
> include/linux/kasan.h | 12 +++++++++---
> mm/kasan/shadow.c | 14 ++++++++++----
> mm/vmalloc.c | 34 ++++++++++++++++++++++++++--------
> 3 files changed, 45 insertions(+), 15 deletions(-)
LGTM,
Reviewed-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2024-07-29 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 16:52 Adrian Huang
2024-07-28 21:18 ` Andrew Morton
2024-07-29 11:12 ` Huang Adrian
2024-07-29 11:29 ` Uladzislau Rezki
2024-07-30 9:36 ` Adrian Huang
2024-07-30 11:38 ` Uladzislau Rezki
2024-07-30 16:27 ` Huang Adrian
2024-07-30 16:42 ` Uladzislau Rezki
2024-07-31 0:39 ` Huang Adrian
2024-07-31 13:38 ` Uladzislau Rezki
2024-07-29 8:30 ` Baoquan He [this message]
2024-07-29 11:19 ` Huang Adrian
2024-07-30 1:18 ` Andrew Morton
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=ZqdTK+i9fH/hxB2A@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hch@infradead.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=sunjw10@lenovo.com \
--cc=urezki@gmail.com \
--cc=vincenzo.frascino@arm.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