linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Selva <manuel.selva@insa-lyon.fr>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Understanding perf mem -t load results
Date: Sun, 15 Dec 2013 23:03:13 +0100	[thread overview]
Message-ID: <52AE2721.8020501@insa-lyon.fr> (raw)
In-Reply-To: <877gb5vmmn.fsf@tassilo.jf.intel.com>

Thanks for the answer Andi.

Is there any way (I couldn't find in the Intel documentation) to have an 
approximation of the "maximum" acceptable frequency ?

Manu

On 12/15/2013 10:18 PM, Andi Kleen wrote:
> Manuel Selva <manuel.selva@insa-lyon.fr> writes:
>>
>> perf mem -t load rec -c 1 make -j18
>
> With -c1 on such a frequent event you will not sample much, but just
> throttle a lot, as the PMI handler would use too much time.
> Your numbers are likely garbage.
>
> -Andi
>

  reply	other threads:[~2013-12-15 22:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 14:06 Understanding perf mem -t load results Manuel Selva
2013-12-15 18:27 ` Manuel Selva
2013-12-15 21:18 ` Andi Kleen
2013-12-15 22:03   ` Manuel Selva [this message]
2013-12-15 23:45     ` Andi Kleen
2013-12-16  9:13       ` Manuel Selva
2013-12-20  9:38         ` Manuel Selva
2013-12-24  2:18           ` Andi Kleen
2013-12-24  7:10             ` Manuel Selva
2013-12-24  7:28               ` Andi Kleen
2013-12-24  7:42                 ` Manuel Selva
2013-12-24 21:27                   ` Andi Kleen
2013-12-25 10:25                     ` Manuel Selva
2014-01-07 15:06                       ` Manuel Selva
2014-01-07 21:27                         ` Andi Kleen
2014-01-08  8:53                           ` Manuel Selva
2014-01-08  9:50                             ` Manuel Selva
2014-01-08 19:44                             ` 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=52AE2721.8020501@insa-lyon.fr \
    --to=manuel.selva@insa-lyon.fr \
    --cc=andi@firstfloor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).