All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Hyojong Kim <hkim606@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf events (node-loads, node-load-misses, ...)
Date: Mon, 01 May 2017 20:25:02 -0700	[thread overview]
Message-ID: <87inlkgctt.fsf@firstfloor.org> (raw)
In-Reply-To: <CAC8SZUvZKWkniGBZE_afeNPJT2_9OnKBOudHWHJ_aHNmCbs1Uw@mail.gmail.com> (Hyojong Kim's message of "Mon, 1 May 2017 13:03:41 -0400")

Hyojong Kim <hkim606@gmail.com> writes:

> 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.

node-loads is the number of memory reads served by the local NUMA node.
node-loads-misses is the number of reads served by a remote NUMA node.
Similar for stores.

It has nothing to do with the disk.

-Andi

  parent reply	other threads:[~2017-05-02  3:25 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
2017-05-02 15:54   ` Hyojong Kim
2017-05-02  3:25 ` Andi Kleen [this message]
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=87inlkgctt.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.