From: "Huang\, Ying" <ying.huang@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: kernel test robot <xiaolong.ye@intel.com>, <lkp@01.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [dcache_{readdir, dir_lseek}() users] 4e82901cd6: reaim.jobs_per_min -49.1% regression
Date: Wed, 01 Jun 2016 09:03:23 +0800 [thread overview]
Message-ID: <87bn3laffo.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20160531134011.GB14480@ZenIV.linux.org.uk> (Al Viro's message of "Tue, 31 May 2016 14:40:11 +0100")
Al Viro <viro@ZenIV.linux.org.uk> writes:
> On Tue, May 31, 2016 at 04:15:15PM +0800, kernel test robot wrote:
>>
>>
>> FYI, we noticed reaim.jobs_per_min -49.1% regression due to commit:
>>
>> commit 4e82901cd6d1af21ae232ae835c36d8230c809e8 ("dcache_{readdir,dir_lseek}() users: switch to ->iterate_shared")
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>
>> in testcase: reaim
>> on test machine: lkp-hsx04: 144 threads Brickland Haswell-EX with 512G memory
>> with following parameters: cpufreq_governor=performance/iterations=4/nr_task=1600%/test=fserver
>
> [snip]
>
> Is there any way to get the profiles?
Sorry, our perf-profile support is broken after upgrading perf-profile
recently. We will restore it ASAP and send back to you the perf profile
results.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2016-06-01 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:15 [lkp] [dcache_{readdir,dir_lseek}() users] 4e82901cd6: reaim.jobs_per_min -49.1% regression kernel test robot
2016-05-31 13:40 ` Al Viro
2016-06-01 1:03 ` Huang, Ying [this message]
2016-06-02 6:28 ` [LKP] [lkp] [dcache_{readdir, dir_lseek}() " Huang, Ying
2016-06-02 16:29 ` Al Viro
2016-06-26 9:50 ` Thorsten Leemhuis
2016-06-26 17:13 ` Linus Torvalds
2016-06-26 18:06 ` Al Viro
2016-06-26 21:20 ` Linus Torvalds
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=87bn3laffo.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).