From: "Mikael Starvik" <mikael.starvik@axis.com>
To: <sid@sources.redhat.com>
Subject: Latency in cache hierarchies
Date: Tue, 15 Feb 2005 13:14:00 -0000 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66801B7637A@exmail1.se.axis.com> (raw)
Lets say you have a system with a L1-cache and a L2-cache.
In cache_component::read_line() the latency for the first read is saved as a
latency for the complete operation. This looks correct to me because it is
the first read that may trigger additional refills down the chain and has
the largest latency.
In cache_component::write_line() the latency for the last write is returned.
This makes me a bit confused. The first write may trigger dirty flushed down
the chain and should have the largest latency so why isn't that saved in the
same way as in read_line?
/Mikael
reply other threads:[~2005-02-15 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BFECAF9E178F144FAEF2BF4CE739C66801B7637A@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).