User manual

Table Of Contents
Zynq-7000 AP SoC Technical Reference Manual www.xilinx.com 303
UG585 (v1.11) September 27, 2016
Chapter 10: DDR Memory Controller
10.4.5 Stage 2 – Read Versus Write
The reads and the writes each have a queue in the DDR Core. The entries in these queues then vie for
the next level of arbitration, shown in Figure 10-7.
This stage of arbitration starts with the aging counter as shown in Figure 10-7. If there is a same type
of transaction with a priority 0, it wins. For example if a read won the last round of arbitration and
there is a read with priority 0, it wins. If there is not a same type of transaction with priority 0, and
another type of transaction with a priority 0 is present, it wins. If there is no Priority 0 in the queue
then it stays with the same type of transaction. An appropriate credit availability check is done before
selecting any request in all the above cases.
10.4.6 High Priority Read Ports
Before going into Stage 3 of the arbitration, a feature of the DDRC, the high priority read, needs to
be described. The HPR, or high priority read feature, allows splitting the read data queue (32 words)
within the DDRC into two separate queues for low and high priority. Each of the four read ports can
be assigned a low or high priority. By default this feature is disabled. When used, a high priority read
device is not slowed down by the (potentially slower) read data rate of a low-priority device. In a
typical use case, HPR is enabled on port 0 (CPU), thus reducing the CPU average read latency. The
split of the read data queue does not have to be two equal parts. Thus giving the CPU a small queue
to bypass the larger queue to service reads that need a lower latencies. Figure 10-8 shows where the
read queue is split.
X-Ref Target - Figure 10-7
Figure 10-7: Stage 2 – Read Versus Write
UG585_c10_07_032012
Write Winner
Aging Counter
Read Winner
Aging Counter
Stay with
Same Type
Other Type
Priority 0?
Winner
T
Winner
F
Same Type
Priority 0?
Winner
T
F