From: Mike Galbraith <efault@gmx.de>
To: paulmck@linux.vnet.ibm.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: TREE_SRCU slows hotplug by factor ~16
Date: Mon, 24 Apr 2017 10:43:02 +0200 [thread overview]
Message-ID: <1493023382.6266.9.camel@gmx.de> (raw)
In-Reply-To: <1493019303.4617.6.camel@gmx.de>
On Mon, 2017-04-24 at 09:35 +0200, Mike Galbraith wrote:
> # tracer: nop
> #
> # entries-in-buffer/entries-written: 229332/229332 #P:8
> #
> # _-----=> irqs-off
> # / _----=> need-resched
> # | / _---=> hardirq/softirq
> # || / _--=> preempt-depth
> # ||| / delay
> # TASK-PID CPU# |||| TIMESTAMP FUNCTION
> # | | | |||| | |
> stress-cpu-hotp-2443 [004] .... 144.123608: synchronize_srcu: enter
> stress-cpu-hotp-2443 [004] .... 144.123610: call_srcu: enter
> stress-cpu-hotp-2443 [004] .... 144.123612: call_srcu: exit
> stress-cpu-hotp-2443 [005] .... 144.139528: synchronize_srcu: exit
I probably could have sent a LOT less trace.
classic:
# tracer: nop
#
# entries-in-buffer/entries-written: 114688/114688 #P:8
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
stress-cpu-hotp-4337 [007] .... 174.082801: synchronize_srcu: enter
stress-cpu-hotp-4337 [007] .... 174.082802: synchronize_srcu: exit
stress-cpu-hotp-4337 [007] .... 174.082896: synchronize_srcu: enter
stress-cpu-hotp-4337 [007] .... 174.082896: synchronize_srcu: exit
stress-cpu-hotp-4337 [007] .... 174.082975: synchronize_srcu: enter
stress-cpu-hotp-4337 [007] .... 174.082975: synchronize_srcu: exit
stress-cpu-hotp-4337 [007] .... 174.083051: synchronize_srcu: enter
stress-cpu-hotp-4337 [007] .... 174.083051: synchronize_srcu: exit
....
next prev parent reply other threads:[~2017-04-24 8:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 2:48 TREE_SRCU slows hotplug by factor ~16 Mike Galbraith
2017-04-24 3:32 ` Paul E. McKenney
2017-04-24 5:24 ` Mike Galbraith
2017-04-24 6:22 ` Paul E. McKenney
2017-04-24 7:35 ` Mike Galbraith
2017-04-24 8:43 ` Mike Galbraith [this message]
2017-04-24 16:24 ` Paul E. McKenney
2017-04-25 22:36 ` Paul E. McKenney
2017-04-26 14:31 ` Paul E. McKenney
2017-04-26 15:26 ` Mike Galbraith
2017-04-26 15:44 ` Paul E. McKenney
2017-04-26 15:49 ` Mike Galbraith
2017-04-26 16:00 ` Paul E. McKenney
2017-04-26 17:45 ` Mike Galbraith
2017-04-26 17:55 ` Paul E. McKenney
2017-04-26 17:56 ` Paul E. McKenney
2017-04-26 18:12 ` Mike Galbraith
2017-04-26 18:25 ` Paul E. McKenney
2017-04-27 3:43 ` Mike Galbraith
2017-04-27 4:11 ` Paul E. McKenney
2017-04-27 4:15 ` Mike Galbraith
2017-04-27 5:32 ` Paul E. McKenney
2017-04-27 5:44 ` Mike Galbraith
2017-04-27 12:37 ` 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=1493023382.6266.9.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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