| 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: <tip-b63940970492f5f187d546e191bc2c6831491fe3@git.kernel.org> Date: Tue, 18 Mar 2014 01:28:55 -0700 From: tip-bot for Andi Kleen <tipbot@...or.com> To: linux-tip-commits@...r.kernel.org Cc: acme@...hat.com, linux-kernel@...r.kernel.org, eranian@...gle.com, hpa@...or.com, mingo@...nel.org, ak@...ux.intel.com, tglx@...utronix.de Subject: [tip:perf/core] perf mem: Clarify load-latency in documentation Commit-ID: b63940970492f5f187d546e191bc2c6831491fe3 Gitweb: http://git.kernel.org/tip/b63940970492f5f187d546e191bc2c6831491fe3 Author: Andi Kleen <ak@...ux.intel.com> AuthorDate: Fri, 28 Feb 2014 06:02:14 -0800 Committer: Arnaldo Carvalho de Melo <acme@...hat.com> CommitDate: Fri, 14 Mar 2014 11:20:44 -0300 perf mem: Clarify load-latency in documentation Clarify in the documentation that 'perf mem report' reports use-latency, not load/store-latency on Intel systems. This often causes confusion with users. Signed-off-by: Andi Kleen <ak@...ux.intel.com> Cc: Stephane Eranian <eranian@...gle.com> Link: http://lkml.kernel.org/r/1393596135-4227-2-git-send-email-andi@firstfloor.org Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.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>...:: -- 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