[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E8ECBC65D0B2554DAD44EBE43059B3740F2AA1@ORSMSX110.amr.corp.intel.com>
Date: Mon, 24 Feb 2020 19:42:45 +0000
From: "Kleen, Andi" <andi.kleen@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
"Tang, Feng" <feng.tang@...el.com>
CC: Jiri Olsa <jolsa@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
"Chen, Rong A" <rong.a.chen@...el.com>,
Ingo Molnar <mingo@...nel.org>,
"Vince Weaver" <vincent.weaver@...ne.edu>,
Jiri Olsa <jolsa@...nel.org>,
"Alexander Shishkin" <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>,
Stephane Eranian <eranian@...gle.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
"lkp@...ts.01.org" <lkp@...ts.01.org>,
"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [LKP] Re: [perf/x86] 81ec3f3c4c: will-it-scale.per_process_ops
-5.5% regression
>Does anybody else have any ideas?
We've had problems with atomics having strange ordering constraints before.
But it might be c2c missing the right cache line. There are some known cases where that can happen.
Feng, can you double check with
perf record -a -d -e mem_load_l3_hit_retired.xsnp_hitm:pp,mem_load_l3_miss_retired.remote_hitm:pp ...
Does it report the same hot IPs as c2c?
What's the break down between the first and the second event for the hot IPs? The first is inside socket, the second between sockets.
-Andi
Powered by blists - more mailing lists