From: Valdis.Kletnieks@vt.edu
To: root@chaos.analogic.com
Cc: Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ON TOPIC] HELP: Getting lousy memory throughput from Abit KD7
Date: Tue, 22 Jul 2003 15:53:50 -0400 [thread overview]
Message-ID: <200307221953.h6MJroXb001837@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 22 Jul 2003 15:34:51 EDT." <Pine.LNX.4.53.0307221520290.5609@chaos>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Tue, 22 Jul 2003 15:34:51 EDT, "Richard B. Johnson" said:
> If I needed to really find the memory access time, I would write
> a program to test it.
> (4) Warm the cache first by reading everything in the buffer you
> are going to test.
At which point you're measuring the cache speed not the memory speed.
> You will probably be amazed at how well your system performs. This
> dual CPU 400 MHz thing, with 100 MHz memory does 1,900++ MiB/sec.
Which probably explains this result. Do a quick sanity check - this number
seems to indicate 20 bytes per memory clock, EVERY clock - either there's
some VERY creative use of prefetching to make sure that you never hit a
cache line miss, or you're measuring the cache.. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-22 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 21:14 [OT??] HELP: Getting lousy memory throughput from Abit KD7 Timothy Miller
2003-07-22 19:21 ` [ON TOPIC] " Timothy Miller
2003-07-22 19:34 ` Richard B. Johnson
2003-07-22 19:53 ` Valdis.Kletnieks [this message]
2003-07-22 21:04 ` Dave Jones
2003-07-22 21:30 ` Jamie Lokier
2003-07-22 21:36 ` Mike Fedyk
2003-07-27 17:15 ` [OT??] " Marc Wilson
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=200307221953.h6MJroXb001837@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=root@chaos.analogic.com \
/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).