From: Thomas Gleixner <tglx@linutronix.de>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: Alex Thorlton <athorlton@sgi.com>,
LKML <linux-kernel@vger.kernel.org>, Mike Travis <travis@sgi.com>,
Russ Anderson <rja@sgi.com>, Dimitri Sivanich <sivanich@sgi.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
x86@kernel.org, lkp@01.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression
Date: Fri, 28 Oct 2016 00:37:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610280030460.4913@nanos> (raw)
In-Reply-To: <20161027015508.GG21890@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Thu, 27 Oct 2016, Ye Xiaolong wrote:
> Yes, this is weird, the per_thread_ops change is small and should be run
> to run variation, the actual significant change is will-it-scale.time.user_time
> -27% decrease, but the patch seems not relevant, we can't interpret it. :(
>
> We've tried to queue the jobs (4 times) for
> 71854cb812ec23bfe5f63d52217e6b9e6cb901f5 and v4.9-rc1 with new kconfig
> (added CONFIG_DEBUG_INFO_REDUCED), and result shows user_time change is
> quite stable.
> v4.9-rc1 71854cb812ec23bfe5f63d5221
> ---------------- --------------------------
> %stddev %change %stddev
> \ | \
> 1670068 ± 0% -3.8% 1606650 ± 1% will-it-scale.per_thread_ops
> 9749 ± 2% +1328.0% 139222 ±105% will-it-scale.time.involuntary_context_switches
^^^^^^ This is massive
I have no explanation for this either, but you really should try to figure
out what's going on here.
The only difference between plain rc1 and rc + this patch is the resulting
text size and therefor some other unrelated stuff moving to different
places in memory which has some yet to figure out side effects.
Thanks,
tglx
next prev parent reply other threads:[~2016-10-27 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 1:48 [PATCH v2] x86/platform/UV: Fix support for EFI_OLD_MEMMAP after BIOS callback updates Alex Thorlton
2016-10-20 12:26 ` Matt Fleming
2016-10-21 5:48 ` [tip:x86/urgent] " tip-bot for Alex Thorlton
2016-10-25 6:46 ` [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression kernel test robot
2016-10-25 10:57 ` Thomas Gleixner
2016-10-27 1:55 ` Ye Xiaolong
2016-10-27 22:37 ` Thomas Gleixner [this message]
2016-10-31 5:41 ` [LKP] " Fengguang Wu
2016-10-31 18:19 ` Thomas Gleixner
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=alpine.DEB.2.20.1610280030460.4913@nanos \
--to=tglx@linutronix.de \
--cc=athorlton@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
--cc=xiaolong.ye@intel.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®