From: Nadav Amit <namit@vmware.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Xu <peterx@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Yu Zhao <yuzhao@google.com>,
Nick Piggin <npiggin@gmail.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3 0/5] mm/mprotect: avoid unnecessary TLB flushes
Date: Fri, 11 Mar 2022 18:40:48 +0000 [thread overview]
Message-ID: <FA3620A4-8633-4AAC-B35F-F0040477613F@vmware.com> (raw)
In-Reply-To: <20220309134046.31a0751523acb9babb55b9de@linux-foundation.org>
> On Mar 9, 2022, at 1:40 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 8 Mar 2022 20:10:38 -0800 Nadav Amit <nadav.amit@gmail.com> wrote:
>
>> This patch-set is intended to remove unnecessary TLB flushes during
>> mprotect() syscalls. Once this patch-set make it through, similar
>> and further optimizations for MADV_COLD and userfaultfd would be
>> possible.
>
> Thanks. I'll save this away for consideration after the -rc1 release.
> Which gives others plenty of time for review (hint) (request).
>
I see that some patches did not make it through to the mailing list.
I will resend later today.
prev parent reply other threads:[~2022-03-11 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220309041043.302261-1-namit@vmware.com>
2022-03-09 4:10 ` [PATCH v3 2/5] x86/mm: check exec permissions on fault Nadav Amit
2022-03-09 4:10 ` [PATCH v3 3/5] mm/mprotect: use mmu_gather Nadav Amit
2022-03-09 4:10 ` [PATCH v3 5/5] mm: avoid unnecessary flush on change_huge_pmd() Nadav Amit
2022-03-09 21:40 ` [PATCH v3 0/5] mm/mprotect: avoid unnecessary TLB flushes Andrew Morton
2022-03-11 18:40 ` Nadav Amit [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=FA3620A4-8633-4AAC-B35F-F0040477613F@vmware.com \
--to=namit@vmware.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=npiggin@gmail.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yuzhao@google.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