Sophiane Senni ce2722cdd9 mem: Split the hit_latency into tag_latency and data_latency ... If the cache access mode is parallel, i.e. "sequential_access" parameter is set to "False", tags and data are accessed in parallel. Therefore, the hit_latency is the maximum latency between tag_latency and data_latency. On the other hand, if the cache access mode is sequential, i.e. "sequential_access" parameter is set to "True", tags and data are accessed sequentially. Therefore, the hit_latency is the sum of tag_latency plus data_latency. Signed-off-by: Jason Lowe-Power <jason@lowepower.com>		2016-11-30 17:10:27 -05:00
..
boot	rcs scripts: remove bbench.rcS	2013-04-02 12:46:49 -04:00
common	mem: Split the hit_latency into tag_latency and data_latency	2016-11-30 17:10:27 -05:00
dist	config: Make configs/common a Python package	2016-10-14 10:37:38 -04:00
dram	config: Make configs/common a Python package	2016-10-14 10:37:38 -04:00
example	mem: Split the hit_latency into tag_latency and data_latency	2016-11-30 17:10:27 -05:00
learning_gem5	mem: Split the hit_latency into tag_latency and data_latency	2016-11-30 17:10:27 -05:00
network	ruby: Fix regressions and make Ruby configs Python packages	2016-10-13 03:17:19 -04:00
ruby	config: Make configs/common a Python package	2016-10-14 10:37:38 -04:00
splash2	config: Make configs/common a Python package	2016-10-14 10:37:38 -04:00
topologies	ruby: Fix regressions and make Ruby configs Python packages	2016-10-13 03:17:19 -04:00