public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: acme@infradead.org
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	eranian@google.com
Subject: [PATCH 1/2] perf, tools, mem: Clarify load-latency in documentation
Date: Fri, 28 Feb 2014 06:02:14 -0800	[thread overview]
Message-ID: <1393596135-4227-2-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1393596135-4227-1-git-send-email-andi@firstfloor.org>

From: Andi Kleen <ak@linux.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@google.com
Signed-off-by: Andi Kleen <ak@linux.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


  reply	other threads:[~2014-02-28 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 14:02 Clarify perf man pages Andi Kleen
2014-02-28 14:02 ` Andi Kleen [this message]
2014-03-18  8:28   ` [tip:perf/core] perf mem: Clarify load-latency in documentation tip-bot for Andi Kleen
2014-02-28 14:02 ` [PATCH 2/2] perf, tools, probe: Clarify x86 register naming for perf probe Andi Kleen
2014-03-02  3:08   ` Masami Hiramatsu
2014-03-18  8:29   ` [tip:perf/core] perf " tip-bot for Andi Kleen

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=1393596135-4227-2-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox