BNR# Behavior During Runtime

Figure 48-8 on page 1200 illustrates BNR# behavior during run-time.

  1. The Priority Agent had acquired ownership of the Request Phase signal group in the clock prior to clock 1 and initiated a transaction request. It deasserted BPRI# as it did so to yield ownership to physical processor 0 (BREQ0# was asserted). The indicator is in the Free state and BNR# is being sampled by all Request Agents two clocks after ADS# is sampled asserted.

  2. On clock one, physical processor 0 samples BPRI# deasserted, indicating that it will be the next owner of the Request Phase signal group.

  3. Physical processor 0 initiates a transaction request at the start of clock two (its indicator is in the Free state, giving it permission to do so).

  4. At the start of clock three, BNR# is sampled asserted indicating that one or more FSB agents cannot handle the issuance of any more transactions. The indicator transitions from the Free to the Stalled state in clock four and the BNR# sample rate changes to every two clocks (with no relationship to ADS#'s state). No new transactions can be issued by any Request Agent while they are in the Stalled state.

  5. In clock five, the Priority Agent reasserts BPRI# because it wants to issue another transaction. It cannot do so, however, until BNR# is sampled deasserted.

  6. BNR# is sampled deasserted on clock seven and all Request Agents change the indicator to the Throttled state in clock eight. This gives the Priority Agent permission to issue a new transaction request in clock eight.

  7. BNR# is sampled deasserted again on clock nine and all Request Agents transition to the free state in clock 10. The BNR# sample rate changes back to being sampled by all Request Agents two clocks after ADS# is sampled asserted.

Figure 48-8. BNR# During Runtime


..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.117.216.229