This is the mail archive of the
sid@sources.redhat.com
mailing list for the SID project.
Latency in cache hierarchies
- From: "Mikael Starvik" <mikael dot starvik at axis dot com>
- To: <sid at sources dot redhat dot com>
- Date: Tue, 15 Feb 2005 14:12:57 +0100
- Subject: Latency in cache hierarchies
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