From: Namhyung Kim <namhyung@kernel.org>
To: Chulmin Kim <cmkim@core.kaist.ac.kr>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Question about LLC-load-misses event
Date: Tue, 23 Oct 2012 14:39:54 +0900 [thread overview]
Message-ID: <87a9vd7nmd.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <507C1036.7020707@core.kaist.ac.kr> (Chulmin Kim's message of "Mon, 15 Oct 2012 22:31:34 +0900")
Hi Chulmin,
On Mon, 15 Oct 2012 22:31:34 +0900, Chulmin Kim wrote:
> 2012-10-15 오후 10:07, Chulmin Kim 쓴 글:
>> (perf command : perf stat -a -A -e LLC-loads -e LLC-load-misses -e
>> instructions sleep 3)
>>
>> The problem is,, the bandwidth from STREAM benchmark does not match with
>> the monitored value.
>>
>> e.g.
>> I got 9395MB/s from Stream.
>>
>> "perf" shows 134,642,063 LLC-load-misses for 3 seconds.
>> -> BW = ((# of events)/(3 seconds)) * 64 bytes / (1024*1024) = 2739MB/s
>> In this equation, the term (64bytes) is for cache line size, and the
>> term(1024*1024) is for (MB/s).
>>
>> Why does this mismatch occur?
> In case of Oprofile, the value for a certain event represents the number
> of the overflows which occur when the number of the event exceeds the
> predefined value.
> Is it a similar case with that?
I guess not. And what's the result of the LLC-loads? AFAIK it counts
all cache accesses including hits and misses. Did you calculate the
bandwidth using the result of LLC-loads? I suspect the h/w *might*
prefetches a couple of lines when cache-miss occurred, but I'm not
sure. :)
Thanks,
Namhyung
next prev parent reply other threads:[~2012-10-23 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 13:07 Question about LLC-load-misses event Chulmin Kim
2012-10-15 13:31 ` Chulmin Kim
2012-10-23 5:39 ` Namhyung Kim [this message]
2012-10-23 5:53 ` Chulmin Kim
2012-10-24 12:56 ` Chulmin Kim
-- strict thread matches above, loose matches on Subject: below --
2012-10-15 12:59 Chulmin 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=87a9vd7nmd.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=cmkim@core.kaist.ac.kr \
--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.