From: Andy Lutomirski <luto@kernel.org>
To: Nicholas Piggin <npiggin@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 0/4] shoot lazy tlbs
Date: Fri, 4 Jun 2021 10:05:01 -0700 [thread overview]
Message-ID: <991660c3-c2bf-c303-a55c-7454f0cc45f7@kernel.org> (raw)
In-Reply-To: <603ffd67-3638-4c47-8067-c1bdfdf65f1b@kernel.org>
On 6/4/21 9:54 AM, Andy Lutomirski wrote:
> On 5/31/21 11:22 PM, Nicholas Piggin wrote:
>> There haven't been objections to the series since last posting, this
>> is just a rebase and tidies up a few comments minor patch rearranging.
>>
>
> I continue to object to having too many modes. I like my more generic
> improvements better. Let me try to find some time to email again.
>
Specifically, this:
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=x86/mm
I, or someone, needs to dust off my membarrier series before any of
these kinds of changes get made. The barrier situation in the scheduler
is too confusing otherwise.
next prev parent reply other threads:[~2021-06-04 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 6:22 [PATCH v3 0/4] shoot lazy tlbs Nicholas Piggin
2021-06-01 6:23 ` [PATCH v3 1/4] lazy tlb: introduce lazy mm refcount helper functions Nicholas Piggin
2021-06-01 6:23 ` [PATCH v3 2/4] lazy tlb: allow lazy tlb mm switching to be configurable Nicholas Piggin
2021-06-01 6:23 ` [PATCH v3 3/4] lazy tlb: shoot lazies, a non-refcounting lazy tlb option Nicholas Piggin
2021-06-01 6:23 ` [PATCH v3 4/4] powerpc/64s: enable MMU_LAZY_TLB_SHOOTDOWN Nicholas Piggin
2021-06-04 16:54 ` [PATCH v3 0/4] shoot lazy tlbs Andy Lutomirski
2021-06-04 17:05 ` Andy Lutomirski [this message]
2021-06-05 0:17 ` Nicholas Piggin
2021-06-05 0:26 ` Nicholas Piggin
2021-06-05 2:52 ` Nicholas Piggin
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=991660c3-c2bf-c303-a55c-7454f0cc45f7@kernel.org \
--to=luto@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).