3.0 Client Interface
(Continued)
Transmit Port Timing when PIPE is Negated
TL/F/11928–22
FIGURE 3.5. When PIPE is negated, the Type Field and the
Symbol Field are Loaded during the Same Clock Cycle
TL/F/11928–15
FIGURE 3.6. Rx Port Client Interface
3.4 Client Receive Port
Figure 3.6 shows the QR0001 receive block and part of the
forwarding path.
1. The Upstream Router, LB Target Handler, Target Han-
dler, and the Ring FIFO are part of the forwarding path.
The LB Target Handler processes LB vouchers targeted
to this node into tickets. These tickets are forwarded to
the source node through the downstream port.
The Target Handler processes vouchers targeted to this
node into tickets. These tickets are forwarded to the
source node through the downstream port.
The Ring FIFO stores incoming data from the upstream
port that is intended to be forwarded to other nodes on
the ring, when the downstream pipe is allocated to
launching local data generated by this node.
Now the receive block:
2. The Head Stripper removes all heads except those iden-
tifying the beginning of a stream.
3. The Target FIFO reserves space for 3 normal packets
and 6 LB packets.
4. The Rx Resynchronizer is an 8-deep FIFO in the path
between Target FIFO and the Rx Port.
Note:
The Rx Resynchronizer will handle the discontinuity between the cli-
ent interface and the ring logic of the controller. This function will be
implemented on the next QuickRing deviceDQR1001.
5. The Rx Port is the last stage between a data stream and
the client interface.
On release of Reset: the first two non null symbols that
appear at the RxS
[
31:0
]
are the node ID of the controller,
and the largest/maximum ID number on the ring. (See Sec-
tion 9.1.)
RxET alerts the client interface, up to 20 symbols prior to
the output stage, the type of data entering the receive pipe-
line. The RxT, when PIPE is asserted, leads by one clock
the symbol that it identifies; thus, giving the client a one
clock cycle advance notice of the symbol about to appear at
the RxS
[
31:0
]
. The client may choose to stall the symbol at
RxS
[
31:0
]
if desired.
At the Rx Port, a contiguous data stream is unbounded, and
data belonging to the same head is marked by a single initial
head appearance. At the Rx Port there is no evidence of a
packet. A new head will appear only when there is a change
in data stream. A long data stream transmitted in multiple
packets from one node to another, will appear at the Rx
Port as a single head followed by a long data stream, unless
broken by a different stream from a third node.
In cases where one target node is the subject of multiple
transmissions from several nodes, multiple streams, marked
by head symbols, will appear multiplexed at the Rx Port. The
same will occur if one source node is sending different
streams to the same target. A stream is treated as a differ-
ent stream if the 32-bit head symbol varies in at least one
bit.
8