public inbox for
 help / color / mirror / Atom feed
* Latency in cache hierarchies
@ 2005-02-15 13:14 Mikael Starvik
  0 siblings, 0 replies; only message in thread
From: Mikael Starvik @ 2005-02-15 13:14 UTC (permalink / raw)
  To: sid

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?


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-02-15 13:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-15 13:14 Latency in cache hierarchies Mikael Starvik

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).