From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: linux-kernel@vger.kernel.org, Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] rcu: Enable RCU tracepoints by default to aid in debugging
Date: Fri, 23 Dec 2016 09:16:25 -0800 [thread overview]
Message-ID: <20161223171625.GY3924@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161223151753.22745-1-matt@codeblueprint.co.uk>
On Fri, Dec 23, 2016 at 03:17:53PM +0000, Matt Fleming wrote:
> While debugging a performance issue I needed to understand why
> RCU sofitrqs were firing so frequently.
>
> Unfortunately, the RCU callback tracepoints are hidden behind
> CONFIG_RCU_TRACE which defaults to off in the upstream kernel and is
> likely to also be disabled in enterprise distribution configs.
>
> Enable it by default for CONFIG_TREE_RCU. However, we must keep it
> disabled for tiny RCU, because it would otherwise pull in a large
> amount of code that would make tiny RCU less than tiny.
>
> I ran some file system metadata intensive workloads (git checkout,
> FS-Mark) on a variety of machines with this patch and saw no
> detectable change in performance.
>
> Cc: Mel Gorman <mgorman@techsingularity.net>
> Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
Queued for testing and review, thank you!
Thanx, Paul
> ---
> lib/Kconfig.debug | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index a6c8db1d62f6..7fe1ff001792 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1431,6 +1431,7 @@ config RCU_CPU_STALL_TIMEOUT
> config RCU_TRACE
> bool "Enable tracing for RCU"
> depends on DEBUG_KERNEL
> + default y if TREE_RCU
> select TRACE_CLOCK
> help
> This option provides tracing in RCU which presents stats
> --
> 2.10.0
>
prev parent reply other threads:[~2016-12-23 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 15:17 Matt Fleming
2016-12-23 17:16 ` Paul E. McKenney [this message]
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=20161223171625.GY3924@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
/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