From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
torvalds@linux-foundation.org, oleg@redhat.com,
paulmck@linux.vnet.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, stern@rowland.harvard.edu,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>
Subject: Re: [RFC][PATCH 1/5] mm: Rework {set,clear,mm}_tlb_flush_pending()
Date: Tue, 1 Aug 2017 17:44:14 +0100 [thread overview]
Message-ID: <20170801164414.GB12027@arm.com> (raw)
In-Reply-To: <20170801163903.wuwrk6ysyd52dwxm@hirez.programming.kicks-ass.net>
On Tue, Aug 01, 2017 at 06:39:03PM +0200, Peter Zijlstra wrote:
> Still this is all rather unsatisfactory. Either we should define
> flush_tlb*() to imply a barrier when its not a no-op (sparc64/ppc-hash)
> or simply make clear_tlb_flush_pending() an smp_store_release().
>
> I prefer the latter option.
>
> Opinions?
I prefer the latter option too, since I'd like to relax the arm64 TLB
flushing to have weaker barriers for the local case. Granted, that doesn't
break the NUMA migration code, but it would make the barrier semantics of
the TLB invalidation routines even more subtle if we were to define them
generally.
Will
next prev parent reply other threads:[~2017-08-01 16:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 16:15 [RFC][PATCH 0/5] Getting rid of smp_mb__before_spinlock Peter Zijlstra
2017-06-07 16:15 ` [RFC][PATCH 1/5] mm: Rework {set,clear,mm}_tlb_flush_pending() Peter Zijlstra
2017-06-09 14:45 ` Will Deacon
2017-06-09 18:42 ` Peter Zijlstra
2017-07-28 17:45 ` Peter Zijlstra
2017-08-01 10:31 ` Will Deacon
2017-08-01 12:02 ` Benjamin Herrenschmidt
2017-08-01 12:14 ` Peter Zijlstra
2017-08-01 16:39 ` Peter Zijlstra
2017-08-01 16:44 ` Will Deacon [this message]
2017-08-01 16:48 ` Peter Zijlstra
2017-08-01 22:59 ` Peter Zijlstra
2017-08-02 1:23 ` Benjamin Herrenschmidt
2017-08-02 8:11 ` Peter Zijlstra
2017-08-02 8:15 ` Will Deacon
2017-08-02 8:43 ` Will Deacon
2017-08-02 8:51 ` Peter Zijlstra
2017-08-02 9:02 ` Will Deacon
2017-08-02 22:54 ` Benjamin Herrenschmidt
2017-08-02 8:45 ` Peter Zijlstra
2017-08-02 9:02 ` Will Deacon
2017-08-02 9:18 ` Peter Zijlstra
2017-08-02 13:57 ` Benjamin Herrenschmidt
2017-08-02 15:46 ` Peter Zijlstra
2017-08-02 0:17 ` Benjamin Herrenschmidt
2017-08-01 22:42 ` Benjamin Herrenschmidt
2017-06-07 16:15 ` [RFC][PATCH 2/5] locking: Introduce smp_mb__after_spinlock() Peter Zijlstra
2017-06-07 16:15 ` [RFC][PATCH 3/5] overlayfs: Remove smp_mb__before_spinlock() usage Peter Zijlstra
2017-06-07 16:15 ` [RFC][PATCH 4/5] locking: Remove smp_mb__before_spinlock() Peter Zijlstra
2017-06-07 16:15 ` [RFC][PATCH 5/5] powerpc: Remove SYNC from _switch Peter Zijlstra
2017-06-08 0:32 ` Nicholas Piggin
2017-06-08 6:54 ` Peter Zijlstra
2017-06-08 7:29 ` Nicholas Piggin
2017-06-08 7:57 ` Peter Zijlstra
2017-06-08 8:21 ` Nicholas Piggin
2017-06-08 9:54 ` Michael Ellerman
2017-06-08 10:00 ` Nicholas Piggin
2017-06-08 12:45 ` Peter Zijlstra
2017-06-08 13:18 ` Nicholas Piggin
2017-06-08 13:47 ` Peter Zijlstra
2017-06-09 14:49 ` [RFC][PATCH 0/5] Getting rid of smp_mb__before_spinlock Will Deacon
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=20170801164414.GB12027@arm.com \
--to=will.deacon@arm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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