From: Huang Adrian <adrianhuang0701@gmail.com>
To: Baoquan He <bhe@redhat.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 19:19:33 +0800 [thread overview]
Message-ID: <CAHKZfL3YsfSLfNq268p+bikzgwvj+Ng7R09cZQk16aKio3fViw@mail.gmail.com> (raw)
In-Reply-To: <ZqdTK+i9fH/hxB2A@MiWiFi-R3L-srv>
On Mon, Jul 29, 2024 at 4:30 PM Baoquan He <bhe@redhat.com> wrote:
>
> 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
Oh, my fat-finger. Thanks for pointing it out.
I saw that Andrew already added this patch to his mm branch. Let me
know if I need to send the v2 version to fix this typo. (Depend on
Andew's decision)
-- Adrian
next prev parent reply other threads:[~2024-07-29 11:19 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
2024-07-29 11:19 ` Huang Adrian [this message]
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=CAHKZfL3YsfSLfNq268p+bikzgwvj+Ng7R09cZQk16aKio3fViw@mail.gmail.com \
--to=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bhe@redhat.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