From: "Huang\, Ying" <ying.huang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
kitsunyan <kitsunyan@inbox.ru>, Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>, "Chris Mason" <clm@fb.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>, <lkp@01.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [LKP] [lkp-robot] [sched/fair] 4c77b18cf8: hackbench.throughput -14.4% regression
Date: Tue, 02 May 2017 10:29:19 +0800 [thread overview]
Message-ID: <87r308f0u8.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20170307075303.GS6500@twins.programming.kicks-ass.net> (Peter Zijlstra's message of "Tue, 7 Mar 2017 08:53:03 +0100")
Hi, Peter,
Peter Zijlstra <peterz@infradead.org> writes:
> On Tue, Mar 07, 2017 at 11:18:36AM +0800, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed a -14.4% regression of hackbench.throughput due to commit:
>
> Yeah, I know ... this patch is a mixed bag, some like it, some hate it.
>
> But given it was fingered by a human doing desktopy things that trumps
> artificial benchmark.
>
> Still, I'll try and see if I can fix thing once I find a spare moment.
Do you have any update for this regression?
Don't want to push you, just want to get the latest status.
Best Regards,
Huang, Ying
prev parent reply other threads:[~2017-05-02 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 3:18 [lkp-robot] [sched/fair] 4c77b18cf8: hackbench.throughput -14.4% regression kernel test robot
2017-03-07 7:53 ` Peter Zijlstra
2017-05-02 2:29 ` Huang, Ying [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=87r308f0u8.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=clm@fb.com \
--cc=efault@gmx.de \
--cc=kitsunyan@inbox.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.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;
as well as URLs for NNTP newsgroup(s).