Hacker News new | past | comments | ask | show | jobs | submit
> In this case I am referring to the notional "transmit buffer", which is 4 in the non-working case

Then I agree with what you were saying. Those 4 * 1 KiB are a protocol-level size (similar to the TCP window size), not an actual "buffer".

> Increasing the number of packets in flight does not change the bandwidth, it only improves latency sensitivity (i.e. you can fire more data before requiring an ACK).

That I don't fully follow. To me, the measured bandwidth includes all the effects of ACKs etc. If the the protocol demands that you can have at max 4 * 1 KiB unACKed in flight so you're waiting around for ACKs and not snding data, then increasing the number of packets in flight to 8 would 2x the bandwidth.

> The added hop of latency however makes [it] insufficient to cover the latency.

I agree with that, see also my newer reply https://news.ycombinator.com/item?id=50592931

I this context, I also agree with your original statement; I misunderstood what you referring to with "buffer" (meaning the window, not actual storage), and "bandwidth" (where I think you're referring to the 5 Gbit/s nominal bandwidth of the bus, irrespective of the fact that the effective bandwidth of data sent is much lower due to requiring ACKs for small data).