linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Mike Galbraith <mgalbraith@suse.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] sched: Make schedstats a runtime tunable that is disabled by default v3
Date: Mon, 1 Feb 2016 14:17:58 +0000	[thread overview]
Message-ID: <20160201141758.GA27318@codeblueprint.co.uk> (raw)
In-Reply-To: <1454319426-2658-1-git-send-email-mgorman@techsingularity.net>

On Mon, 01 Feb, at 09:37:06AM, Mel Gorman wrote:
> Changelog since V2
> o Print stats that are not related to schedstat
> o Reintroduce a static inline for update_stats_dequeue
> 
> Changelog since V1
> o Introduce schedstat_enabled and address Ingo's feedback
> o More schedstat-only paths eliminated, particularly ttwu_stat
> 
> schedstats is very useful during debugging and performance tuning but it
> incurs overhead. As such, even though it can be disabled at build time,
> it is often enabled as the information is useful.  This patch adds a
> kernel command-line and sysctl tunable to enable or disable schedstats on
> demand. It is disabled by default as someone who knows they need it can
> also learn to enable it when necessary.
> 
> The benefits are workload-dependent but when it gets down to it, the
> difference will be whether cache misses are incurred updating the shared
> stats or not. These measurements were taken from a 48-core 2-socket machine
> with Xeon(R) E5-2670 v3 cpus although they were also tested on a single
> socket machine 8-core machine with Intel i7-3770 processors.
 
[...]
 
> The gain is small but it'll depend on the CPU and the workload whether
> this patch makes a different.  However, it stands to reason that doing
> less work in the scheduler is a good thing. The downside is that the
> lack of schedstats and tracepoints will be surprising to experts doing
> performance analysis until they find the existance of the schedstats=
> parameter or schedstats sysctl.
> 
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
> ---
>  Documentation/kernel-parameters.txt |   5 ++
>  Documentation/sysctl/kernel.txt     |   8 +++
>  include/linux/sched/sysctl.h        |   4 ++
>  kernel/sched/core.c                 |  62 +++++++++++++++++++++-
>  kernel/sched/debug.c                | 102 +++++++++++++++++++-----------------
>  kernel/sched/fair.c                 |  90 +++++++++++++++++++------------
>  kernel/sched/sched.h                |   1 +
>  kernel/sched/stats.h                |   8 +--
>  kernel/sysctl.c                     |  11 ++++
>  9 files changed, 204 insertions(+), 87 deletions(-)

Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>

  reply	other threads:[~2016-02-01 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01  9:37 [PATCH 1/1] sched: Make schedstats a runtime tunable that is disabled by default v3 Mel Gorman
2016-02-01 14:17 ` Matt Fleming [this message]
2016-02-02  9:32 ` Srikar Dronamraju
2016-02-02 11:58   ` Mel Gorman
2016-02-02 14:45     ` Srikar Dronamraju
2016-02-03  9:15       ` Mel Gorman

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=20160201141758.GA27318@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgalbraith@suse.de \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).