29 September 1997 – Subject To Change
Clocks, Cache, and External Interface
4–23
21164PC-to-Bcache Transactions
Figure 4–10 Bcache Private Write Probe
4.6.5.2 Bcache Private Data-Write Operation
If a CPU-initiated write command hits in the Bcache, the data-write operation is
scheduled immediately. If the write hits clean, then the data-write operation must
update the tag state to dirty. If the write hits dirty, then the data-write operation does
not update the tag store.
If the CPU-initiated write command misses in the Bcache, the data-write is sched-
uled after the fill data from memory has returned. During the fill operation, the
Bcache tag store is updated to reflect the new tag and control state (modified). There-
FM-05561.AI4
index_h<21:4>
tag_ram_oe_l
st_clk
x_h
tag_ram_we_l
data_adsc_l
tag_data<32:19>
data_adv_l
data_ram_oe_l
data_ram_we_l<3:0>
data<127:0>
cpu_clk
0
1
2
3
4
5
6
7
8
bc_rd_latency (=5)
A0
T0
F
bc_clk_ratio (=3)
bc_clk_delay (=1)
Arrow indicates when the 21164PC
clocks Bcache probe data.