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 07:24:44 +0200 [thread overview]
Message-ID: <1493011484.4166.13.camel@gmx.de> (raw)
In-Reply-To: <20170424033250.GX3956@linux.vnet.ibm.com>
On Sun, 2017-04-23 at 20:32 -0700, Paul E. McKenney wrote:
> On Mon, Apr 24, 2017 at 04:48:09AM +0200, Mike Galbraith wrote:
> > Greetings,
> >
> > Running Steven's hotplug stress script in tip w. CLASSIC_SRCU takes 55s
> > in my i4790 box, whereas TREE_SRCU takes over 16m. (Master with the
> > same config does it in 39s.. but then lockdep isn't enabled in master)
>
> That doesn't sound good...
>
> But exactly which version are you using? There were some 8x slowdowns
> earlier this week that have since been fixed. Also, how many CPUs are
> on your system?
4 cores+SMT, tip.yesterday_afternoon (precise!) was initial test point,
tip.this_morning (v4.11-rc7-955-g76f8909e1cd8) is still slow.
-Mike
next prev parent reply other threads:[~2017-04-24 5:24 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 [this message]
2017-04-24 6:22 ` Paul E. McKenney
2017-04-24 7:35 ` Mike Galbraith
2017-04-24 8:43 ` Mike Galbraith
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=1493011484.4166.13.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 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.