From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [rbd] 2f18d46683: vm-scalability.throughput -92.3% regression
Date: Tue, 17 Jul 2018 15:37:44 +0800 [thread overview]
Message-ID: <87sh4igvnb.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CAOi1vP8q45y35hbFyqkNGN4iB2BAbBwzhwROO6TmaoURJUcFEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Ilya Dryomov <idryomov@gmail.com> writes:
> On Fri, Jun 22, 2018 at 10:37 AM kernel test robot
> <xiaolong.ye@intel.com> wrote:
>>
>>
>> Greeting,
>>
>> We noticed a -92.3% regression of vm-scalability.throughput due to commit:
>>
>> commit: 2f18d46683cb3047c41229d57cf7c6e2ee48676f ("rbd: refactor rbd_wait_state_locked()")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> in testcase: vm-scalability
>> on test machine: 80 threads Skylake with 64G memory
>> with following parameters:
>>
>> runtime: 300s
>> test: lru-file-readonce
>> cpufreq_governor: performance
>>
>> test-description: The motivation behind this suite is to exercise functions and regions of the mm/ of the Linux kernel which are of interest to us.
>> test-url: https://git.kernel.org/cgit/linux/kernel/git/wfg/vm-scalability.git/
>
> This is a false positive: rbd is disabled in the attached config,
> as is the rest of ceph:
>
> # CONFIG_CEPH_LIB is not set
> # CONFIG_BLK_DEV_RBD is not set
> # CONFIG_CEPH_FS is not set
>
After double check, it is found that there's a bug in test system itself
which cause the false positive. Sorry for bothering.
Best Regards,
Huang, Ying
prev parent reply other threads:[~2018-07-17 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 8:34 [lkp-robot] [rbd] 2f18d46683: vm-scalability.throughput -92.3% regression kernel test robot
2018-06-22 9:00 ` Ilya Dryomov
2018-07-17 7:37 ` 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=87sh4igvnb.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.