From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
tglx@linutronix.de, Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH v2] rcu: Allow to eliminate softirq processing from rcutree
Date: Tue, 19 Mar 2019 09:50:07 -0700 [thread overview]
Message-ID: <20190319165007.GB4102@linux.ibm.com> (raw)
In-Reply-To: <20190319162431.4w2dqtssqkx6t4pq@linutronix.de>
On Tue, Mar 19, 2019 at 05:24:31PM +0100, Sebastian Andrzej Siewior wrote:
> On 2019-03-19 08:59:23 [-0700], Paul E. McKenney wrote:
> > I doubt that there is any code left from my original, so I set you as
> > author.
>
> I always forward ported it the patch over the years. So if it is no
> longer what it was once so be it.
Besides, it looks very weird for me to have two Signed-off-by lines. ;-)
> > I queued this and am starting tests without setting rcunosoftirq,
> > and will run more later setting it, courtesy of --bootargs.
>
> oki.
>
> > Steve Rostedt did raise a good question about adding event tracing to
> > the park functions. I haven't really settled on an answer yet. Thoughts?
>
> It should trigger CPU hotplug events. If there was something similar for
> the softirq processing then the threaded processing should also have it.
> Please tell me which one should be added and I'm happy to add one.
In theory, the trace_rcu_utilization() should be added, just like at
the beginning and end of the function rcu_core(), but as far as I know,
no one uses that, so I actually have it on my list to remove.
Thanx, Paul
next prev parent reply other threads:[~2019-03-19 16:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 11:11 [PATCH] rcu: Allow to eliminate softirq processing from rcutree Sebastian Andrzej Siewior
2019-03-15 13:35 ` Steven Rostedt
2019-03-15 13:57 ` Sebastian Andrzej Siewior
2019-03-18 2:24 ` Paul E. McKenney
2019-03-19 11:44 ` [PATCH v2] " Sebastian Andrzej Siewior
2019-03-19 15:59 ` Paul E. McKenney
2019-03-19 16:24 ` Sebastian Andrzej Siewior
2019-03-19 16:50 ` Paul E. McKenney [this message]
2019-03-19 17:02 ` Sebastian Andrzej Siewior
2019-03-20 11:32 ` Sebastian Andrzej Siewior
2019-03-20 15:21 ` Paul E. McKenney
2019-03-20 15:44 ` Paul E. McKenney
2019-03-20 16:05 ` Sebastian Andrzej Siewior
2019-03-20 16:15 ` Paul E. McKenney
2019-03-20 16:35 ` Sebastian Andrzej Siewior
2019-03-20 17:30 ` Paul E. McKenney
2019-03-20 17:59 ` Sebastian Andrzej Siewior
2019-03-20 18:12 ` Paul E. McKenney
2019-03-20 18:14 ` Sebastian Andrzej Siewior
2019-03-20 21:13 ` [PATCH v3] " Sebastian Andrzej Siewior
2019-03-20 23:46 ` Paul E. McKenney
2019-03-21 8:27 ` Sebastian Andrzej Siewior
2019-03-21 13:26 ` Paul E. McKenney
2019-03-21 23:32 ` Paul E. McKenney
2019-03-22 7:35 ` Paul E. McKenney
2019-03-22 12:43 ` Paul E. McKenney
2019-03-22 13:42 ` Joel Fernandes
2019-03-22 14:58 ` Paul E. McKenney
2019-03-22 15:50 ` Joel Fernandes
2019-03-22 16:26 ` Paul E. McKenney
2019-03-22 18:07 ` Paul E. McKenney
2019-03-22 23:48 ` Joel Fernandes
2019-03-23 0:25 ` Paul E. McKenney
2019-03-23 1:04 ` Joel Fernandes
2019-03-23 16:10 ` Paul E. McKenney
2019-03-24 23:42 ` Paul E. McKenney
2019-03-25 13:41 ` Joel Fernandes
2019-03-25 15:08 ` Paul E. McKenney
2019-03-25 15:52 ` Paul E. McKenney
2019-03-20 0:26 ` [PATCH] " Joel Fernandes
2019-03-20 11:28 ` Sebastian Andrzej Siewior
2019-03-21 12:06 ` Joel Fernandes
2019-03-21 13:52 ` Paul E. McKenney
2019-03-20 15:24 ` Paul E. McKenney
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=20190319165007.GB4102@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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