From: Fengguang Wu <fengguang.wu@intel.com>
To: Jet Chen <jet.chen@intel.com>
Cc: Aaron Tomlin <atomlin@redhat.com>,
Dave Hansen <dave.hansen@intel.com>, LKP <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [kernel/watchdog.c] ed235875e2c: -14.2% will-it-scale.scalability
Date: Fri, 4 Jul 2014 11:54:55 +0800 [thread overview]
Message-ID: <20140704035455.GA5524@localhost> (raw)
In-Reply-To: <53B6235B.4050205@intel.com>
Hi all,
Sorry please ignore this report: it seems there are no obvious
relationship between the code change and the regression.
Thanks,
Fengguang
On Fri, Jul 04, 2014 at 11:45:31AM +0800, Jet Chen wrote:
> Hi Aaron,
>
> FYI, we noticed the below changes on
>
> commit ed235875e2ca983197831337a986f0517074e1a0 ("kernel/watchdog.c: print traces for all cpus on lockup detection")
>
> test case: lkp-snb01/will-it-scale/signal1
>
> f3aca3d09525f87 ed235875e2ca983197831337a
> --------------- -------------------------
> 0.12 ~ 0% -14.2% 0.10 ~ 0% TOTAL will-it-scale.scalability
> 506146 ~ 0% -4.4% 484004 ~ 0% TOTAL will-it-scale.per_process_ops
> 12193 ~ 4% +12.6% 13726 ~ 6% TOTAL slabinfo.kmalloc-256.active_objs
> 12921 ~ 4% +12.3% 14516 ~ 5% TOTAL slabinfo.kmalloc-256.num_objs
> 123094 ~ 3% -6.5% 115117 ~ 3% TOTAL meminfo.Committed_AS
>
> Legend:
> ~XX% - stddev percent
> [+-]XX% - change percent
>
>
> will-it-scale.per_process_ops
>
> 515000 ++-----------------------------------------------------------------+
> | .*.*.*.*. .* |
> 510000 *+* *.*.* + .*. *. |
> 505000 ++ * *.*.*.*. .* .*.*.*. .*.*.*. + *.*.*.*.*.*
> | * * * *.* |
> 500000 ++ |
> | |
> 495000 ++ |
> | |
> 490000 ++ |
> 485000 ++ O O O O O O |
> | O O O O O O O O O O |
> 480000 O+O O O O O |
> | |
> 475000 ++-----------------------------------------------------------------+
>
>
> [*] bisect-good sample
> [O] bisect-bad sample
>
>
> 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,
> Jet
>
> echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu10/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu11/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu12/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu13/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu14/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu15/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu16/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu17/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu18/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu19/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu20/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu21/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu22/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu23/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu24/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu25/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu26/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu27/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu28/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu29/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu30/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu31/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu8/cpufreq/scaling_governor
> echo performance > /sys/devices/system/cpu/cpu9/cpufreq/scaling_governor
> ./runtest.py signal1 25 1 8 16 24 32
>
prev parent reply other threads:[~2014-07-04 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 3:45 [kernel/watchdog.c] ed235875e2c: -14.2% will-it-scale.scalability Jet Chen
2014-07-04 3:54 ` Fengguang Wu [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=20140704035455.GA5524@localhost \
--to=fengguang.wu@intel.com \
--cc=atomlin@redhat.com \
--cc=dave.hansen@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@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 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).