Separate message labels do not create separate resources. Progress depends on which buffers, credits and pending entries are held while other resources are requested. Begin with a small concrete cycle before discussing virtual networks or fairness.
Lesson | After it you can... |
|---|---|
Name the held and requested resources in a reachable cycle. | |
Order message classes and tell protocol deadlock from routing deadlock. | |
Classify a failure by what can still move. | |
Bound the claim by assumptions A1-A6. |
Read in order after the Part 4 controller resources. Scope: the bad example adds finite resources to the course model, and its corrected variant breaks that one cycle, not every possible cycle in a production fabric.
No. Fairness chooses among enabled actions. A resource deadlock needs a structural escape or a recovery transition, not merely a fairer choice of blocked work.