From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: using perfctr to determine cache miss rate
Date: Sat, 21 Feb 2004 03:37:28 +0000 [thread overview]
Message-ID: <20040220193728.1a189b35.davem@redhat.com> (raw)
In-Reply-To: <87u11l6rp8.fsf@uga.edu>
On Fri, 20 Feb 2004 22:23:47 -0500
Ed L Cashin <ecashin@uga.edu> wrote:
> Is there a way to measure the number of memory accesses (both reads
> and writes) that are not hitting in any cache? It appears not to be
> possible, since only two events can be observed at once, and the
> events are quite specific (e.g. observing dcache write hits makes
> dcache read hits unobservable).
That's right, this is one of the limitations, since you only sample
two events there are certain things you can't sample in one go.
You could run multiple times, sampling different events each time,
but the results won't be so accurate.
next prev parent reply other threads:[~2004-02-21 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 3:23 using perfctr to determine cache miss rate Ed L Cashin
2004-02-21 3:37 ` David S. Miller [this message]
2004-03-02 1:28 ` Ed L Cashin
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=20040220193728.1a189b35.davem@redhat.com \
--to=davem@redhat.com \
--cc=sparclinux@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.