From: "Huang\, Ying" <ying.huang@intel.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: "Huang\, Ying" <ying.huang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, <lkp@01.org>,
<linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
Xiaolong Ye <xiaolong.ye@intel.com>
Subject: Re: [LKP] [lkp] [sched/fair] 53d3bc773e: hackbench.throughput -32.9% regression
Date: Thu, 02 Jun 2016 08:28:14 +0800 [thread overview]
Message-ID: <87pos0igdd.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <1464774513.4023.78.camel@gmail.com> (Mike Galbraith's message of "Wed, 1 Jun 2016 11:48:33 +0200")
Mike Galbraith <umgwanakikbuti@gmail.com> writes:
> On Wed, 2016-06-01 at 16:53 +0800, Huang, Ying wrote:
>
>> You mean the commit is a functionality fix?
>
> Yup.
>
> These kind of things can be a bit annoying. The fix to not subtract
> load that we never added in the first place also pushed hackbench
> around a bit. Do anything at all with load_avg, you're gonna push
> this/that benchmark around a bit, and folks who watch numbers closely
> can end up chasing meaningless deltas.
If this report annoyed you, I am sorry about that. We just want to be
helpful via providing some information. Now I know hackbench is
sensitive to load_avg changes, thanks a lot for the information.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2016-06-02 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:20 [lkp] [sched/fair] 53d3bc773e: hackbench.throughput -32.9% regression kernel test robot
2016-05-31 8:34 ` [LKP] " Huang, Ying
2016-05-31 12:41 ` Peter Zijlstra
2016-06-01 5:00 ` Huang, Ying
2016-06-01 8:40 ` Peter Zijlstra
2016-06-01 8:53 ` Huang, Ying
2016-06-01 9:48 ` Mike Galbraith
2016-06-02 0:28 ` Huang, Ying [this message]
2016-06-02 0:44 ` Mike Galbraith
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=87pos0igdd.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.com \
--cc=xiaolong.ye@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