Doc improved

This commit is contained in:
Éder F. Zulian
2018-07-05 13:12:39 +02:00
parent 9b237be228
commit 7ca6396766

View File

@@ -889,7 +889,7 @@ initiated. If, at any point, requests start coming in, the burst is
interrupted, meaning that the maximum amount of time, considering the worst
case scenario (a request arrives at the same time a REF was issued), is a
refresh cycle time (tRFC). The advantage of pulling-in refreshes is that they
will not issued in the near future (in their actual times), allowing for more
will not be issued in the near future (in their actual times), allowing for more
efficient accesses to the memory.
**Postpone Refresh**
@@ -899,7 +899,9 @@ requests on the buffer. Buffered requests may generate row-hits, so postponing
refreshes may be beneficial for it avoids breaking row-hit sequences what
reduces the number of commands (e.g., ACT, PRE) to carry out the memory
accesses. If the memory enters an idle state, a burst is issued for the same
number of REF commands that were postponed.
number of REF commands that were postponed. When the maximum allowed
number of postponed refreshes is reached a burst is issued in the next
refresh interval despite the memory state (busy or idle).
**The Flexible Refresh FSM**