From: "Huang\, Ying" <ying.huang@linux.intel.com>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: kernel test robot <ying.huang@intel.com>, <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [nfsd] 4aac1bf05b: -2.9% fsmark.files_per_sec
Date: Wed, 30 Sep 2015 07:27:54 +0800 [thread overview]
Message-ID: <87lhbokdqd.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20150929074151.0fe32fc9@tlielax.poochiereds.net> (Jeff Layton's message of "Tue, 29 Sep 2015 07:41:51 -0400")
Jeff Layton <jeff.layton@primarydata.com> writes:
> On Mon, 28 Sep 2015 14:49:32 +0800
> kernel test robot <ying.huang@intel.com> wrote:
>
>> FYI, we noticed the below changes on
>>
>> =========================================================================================
>> tbox_group/testcase/rootfs/kconfig/compiler/cpufreq_governor/iterations/nr_threads/disk/fs/fs2/filesize/test_size/sync_method/nr_directories/nr_files_per_directory:
>> lkp-ne04/fsmark/debian-x86_64-2015-02-07.cgz/x86_64-rhel/gcc-4.9/performance/1x/32t/1HDD/xfs/nfsv4/5K/400M/fsyncBeforeClose/16d/256fpd
>>
>> commit:
>> cd2d35ff27c4fda9ba73b0aa84313e8e20ce4d2c
>> 4aac1bf05b053a201a4b392dd9a684fb2b7e6103
>>
>
> A question...
>
> I think my tree should now contain a fix for this, but with a
> performance regression like this it's difficult to know for sure.
>
> Is there some (automated) way to request that the KTR redo this test?
> If not, will I get a note saying "problem seems to now be fixed" or do
> I just take a lack of further emails from the KTR about this as a sign
> that it's resolved?
Can you provide the branch name and commit ID for your tree with fix? I
can confirm whether it is fixed for you.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-09-29 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 6:49 [lkp] [nfsd] 4aac1bf05b: -2.9% fsmark.files_per_sec kernel test robot
2015-09-29 11:41 ` Jeff Layton
2015-09-29 23:27 ` Huang, Ying [this message]
2015-09-30 0:06 ` Jeff Layton
2015-09-30 8:35 ` Huang, Ying
2015-09-30 10:03 ` Jeff Layton
2015-09-30 23:17 ` Dave Chinner
2015-10-01 0:56 ` J. Bruce Fields
2015-10-01 11:35 ` Jeff Layton
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=87lhbokdqd.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--cc=jeff.layton@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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