mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: rcu: Throttle rcu_try_advance_all_cbs() execution causes visible slowdown in ftrace switching
Date: Fri, 01 Nov 2013 18:19:44 +0100	[thread overview]
Message-ID: <1383326384.6788.49.camel@pathway.suse.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

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)

The following times are from Intel 2xCore i7-3770 CPU @ 3.40GHz when
calling the attached test script (time ./test-ftrace). It 100x switches
between "function" and "nop" tracer. It also enables and disables the
tracer each time.

Results with the commit c229828ca6bc62d6c654:

real    0m49.393s     0m49.632s     0m49.359s
user    0m0.004s      0m0.000s      0m0.004s
sys     0m0.996s      0m0.880s      0m0.892s


Results after reverting the commit c229828ca6bc62d6c654:

real    0m35.320s     0m35.687s     0m35.920s
user    0m0.004s      0m0.004s      0m0.000s
sys     0m1.140s      0m1.208s      0m1.152s


I might do some more debugging on Monday. I wonder if you have any
hints or ideas.

Best Regards,
Petr

[-- Attachment #2: test-ftrace --]
[-- Type: application/x-shellscript, Size: 318 bytes --]

             reply	other threads:[~2013-11-01 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 17:19 Petr Mladek [this message]
2013-11-04 17:02 ` Paul E. McKenney
2013-11-05 15:43   ` Petr Mladek
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=1383326384.6788.49.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

Powered by JetHome