|WikiProject Computing / Networking||(Rated C-class, Mid-importance)|
The introduction was mixing problems of naming, related behaviours, (ATM, MLPS) but was not presenting the mechanism itself. So, I have kept a 4 lines short presentation, and introduced a "Mechanism principle" section, that re-organised all already existing sentences and add a presentation of the mechanism itself.
Moreover, change "the headed/trailer flit" into "the headed/trailer flits" since the header can be composed of several flits (cf. Kalray MPPA for example), and also the trailer.
Changed the example intro a new one, with an animated Figure.
Added the fact that it can create deadlock (a major drawback). I will add an example if I find time.
Removed the sentence "An entire packet need not be buffered to move on to the next node, increasing throughput.". This reduces latency, not throughput.
Added a section "Usage" (was included into "Avantages"), and added references to spacewire and IEEE 1355?
FLIT = digit or unit?
The FLIT page says the acronym stands for FLow control unITs, not digITs as written here.
I'm going to update this page since that sounds like it makes more sense, but I don't ACTUALLY know what I'm talking about. Feel free to revert if I'm wrong, but maybe fix the FLIT page as well? Crcarlin (talk) 18:21, 12 March 2017 (UTC)
- I Well, the FLIT page use both "flow control digits" and "flow control units". Despite the fact that "flow control units" sounds better, a short search on google scholar shows that "flow control digits" is the term used in research papers. Since the mai of Wikipedia is to reflect use, not to correct it, I suggest to change it back to "flow control digits" MarcBoyerONERA (talk) 08:56, 13 March 2017 (UTC)
User:DavidCary update 21 August 2017
- Wormhole routing supports low-latency only when there is no activation of the back-pressure mechanism. And the Sundaresan & Bettati reference is very hold. In fact, they build a real-time access mechanism on top of wormhole since wormhole itself has no real-time capacity. So I disagree with "Wormhole routing supports very low-latency, high-speed, guaranteed delivery of packets suitable for real-time communication." Moreover, "wormhole switching" is the correct word.
- The "routing" section only presents the SpaceWire routing. For example, in Network on chip, the XY routing is mainly used, like in Tilera solutions.
- Dear reader, MarcBoyerONERA has good points that raise more questions in my head that I hope that we all, working together, will clarify in future versions of this article.
- 2. I agree that the "routing" section is currently too narrowly focused on SpaceWire routing. What other routing protocols are used in wormhole networks? Should these protocols be mentioned in the routing protocol article? Is the "chop the first byte off and use that byte to decide where to send the rest of the message" protocol used in Myrinet switches exactly the same as the corresponding SpaceWire protocol? If so, does that protocol have shorter name than "the source routing protocol used in Myrinet and Spacewire"? (Some Wikipedia articles mention "subtractive routing"; is that related or possibly even the same?)
- I hear that a different protocol is used for switching and routing in a grid or hypercube wormhole network -- what are good sources to back up a description of that protocol(s)?
- 1. I agree that "wormhole switching" is the correct phrase to use to describe what the intermediate nodes do in a typical (source routed) wormhole network -- they are switches, not routers.
- I've been using "wormhole routing" to describe the algorithm the transmitter uses to decide and choose what specific path data takes through a wormhole network. Most of the references in this article (at least 4 out of 7 -- Mohapatra, Cook, Haas, and Tvrdik) use the phrase "wormhole routing", so *especially* if I'm misunderstanding what that phrase means, this article needs to mention that phrase and explain what they mean by it. Is there a better phrase I should use to describe the algorithm(s) used to decide and choose what specific path data takes through the wormhole network?
- I know that a lot of people and articles do the confusion, using "wormhole routing" instead of "wormhole switching". That's a pity. For example, the first sentence of Mohapatra reference is "Wormhole *routing* has emerged as the most widely used *switching* technique" :-( What is true is that the routing has an influence on the performances of a network with wormhole switching. MarcBoyerONERA (talk) 07:37, 31 August 2017 (UTC)
- Should Wikipedia have a separate article to describe those (global) wormhole routing algorithms, leaving this article to focus on the (local) switching that occurs at each intermediate node? If so, what should that article be called?
- It's impossible to build a low-latency system on top of high-latency hardware. So the fact that Sundaresan & Bettati built a low-latency system with wormhole switch hardware shows that it is possible to build a low-latency system with wormhole switch hardware.
- There is a confusion between real-time and low-latency. Real-time means "respect timing constraint". And there is no definition of "high" and "low". For some applications, a 10ms latency is high, and for others, its low... By the way, the page Real-time communication deserves a major rewrite, since no real-time network is presented (1553, AFDX, TTP, AVB...). I will add it on my TODO list.MarcBoyerONERA (talk) 07:37, 31 August 2017 (UTC)
- --DavidCary (talk) 19:07, 30 August 2017 (UTC)