From bdb3e469c18c76da5d9c058b881dbd9a6c4fb2c0 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Mon, 25 May 2020 14:54:06 +0100 Subject: [PATCH] argh! frickin MACos terminal expanded out to 86x30 not 80x30 --- src/soc/experiment/l0_cache.py | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/soc/experiment/l0_cache.py b/src/soc/experiment/l0_cache.py index 5f76ae6f..762ed582 100644 --- a/src/soc/experiment/l0_cache.py +++ b/src/soc/experiment/l0_cache.py @@ -153,11 +153,12 @@ class DataMerger(Elaboratable): then uses that row, based on matching address bits, to merge (OR) all data rows into the output. - Basically, by the time DataMerger is used, all of its incoming data is determined - not to conflict. The last step before actually submitting the request to the - Memory Subsystem is to work out which requests, on the same 128-bit cache line, - can be "merged" due to them being: (A) on the same address (bits 4 and above) - (B) having byte-enable lines that (as previously mentioned) do not conflict. + Basically, by the time DataMerger is used, all of its incoming data is + determined not to conflict. The last step before actually submitting + the request to the Memory Subsystem is to work out which requests, + on the same 128-bit cache line, can be "merged" due to them being: + (A) on the same address (bits 4 and above) (B) having byte-enable + lines that (as previously mentioned) do not conflict. Therefore, put simply, this module will: (1) pick a row (any row) and identify it by an index labelled "idx" -- 2.30.2