linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taeung Song <treeze.taeung@gmail.com>
To: Hyojong Kim <hkim606@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf events (node-loads, node-load-misses, ...)
Date: Tue, 2 May 2017 08:29:37 +0900	[thread overview]
Message-ID: <11b191d5-5322-36bb-16e6-d589485a6e5b@gmail.com> (raw)
In-Reply-To: <CAC8SZUvZKWkniGBZE_afeNPJT2_9OnKBOudHWHJ_aHNmCbs1Uw@mail.gmail.com>

Hi Hyojong,

On 05/02/2017 02:03 AM, Hyojong Kim wrote:
> Hello,
>
> My processor has several hardware cache events, of which I am
> interested in node-loads, node-load-misses, node-stores,
> node-store-misses. I think it is kind of obvious that node-loads and
> node-stores represent references to local memory (memory physically
> attached to a processor package). However, I have no clue as to what
> the rest represents. I have some theory that "node-load-misses"
> represent the number of misses in local memory, or the number of
> accesses to disk. Based on the profiled results I have
> (page-faults:16M << node-load-misses+node-store-misses:748M), however,
> this cannot be the raw number of disk accesses. Maybe some kind of
> piggybacking mechanism (by some MSHR kind of structure in memory?)
> could be the reason behind this discrepancy, but no clue. If anyone
> has some idea on this, please share it with me.
>
> I appreciate your help in advance!
>
> Sincerely,
> - Hyojong

Could I detailedly know your test case ?
(e.g options of perf-record, perf.data, test environment, etc)

Of course, you used the perf events (i.e. node-load-misses, etc),
but if you show the correct command and options when using perf-record
and share a link of the perf.data as the profiled results,
it'd be more easy to investigate this situation.


Thanks,
Taeung

  reply	other threads:[~2017-05-01 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 17:03 perf events (node-loads, node-load-misses, ...) Hyojong Kim
2017-05-01 23:29 ` Taeung Song [this message]
2017-05-02 15:54   ` Hyojong Kim
2017-05-02  3:25 ` Andi Kleen
2017-05-02 15:56   ` Hyojong Kim

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=11b191d5-5322-36bb-16e6-d589485a6e5b@gmail.com \
    --to=treeze.taeung@gmail.com \
    --cc=hkim606@gmail.com \
    --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).