From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
sbw@mit.edu
Subject: Re: [PATCH RFC tip/core/rcu] Parallelize and economize NOCB kthread wakeups
Date: Wed, 2 Jul 2014 10:55:01 -0700 [thread overview]
Message-ID: <20140702175501.GW4603@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140702172600.GR19379@twins.programming.kicks-ass.net>
On Wed, Jul 02, 2014 at 07:26:00PM +0200, Peter Zijlstra wrote:
> On Wed, Jul 02, 2014 at 10:08:38AM -0700, Paul E. McKenney wrote:
> > As were others, not that long ago. Today is the first hint that I got
> > that you feel otherwise. But it does look like the softirq approach to
> > callback processing needs to stick around for awhile longer. Nice to
> > hear that softirq is now "sane and normal" again, I guess. ;-)
>
> Nah, softirqs are still totally annoying :-)
Name me one thing that isn't annoying. ;-)
> So I've lost detail again, but it seems to me that on all CPUs that are
> actually getting ticks, waking tasks to process the RCU state is
> entirely over doing it. Might as well keep processing their RCU state
> from the tick as was previously done.
And that is in fact the approach taken by my patch. For which I just
kicked off testing, so expect an update later today. (And that -is-
optimistic! A pessimistic viewpoint would hold that the patch would
turn out to be so broken that it would take -weeks- to get a fix!)
Thanx, Paul
next prev parent reply other threads:[~2014-07-02 17:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:20 [PATCH RFC tip/core/rcu] Parallelize and economize NOCB kthread wakeups Paul E. McKenney
2014-06-27 15:01 ` Mathieu Desnoyers
2014-06-27 15:13 ` Mathieu Desnoyers
2014-06-27 15:21 ` Paul E. McKenney
2014-06-27 15:19 ` Paul E. McKenney
2014-07-02 12:34 ` Peter Zijlstra
2014-07-02 13:46 ` Rik van Riel
2014-07-02 16:55 ` Paul E. McKenney
2014-07-03 2:53 ` Paul E. McKenney
2014-07-02 15:39 ` Paul E. McKenney
2014-07-02 16:04 ` Peter Zijlstra
2014-07-02 17:08 ` Paul E. McKenney
2014-07-02 17:26 ` Peter Zijlstra
2014-07-02 17:29 ` Rik van Riel
2014-07-02 17:57 ` Paul E. McKenney
2014-07-03 9:49 ` Peter Zijlstra
2014-07-02 17:55 ` Paul E. McKenney [this message]
2014-07-03 9:50 ` Peter Zijlstra
2014-07-08 13:19 ` Paul E. McKenney
2014-07-03 13:12 ` Peter Zijlstra
2014-07-08 13:44 ` Paul E. McKenney
2014-07-03 3:31 ` Mike Galbraith
2014-07-03 5:21 ` Paul E. McKenney
2014-07-03 5:48 ` Mike Galbraith
2014-07-03 16:29 ` Paul E. McKenney
2014-07-04 3:23 ` Mike Galbraith
2014-07-04 5:05 ` Paul E. McKenney
2014-07-04 6:01 ` Mike Galbraith
2014-07-04 21:20 ` Paul E. McKenney
2014-07-05 13:04 ` Frederic Weisbecker
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=20140702175501.GW4603@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=niv@us.ibm.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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