News for hackers. Stuff that matters.
Re:It's Always TCP_nodelay by anonymousiam on Monday December 22, 2025 @08:16PM (#46361301)
Thanks for the correction. They're so close to being the same thing that I always call it CSMA/CD. Avoiding a collision is far more preferable than just detecting one.
Re:It's Always TCP_nodelay by reorder9695 on Tuesday December 23, 2025 @07:05AM (#46364638)
Is avoiding a collision always preferable? CSMA/CA has significant overhead (backoff period) for every single frame sent, on a less congested line CSMA/CD has less overhead.
Re:It's Always TCP_nodelay by anonymousiam on Tuesday December 23, 2025 @12:33PM (#46367217)
But CSMA/CD also has a backoff period.
Re:It's Always TCP_nodelay by reorder9695 on Tuesday December 23, 2025 @12:47PM (#46367346)
CSMA/CD only requires that you back off if there actually is a collision. CSMA/CA additionally requires that for every frame sent, after sensing the medium as clear, that you wait for a random amount of time before sending it to avoid collisions. If the medium is frequently clear, CA will still have the overhead of this initial wait where CD will not.
Re:It's Always TCP_nodelay by anonymousiam on Tuesday December 23, 2025 @09:19PM (#46371748)
Depending upon how it's actually implemented, CSMA/CA may have the same (untended?) behavior of CSMA/CD in the sense that setting TCP_NODELAY will also set the backoff timer to zero. It would be interesting to test.

(My other post in this thread mentions it.) https://news.ycombinator.com/item?id=46360209#46361580