From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <frederic@kernel.org>,
Paul McKenney <paulmck@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [patch V2 7/9] softirq: Replace barrier() with cpu_relax() in tasklet_unlock_wait()
Date: Fri, 04 Dec 2020 18:01:58 +0100 [thread overview]
Message-ID: <20201204170805.430113367@linutronix.de> (raw)
In-Reply-To: 20201204170151.960336698@linutronix.de
From: Thomas Gleixner <tglx@linutronix.de>
A barrier() in a tight loop which waits for something to happen on a remote
CPU is a pointless exercise. Replace it with cpu_relax() which allows HT
siblings to make progress.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
include/linux/interrupt.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -668,7 +668,8 @@ static inline void tasklet_unlock(struct
static inline void tasklet_unlock_wait(struct tasklet_struct *t)
{
- while (test_bit(TASKLET_STATE_RUN, &(t)->state)) { barrier(); }
+ while (test_bit(TASKLET_STATE_RUN, &(t)->state))
+ cpu_relax();
}
#else
#define tasklet_trylock(t) 1
next prev parent reply other threads:[~2020-12-04 17:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 17:01 [patch V2 0/9] softirq: Make it RT aware Thomas Gleixner
2020-12-04 17:01 ` [patch V2 1/9] softirq: Add RT specific softirq accounting Thomas Gleixner
2020-12-07 13:06 ` Frederic Weisbecker
2020-12-04 17:01 ` [patch V2 2/9] irqtime: Make accounting correct on RT Thomas Gleixner
2020-12-07 0:23 ` Frederic Weisbecker
2020-12-07 0:57 ` Thomas Gleixner
2020-12-07 1:14 ` Frederic Weisbecker
2020-12-07 13:27 ` Frederic Weisbecker
2020-12-07 14:44 ` Thomas Gleixner
2020-12-04 17:01 ` [patch V2 3/9] softirq: Move various protections into inline helpers Thomas Gleixner
2020-12-07 13:37 ` Frederic Weisbecker
2020-12-04 17:01 ` [patch V2 4/9] softirq: Make softirq control and processing RT aware Thomas Gleixner
2020-12-07 14:16 ` Frederic Weisbecker
2020-12-07 15:08 ` Thomas Gleixner
2020-12-08 0:08 ` Frederic Weisbecker
2020-12-09 10:11 ` Peter Zijlstra
2020-12-09 12:36 ` Thomas Gleixner
2020-12-09 12:42 ` Peter Zijlstra
2020-12-09 13:30 ` Thomas Gleixner
2020-12-09 10:34 ` Peter Zijlstra
2020-12-04 17:01 ` [patch V2 5/9] tick/sched: Prevent false positive softirq pending warnings on RT Thomas Gleixner
2020-12-08 12:23 ` Frederic Weisbecker
2020-12-04 17:01 ` [patch V2 6/9] rcu: Prevent false positive softirq warning " Thomas Gleixner
2020-12-04 17:59 ` Paul E. McKenney
2020-12-04 17:01 ` Thomas Gleixner [this message]
2020-12-07 11:39 ` [patch V2 7/9] softirq: Replace barrier() with cpu_relax() in tasklet_unlock_wait() Peter Zijlstra
2020-12-07 15:21 ` Thomas Gleixner
2020-12-04 17:01 ` [patch V2 8/9] tasklets: Use static inlines for stub implementations Thomas Gleixner
2020-12-04 17:02 ` [patch V2 9/9] tasklets: Prevent kill/unlock_wait deadlock on RT Thomas Gleixner
2020-12-07 11:47 ` Peter Zijlstra
2020-12-07 14:00 ` Sebastian Andrzej Siewior
2020-12-07 14:27 ` Peter Zijlstra
2020-12-07 17:55 ` Thomas Gleixner
2020-12-07 15:22 ` Thomas Gleixner
2020-12-07 15:39 ` Sebastian Andrzej Siewior
2020-12-07 17:49 ` Thomas Gleixner
2020-12-07 17:50 ` Thomas Gleixner
2020-12-06 10:05 ` [patch V2 0/9] softirq: Make it RT aware Sebastian Andrzej Siewior
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=20201204170805.430113367@linutronix.de \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@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).