From: Tyson Thomas <tyson.thomas@sydney.edu.au>
To: "Liang, Kan" <kan.liang@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: [BUG REPORT] perf tools: x86_64: weight column displays odd memory latency data
Date: Wed, 1 Jun 2022 05:03:01 +0000 [thread overview]
Message-ID: <MEYPR01MB66152548BEC4D0113BBBD7A5DBDF9@MEYPR01MB6615.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <fd28e6fb-cf4c-a065-6138-4c581e871341@linux.intel.com>
Hi Kan,
Thanks for the reply.
The exact command used was: perf mem report
The columns are in order: Overhead, Samples, Local Weight, Memory Access.
The results I sent before are: Overhead, Local Weight and Memory.
So, to update the table from before, each tuple has a sample of 1, so it is:
0.02%,1 ,62515 ,L1 or L1 hit
0.02%,1 ,54048 ,L1 or L1 hit
0.02%,1 ,52206 ,L1 or L1 hit
0.02%,1 ,49831 ,L1 or L1 hit
0.02%,1 ,49056 ,Local RAM or RAM hit
0.01%,1 ,40666 ,LFB or LFB hit
0.01%,1 ,38080 ,L1 or L1 hit
0.01%,1 ,36772 ,L1 or L1 hit
So, the weights are absurdly high here.
I'll give a reply on perf report -D shortly.
Regards,
Tyson
From: Liang, Kan <kan.liang@linux.intel.com>
Sent: Wednesday, 25 May 2022 12:58 AM
To: Tyson Thomas <tyson.thomas@sydney.edu.au>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; linux-perf-users@vger.kernel.org <linux-perf-users@vger.kernel.org>
Subject: Re: [BUG REPORT] perf tools: x86_64: weight column displays odd memory latency data
On 5/22/2022 6:14 PM, Tyson Thomas wrote:
> Hi Kan, Linux-Perf Team
>
> I have observed some odd behaviour within perf when using perf-mem. Specifically the reported latency under the weight column appears to be unreasonably high.
>
> Here is a given sample from a recent test, I find that some of the latencies are close to an unsigned short and I cannot seem to be understand why that would be outside of it being an issue with the perf events.
>
> This can be replicated using a NAS benchmark, specifically cg.D.
>
> I observe the following results in perf mem report (just getting the top 10 results)
>
Could you please show me the exact perf command used?
With my perf mem report,
The first column is the Overhead.
The second column is the number of samples.
The third column is the weight.
The fourth is the Memory access.
Seems like the weight is missed?
Could you please check the perf report -D?
It will dump the weight for each Sample.
Does it look correct?
Thanks,
Kan
> 0.02% ,62515 ,L1 or L1 hit
> 0.02% ,54048 ,L1 or L1 hit
> 0.02% ,52206 ,L1 or L1 hit
> 0.02% ,49831 ,L1 or L1 hit
> 0.02% ,49056 ,Local RAM or RAM hit
> 0.01% ,40666 ,LFB or LFB hit
> 0.01% ,38080 ,L1 or L1 hit
> 0.01% ,36772 ,L1 or L1 hit
> 0.01% ,36729 ,LFB or LFB hit
> 0.01% ,27101 ,LFB or LFB hit
>
> Is it possible for someone to shed some light on this or am I misunderstanding how the weight column is used here?
> This appears to have been an issue on 5.4, 5.10 and 5.15. I am looking into seeing if it is still present in 5.17 and 5.18.
>
> I've also tried this on different Intel CPUs such as Intel Xeon 6230, i5-1135G7, Intel Xeon 6330
>
> Any insight or help would be appreciated,
> Tyson
next prev parent reply other threads:[~2022-06-01 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 22:14 [BUG REPORT] perf tools: x86_64: weight column displays odd memory latency data Tyson Thomas
2022-05-24 14:58 ` Liang, Kan
2022-06-01 5:03 ` Tyson Thomas [this message]
2022-06-03 14:03 ` Liang, Kan
2022-06-07 20:39 ` Tyson Thomas
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=MEYPR01MB66152548BEC4D0113BBBD7A5DBDF9@MEYPR01MB6615.ausprd01.prod.outlook.com \
--to=tyson.thomas@sydney.edu.au \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.