From: Xishi Qiu <qiuxishi@huawei.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
Laura Abbott <lauraa@codeaurora.org>, Hui Zhu <zhuhui@xiaomi.com>,
Wang Xiaoqiang <wangxq10@lzu.edu.cn>,
LKML <linux-kernel@vger.kernel.org>, <lkp@01.org>
Subject: Re: [lkp] [mm] 6f25a14a70: will-it-scale.scalability -4.0% regression
Date: Thu, 7 Apr 2016 10:40:06 +0800 [thread overview]
Message-ID: <5705C886.90708@huawei.com> (raw)
In-Reply-To: <20160407010657.GB12139@yexl-desktop>
On 2016/4/7 9:06, kernel test robot wrote:
> FYI, we noticed that will-it-scale.scalability -4.0% regression on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 6f25a14a7053b69917e2ebea0d31dd444cd31fd5 ("mm: fix invalid node in alloc_migrate_target()")
>
alloc_migrate_target() is called from cma or mem-offline.
I have no idea what's the relation between these, any ideas?
Thanks,
Xishi Qiu
>
> =========================================================================================
> compiler/cpufreq_governor/kconfig/rootfs/tbox_group/test/testcase:
> gcc-4.9/performance/x86_64-rhel/debian-x86_64-2015-02-07.cgz/lkp-ivb-d03/pthread_mutex1/will-it-scale
>
> commit:
> 969e8d7e47f93ef693028667480558de8f70523f
> 6f25a14a7053b69917e2ebea0d31dd444cd31fd5
>
> 969e8d7e47f93ef6 6f25a14a7053b69917e2ebea0d
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> %stddev %change %stddev
> \ | \
> 2.032e+08 ± 0% -1.6% 2e+08 ± 0% will-it-scale.per_process_ops
> 0.83 ± 0% -4.0% 0.79 ± 0% will-it-scale.scalability
> 214103 ± 14% -20.2% 170884 ± 14% sched_debug.cpu.ttwu_count.stddev
> 3789 ± 7% -10.3% 3398 ± 6% slabinfo.anon_vma_chain.active_objs
> 4660 ± 5% +7.7% 5019 ± 2% vmstat.system.in
>
>
> lkp-ivb-d03: Ivy Bridge
> Memory: 4G
>
>
>
> To reproduce:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
>
>
> Disclaimer:
> Results have been estimated based on internal Intel analysis and are provided
> for informational purposes only. Any difference in system hardware or software
> design or configuration may affect actual performance.
>
>
> Thanks,
> Xiaolong Ye
prev parent reply other threads:[~2016-04-07 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 1:06 [lkp] [mm] 6f25a14a70: will-it-scale.scalability -4.0% regression kernel test robot
2016-04-07 2:40 ` Xishi Qiu [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=5705C886.90708@huawei.com \
--to=qiuxishi@huawei.com \
--cc=js1304@gmail.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=wangxq10@lzu.edu.cn \
--cc=xiaolong.ye@intel.com \
--cc=zhuhui@xiaomi.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