From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com,
guobing.chen@intel.com, ming.a.chen@intel.com,
frank.du@intel.com, Shuhua.Fan@intel.com, wangyang.guo@intel.com,
Wenhuan.Huang@intel.com, jessica.ji@intel.com,
shan.kang@intel.com, guangli.li@intel.com, tiejun.li@intel.com,
yu.ma@intel.com, dapeng1.mi@intel.com, jiebin.sun@intel.com,
gengxin.xie@intel.com, fan.zhao@intel.com,
aubrey.li@linux.intel.com, yu.c.chen@intel.com
Subject: Re: [x86, sched] 2a0abc5969: phoronix-test-suite.stress-ng.SystemVMessagePassing.bogo_ops_s -14.1% regression
Date: Mon, 16 Nov 2020 10:31:25 +0100 [thread overview]
Message-ID: <1605519085.19452.74.camel@suse.cz> (raw)
In-Reply-To: <20201116070733.GA22371@xsang-OptiPlex-9020>
On Mon, 2020-11-16 at 15:07 +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -14.1% regression of phoronix-test-suite.stress-ng.SystemVMessagePassing.bogo_ops_s due to commit:
>
>
> commit: 2a0abc59699896f03bf6f16efb8a3a490511216f ("x86, sched: Add support for frequency invariance on SKYLAKE_X")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
>
> in testcase: phoronix-test-suite
> on test machine: 96 threads Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz with 192G memory
> with following parameters:
>
> test: stress-ng-1.2.2
> option_a: System V Message Passing
> cpufreq_governor: performance
> ucode: 0x5002f01
I haven't checked this regression yet, but when a "schedutil" change like
this patch triggers a regression when the "performance" governor is used,
the trouble might come in some roundabout way, eg. from cache alignment issues.
The patch defines a number of (not necessarily aligned) per-cpu variables, and
there was a recent thread where Boris Petkov, Tony Luck and Mel Gorman debugged
something that had similar characteristics:
"RE: [LKP] Re: [x86/mce] 1de08dccd3: will-it-scale.per_process_ops -14.1% regression"
https://lore.kernel.org/lkml/6e996ad05e434a6fb13f069ee72b876b@intel.com/
I'll study this problem with that in mind.
Giovanni
prev parent reply other threads:[~2020-11-16 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 7:07 kernel test robot
2020-11-16 9:31 ` Giovanni Gherdovich [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=1605519085.19452.74.camel@suse.cz \
--to=ggherdovich@suse.cz \
--cc=Shuhua.Fan@intel.com \
--cc=Wenhuan.Huang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=fan.zhao@intel.com \
--cc=feng.tang@intel.com \
--cc=frank.du@intel.com \
--cc=gengxin.xie@intel.com \
--cc=guangli.li@intel.com \
--cc=guobing.chen@intel.com \
--cc=jessica.ji@intel.com \
--cc=jiebin.sun@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ming.a.chen@intel.com \
--cc=mingo@kernel.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=shan.kang@intel.com \
--cc=tiejun.li@intel.com \
--cc=wangyang.guo@intel.com \
--cc=ying.huang@intel.com \
--cc=yu.c.chen@intel.com \
--cc=yu.ma@intel.com \
--cc=zhengjun.xing@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
all inboxes | Powered by JetHome®