From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"open list:READ-COPY UPDATE..." <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/1] rcu: Use rcu_gp_kthread_wake() to wake up kthreads
Date: Sun, 27 Jul 2014 10:19:36 -0700 [thread overview]
Message-ID: <20140727171936.GQ11241@linux.vnet.ibm.com> (raw)
In-Reply-To: <53D2E861.2060000@gmail.com>
On Fri, Jul 25, 2014 at 07:29:37PM -0400, Pranith Kumar wrote:
>
> On 07/25/2014 07:15 PM, Paul E. McKenney wrote:
> > On Fri, Jul 25, 2014 at 06:23:41PM -0400, Pranith Kumar wrote:
> >> Here total is the total number of times we enter th function rcu_report_qs_rsp()
> >> and unnecessary is the times we call wake_up() unnecessarily.
> >> case1, 2, 3 are the cases I listed above.
> >>
> >> Note that the frequency has gone way up than before, I am not sure why that is.
> >>
> >> *ALL* the wakeups seem to be unnecessary from that location. And the
> >> main reason is that gp_flags is 0.
> >>
> >> My rcugp file has the following:
> >>
> >> completed=257515 gpnum=257516 age=1 max=1684
> >>
> >> Thoughts?
> > Hard to believe in the rcutorture case. My guess was that rcutorture was
> > doing about 9000 wakeups, 2000 of which were unnecessary. Which would
> > of course still tilt things very much in favor of your patch.
> >
> > I am not surprised in the mostly-idle case, as the RCU grace-period
> > kthread would most likely be the one ending the grace period, which
> > would therefore almost always be a self-wakeup.
> >
> > Any chance of a peek at your debugging code?
>
> Sure, I am also attaching my dmesg output. Hope it helps!
Looks legit. I guess that having even one CPU idle for the duration
of the grace period will cause a self wakeup, so perhaps I should not
have been surprised.
In any case, please summarize the data down to no more than 30 lines of
text and resend your wakeup-elimination patch with this text included
as the change log.
Thanx, Paul
next prev parent reply other threads:[~2014-07-27 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 5:06 [RFC PATCH 1/1] rcu: Use rcu_gp_kthread_wake() to wake up kthreads Pranith Kumar
2014-07-25 6:24 ` Pranith Kumar
2014-07-25 15:02 ` Paul E. McKenney
2014-07-25 22:23 ` Pranith Kumar
2014-07-25 23:15 ` Paul E. McKenney
2014-07-25 23:29 ` Pranith Kumar
2014-07-27 17:19 ` Paul E. McKenney [this message]
2014-07-25 14:44 ` Paul E. McKenney
2014-07-25 20:19 ` Pranith Kumar
2014-07-25 22:47 ` Paul E. McKenney
2014-07-27 15:55 ` Pranith Kumar
2014-07-27 16:29 ` Paul E. McKenney
2014-07-27 16:44 ` Pranith Kumar
2014-07-27 17:16 ` 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=20140727171936.GQ11241@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.