On 11/08/2017 05:04 PM, Fred Smith wrote:
Just for example, the faster you pour packets down the pipe, the more likely that one of 'em is going to "collide" with a packet from some other system/process that also wants to use the network. When collisions occur, both systems that are sending stop, back off for a more or less random amount of time then try again. In general, this allows one of 'em to get finished before the other one tries again. and there's the similar situation where the computer you're trying to use to send a big file (for a speed test, e.g.) goes to send one of its packets and finds someone else already using the wire. so it, again. has to back off for some more-or-less random amount of time and try again later. Systems will listen on the wire to see if it is in use and if not will start sending. if two systems do that at the same time, that's where collisions come from.
This is what happens with wireless, but not on Ethernet any longer. Ethernet is all point-to-point, full-duplex. A switch passes the packets around between the links, but it has buffering so you don't lose the packets when you get multiple links sending to the same port. I suppose it's possible if you have multiple links sending lots of data through one other link that the switch could run out of buffer space. But in that case you're already over your bandwidth limit and transfer speeds will have to be throttled anyway.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
