Sun Microelectronics
126
UltraSPARC User’s Manual
Figure 7-30
Data_Stall to
UltraSPARC
Sinking Data
In Figure 7-30 latching of the first quadword D
0
is deferred by one clock cycle.
7.14 Multiple Outstanding Transactions
7.14.1 Ordering of S_REPLYs
UltraSPARC-I supports only one outstanding 64-byte read (P_RD*_REQ or
P_NCBRD_REQ in Class 0). In addition, since a single read buffer is used for all
reads, UltraSPARC-I supports only one outstanding read of any type. Thus,
P_RD*_REQ or P_NCBRD_REQ in Class 0 and P_NCRD_REQ in Class 1 cannot
be outstanding simultaneously.
UltraSPARC-II supports three outstanding 64-byte reads (P_RD*_REQ or
P_NCBRD_REQ in Class 0). As in UltraSPARC-I, P_RD*_REQ / P_NCBRD_REQ
is mutually exclusive with P_NCRD_REQ. if any P_NCRD_REQ is outstanding,
UltraSPARC-II will not issue any other request. Finally, UltraSPARC-II will not is-
sue a P_NCRD_REQ if any Class 0 transaction is outstanding.
UltraSPARC issues all other transactions in Class 1, and can have many outstand-
ing. Multiple Class 1 transactions must be completed in the same order that the
address packets are issued. This presents some issues with implementing coher-
ent read / Writeback pairs in systems with another cache coherent memory re-
questor (or another UltraSPARC). The SC may need to maintain intermediate
state to track either the new read miss line or the Writeback line. The read miss
and Writeback may complete in any order, and the Writeback may be queued be-
hind other Class 1 transactions.
64-byte reads must be completed in order. Coherent Writebacks also must be
completed in order, because of the FIFOs used in the implementation.
S_REPLY to Data Sink
Data on Bus
D[1]
D[2]
D[3]
Data Stall
S_REPLY
D[0]
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com