1 / 41

1394.1 Overview (evolving slide set)

1394.1 Overview (evolving slide set). December 13, 1999 Dr. David V. James, Sony dvj@alum.mit.edu (contains slide animations). Bus bridge topologies. (selective routing between buses). Hierarchical bus bridges. b.1. b.4. b.2. a.0. a.1. c.0. c.1. Two portals, one on each bus

asa
Download Presentation

1394.1 Overview (evolving slide set)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1394.1 Overview(evolving slide set) December 13, 1999 Dr. David V. James, Sonydvj@alum.mit.edu (contains slide animations)

  2. Bus bridge topologies (selective routing between buses)

  3. Hierarchical bus bridges b.1 b.4 b.2 a.0 a.1 c.0 c.1 Two portals, one on each bus forwards async by destinationID async routing tables are stable forwards isoch by channel number isoch routing entries are dynamic

  4. Looped bus bridges b.1 b.4 b.2 a.0 a.1 c.0 c.1 disabled bridge During initialization, disable redundant bridge Active topology forms a spanning tree

  5. Software route adjustments b.1 b.4 b.2 a.0 a.1 c.0 c.1 a/c The redundant bridge can be partially activated.Shortest path routing is then enable.But, caution is necessary to avoid deadlocks.

  6. Assigned busID addresses (net refresh after bus reset)

  7. Bus reset results b.1 b.4 b.2 a.0 a.1 d.0 d.1 (c.0) (c.1) A bus reset does several things: a new bus number is assigned a courtesy notification is broadcast

  8. Why new busID assignment? Primary objectives: correctness & simplicity secondary objective: efficient reset recoveryExisting (remapped) virtualIDs can be unsafeDirect local-node addressing (no alpha agent) more efficient; no caching concernsNo source_ID/destination_ID substitutionsNo localID accounts (DIRTY,FREE,...)Single bus rediscovery can be efficient

  9. Subnet disconnection e.1 e.2 e.1 a.0 a.1 d.0 d.1 Both subbuses get new busIdsDirty “victim” subnet is “scrubbed”

  10. Subnet reconnection f.1 f.4 f.2 a.0 a.1 g.0 g.1 New busIDs are assigned: To all merged (bus reset) nodes To unaffected victim buses (due to USED/DIRTY conflict)

  11. Isochronous connections (one talker & multiple listeners)

  12. Isochronous connection (A) L T C Connection assumptions: controller, talker, listener anywhere disconnect if any are “lost” async: channel but no bandwidth

  13. Isochronous connection (B) L’ T C’ Common connection: same talkerEui/plugID distinct controller listener nodes (example: common listener bus)

  14. Overlaid connections L’ L T C’ T C L’ L T C’ C

  15. Persistent connections (NO!) L’ L L’ L C” T C’ C T C’ L” C ? ? L’ L L’ L T T C’ C C’ C

  16. Source quarantine (bridge-aware)

  17. Bridge-aware quarantine detection/removal res res req req Quarantined requester: request accepted, response returned distinct rcode/scode identifies problem Quarantine release: FirstSwap transaction clears quarantine (sequence number possible)

  18. Bridge-awarequarantine recovery res res req req (discard) Quarantine recovery: Discard EUI-to-nodeID translations (or ignore, based on sequence number)

  19. Legacy source quarantine

  20. Legacy quarantine detection res req C Quarantined requester (the same): request accepted (ack_complete), discarded controller’s response-frame timeout occurs

  21. Legacy quarantine recovery list list talk talk C C Quarantine recovery: FinalSwap transaction clears quarantine Consumer reactivates the talker

  22. Net initialization Net refresh - assigns new busIDsNet restart - slowly recycles busIDsNet reset - quickly recycles busIDs

  23. Initial configuration net’s primary-alpha portal bus’s secondary-alpha portal isolating bus-bridge portal

  24. Node attachment results(animated sequence)

  25. Net refresh messages

  26. Bus reset (node attached) bus reset Bus reset invalidates node’s busIDs Reset portals becomes prime-portal candidates Cross-bridge traffic is disabled

  27. Primary bus acquisition Acquisition messages are sent by each portal Acquisition messages sent to “next” portalThe “next” portal is defined to be stable

  28. Primary bus acquisitioned Largest portalID acquisition survivesMessages “pass through” victim portals Completes when candidate’s message return

  29. Adjacent bus acquistion “Breach” packets sent from current candidate Receipt of breach packets initiates breach Adjacent bus acquisition begins...

  30. Remote bus acquisition After acquisition, breach packets sentBreach packets start remote-bus acquisition

  31. Bus acquisition completes Breach packets avoid acquired territoryNet acquisition completes when breach returnsTentative busID/route assignments determined

  32. Commit phase begins Commit begins after breach packets return bridge routing tables are changed busID assignment removes barriers

  33. Commit phase completes Commit completes when commit packets returnNormal operation is possible at this time

  34. Refresh sequence review Bus reset Acquisition Commit

  35. Node attachment results(animated sequence)

  36. Net refresh messages(animated sequence)

  37. Isochronous BW averaging

  38. Peak bandwidth credits BW maximum average time credits

  39. Event merging (if local events are insufficient...)

  40. GASP event overload src src src src tgt 4 input with one output, so something is lost

  41. Merged event parameters merge point OR’d source events timeOfBirth source events timeOfBirth source events timeOfBirth newest time

More Related