| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1393596135-4227-2-git-send-email-andi@firstfloor.org> Date: Fri, 28 Feb 2014 06:02:14 -0800 From: Andi Kleen <andi@...stfloor.org> To: acme@...radead.org Cc: linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>, eranian@...gle.com Subject: [PATCH 1/2] perf, tools, mem: Clarify load-latency in documentation From: Andi Kleen <ak@...ux.intel.com> Clarify in the documentation that perf mem report reports use-latency, not load/store-latency on Intel systems. This often causes confusion with users. Cc: eranian@...gle.com Signed-off-by: Andi Kleen <ak@...ux.intel.com> --- tools/perf/Documentation/perf-mem.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/perf/Documentation/perf-mem.txt b/tools/perf/Documentation/perf-mem.txt index 888d511..1d78a40 100644 --- a/tools/perf/Documentation/perf-mem.txt +++ b/tools/perf/Documentation/perf-mem.txt @@ -18,6 +18,10 @@ from it, into perf.data. Perf record options are accepted and are passed through "perf mem -t <TYPE> report" displays the result. It invokes perf report with the right set of options to display a memory access profile. +Note that on Intel systems the memory latency reported is the use-latency, +not the pure load (or store latency). Use latency includes any pipeline +queueing delays in addition to the memory subsystem latency. + OPTIONS ------- <command>...:: -- 1.8.5.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists