From: Mike Galbraith <mgalbraith@suse.de>
To: Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Make schedstats a runtime tunable that is disabled by default v2
Date: Wed, 27 Jan 2016 16:58:27 +0100 [thread overview]
Message-ID: <1453910307.3517.22.camel@suse.de> (raw)
In-Reply-To: <1453908566-15211-1-git-send-email-mgorman@techsingularity.net>
On Wed, 2016-01-27 at 15:29 +0000, Mel Gorman wrote:
> Changelog since V1
> o Introduce schedstat_enabled and address Ingo's feedback
> o More schedstat-only paths eliminated, particularly ttwu_stat
As mentioned offline, with the somewhat lighter than distro config of
my box, the patch delivered ~4% on cross core pipe-test loop time, and
~2% for tbench throughput.
-Mike
next prev parent reply other threads:[~2016-01-27 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 15:29 Mel Gorman
2016-01-27 15:58 ` Mike Galbraith [this message]
2016-01-28 10:32 ` Matt Fleming
2016-01-28 10:59 ` Mel Gorman
2016-01-28 11:34 ` Matt Fleming
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=1453910307.3517.22.camel@suse.de \
--to=mgalbraith@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--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
Powered by JetHome