From: "zzh" <david-1z@263.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: about memory bandwidth
Date: Fri, 7 Apr 2000 18:37:35 +0800 (CST) [thread overview]
Message-ID: <38EDBA6F.06842@mta2> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Hi,How to measure the 60x bus bandwidth.I write a program to write
to sdram in a tight loop,every iteration ,i write 8 words,
it takes about 36 seconds to finish 32M iterations with i-cache
enabled and d-cache disenabled.With d-cache enabled and flushing
cache in every iteration,it takes about 16 seconds.This is below
what i speculated.What is the possible reason?I program the sdram
machine to enable burst mode. 4/7/2000
_____________________________________________
263Ê×¶¼ÔÚÏß--ÖйúÈ˵ÄÍøÉϼÒÔ° http://www.263.net
¾«²Ê¡¢Ãâ·Ñ¡¢»¹ÄÜÊ¡ÉÏÍø·Ñ£¬¿ì¶©ÔÄË÷Ò×µç×Ó¿¯Îhttp://www.soim.com
»ý£¨ÓÅ£©µã£¬»»£¨½±£©Æ·£¡http://www.thepoints.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-07 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 10:37 zzh [this message]
2000-04-07 12:09 ` about memory bandwidth Gabriel Paubert
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=38EDBA6F.06842@mta2 \
--to=david-1z@263.net \
--cc=linuxppc-embedded@lists.linuxppc.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).