From: Petr Mladek <pmladek@suse.cz>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Tibor Billes <tbilles@gmx.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: rcu: Throttle rcu_try_advance_all_cbs() execution causes visible slowdown in ftrace switching
Date: Tue, 05 Nov 2013 16:43:06 +0100 [thread overview]
Message-ID: <1383666186.27527.57.camel@pathway.suse.cz> (raw)
In-Reply-To: <20131104170232.GS3947@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
Hello Paul,
Paul E. McKenney píše v Po 04. 11. 2013 v 09:02 -0800:
> On Fri, Nov 01, 2013 at 06:19:44PM +0100, Petr Mladek wrote:
> > Hi,
> >
> > I am doing some clean up in x86 ftrace code. I check the performance by
> > switching between different tracers and by enabling and disabling them.
> >
> > The operation has started to be much slower after rebasing on the
> > kernel tip tree. Bisecting has shown that the difference was caused by
> > the commit c229828ca6bc62d6c654 (rcu: Throttle
> > rcu_try_advance_all_cbs() execution)
> This is a slowpath, and that commit did fix a real bug, so I am OK with
> this modest slowdown.
>
> That said, if you have a workload where this is a problem, please try
> building with CONFIG_RCU_FAST_NO_HZ=n. The fact that this commit had any
> effect at all leads me to believe that you used CONFIG_RCU_FAST_NO_HZ=y.
Yes, I used CONFIG_RCU_FAST_NO_HZ=y.
I am not aware of any other workload with this problem. I tried few
benchmarks: dbench, unixbench, and aim. They did not show any
considerable difference with and without the commit. If you are
interested you might find more details in the attached logs.
Just for record, I also checked how the ftrace test was affected by the
commit under various system load. The speed difference was there if at
least one CPU was idle. But the test was slower on idle system even
without the patch. Hence this is not the only change that causes some
difference. See the attached "ftrace" file for more details.
I am still a bit curious why ftrace code is so special here and why it
does not affect the other benchmarks. Anyway, I agree that ftrace
change/start/stop operations are not time critical and the extra delay
might be worth fixing the other bug. I am fine with it :-)
Best Regards,
Petr
[-- Attachment #2: aim9 --]
[-- Type: application/x-gmc-link, Size: 30205 bytes --]
[-- Attachment #3: dbench --]
[-- Type: application/x-gmc-link, Size: 6430 bytes --]
[-- Attachment #4: ftrace --]
[-- Type: text/plain, Size: 2066 bytes --]
test: ftrace
CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
RAM: 4GB
Started using the command:
time ./test-ftrace
Where test-ftrace is:
--- cut ---
#!/bin/bash
echo "Testing ftrace - begin"
cd /sys/kernel/debug/tracing
count=0
while test $count -lt 100 ; do
for tracer in function nop ; do
echo $tracer >current_tracer
echo 1 >tracing_on
echo 0 >tracing_on
done
count=$(($count + 1))
done
cd -
echo "Testing ftrace - end"
--- cut ---
and the load was generated using the script make-load:
--- cut ---
#!/bin/bash
a=1
while true ; do
a=$(($a+1))
done
--- cut ---
Now, results with no load on the system; with the commit c229828ca6bc62d
(rcu: Throttle rcu_try_advance_all_cbs() execution)
real 0m49.393s 0m49.632s 0m49.359
user 0m0.004s 0m0.000s 0m0.004s
sys 0m0.996s 0m0.880s 0m0.892s
and with reverted c229828ca6bc62d (rcu: Throttle rcu_try_advance_all_cbs()
execution)
real 0m35.320s 0m35.687s 0m35.920s
user 0m0.004s 0m0.004s 0m0.000s
sys 0m1.140s 0m1.208s 0m1.152s
---
Results with 100% load on one CPU and no load on 2nd CPU (started the script
make-load once) with c229828ca6bc62d (rcu: Throttle rcu_try_advance_all_cbs()
execution)
real 0m44.964s 0m45.083s 0m45.171s
user 0m0.000s 0m0.000s 0m0.004s
sys 0m1.580s 0m1.612s 0m1.576s
and with reverted c229828ca6bc62d (rcu: Throttle rcu_try_advance_all_cbs()
execution)
real 0m30.816s 0m31.326s 0m31.191s
user 0m0.004s 0m0.004s 0m0.008s
sys 0m1.240s 0m1.248s 0m1.232s
---
Results with 100% load on both CPUs (started script make-load twice)
with c229828ca6bc62d (rcu: Throttle rcu_try_advance_all_cbs() execution)
real 0m20.294s 0m20.538s 0m20.470s
user 0m0.004s 0m0.000s 0m0.000s
sys 0m1.284s 0m1.388s 0m1.612s
and with reverted c229828ca6bc62d (rcu: Throttle rcu_try_advance_all_cbs()
execution)
real 0m20.305s 0m20.056s 0m20.259
user 0m0.000s 0m0.000s 0m0.000s
sys 0m1.416s 0m1.452s 0m1.560s
[-- Attachment #5: unixbench --]
[-- Type: application/x-gmc-link, Size: 4541 bytes --]
next prev parent reply other threads:[~2013-11-05 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 17:19 Petr Mladek
2013-11-04 17:02 ` Paul E. McKenney
2013-11-05 15:43 ` Petr Mladek [this message]
2013-11-05 16:25 ` Paul E. McKenney
2014-08-22 3:35 ` Fengguang Wu
2014-08-22 8:32 ` Petr Mládek
2014-08-22 11:43 ` Fengguang Wu
2014-09-17 14:42 ` Steven Rostedt
2014-09-18 12:45 ` Fengguang Wu
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=1383666186.27527.57.camel@pathway.suse.cz \
--to=pmladek@suse.cz \
--cc=jkosina@suse.cz \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tbilles@gmx.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
all inboxes | Powered by JetHome®