From: Peter Zijlstra <peterz@infradead.org>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>,
"Wu, Fengguang" <fengguang.wu@intel.com>
Subject: Re: [LKP] [sched/core] 9edfbfed3f5: +88.2% hackbench.time.involuntary_context_switches
Date: Mon, 9 Feb 2015 10:27:35 +0100 [thread overview]
Message-ID: <20150209092735.GP5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAC=cRTN3VKmgM4BYUrN=rMfg8stiP-F_oWR+2LSPFR9m1Wmfqg@mail.gmail.com>
On Mon, Feb 09, 2015 at 04:47:07PM +0800, huang ying wrote:
> There are no distinguishable difference between the parent and the child
> for hackbench throughput number.
>
> Usually you will not consider statistics such as involuntary context
> switches?
Only if there's a 'problem' with the primary performance metric (total
runtime in case of hackbench).
Once the primary metric shifts, you go look at what the cause of this
change might be, at that point things like # context switches etc.. are
interesting. As long as the primary performance metric is stable, meh.
As such; I would suggest _always_ reporting the primary metric for each
benchmark, preferably on top and not hidden somewhere in the mass of
numbers.
I now had to very carefully waste a few minutes of my time reading those
numbers to see if there was anything useful in; there wasn't.
next prev parent reply other threads:[~2015-02-09 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 5:58 [LKP] [sched/core] 9edfbfed3f5: +88.2% hackbench.time.involuntary_context_switches Huang Ying
2015-02-09 8:31 ` Peter Zijlstra
[not found] ` <CAC=cRTN3VKmgM4BYUrN=rMfg8stiP-F_oWR+2LSPFR9m1Wmfqg@mail.gmail.com>
2015-02-09 9:27 ` Peter Zijlstra [this message]
2015-02-10 7:26 ` Markus Pargmann
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=20150209092735.GP5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=ying.huang@intel.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