upvote
> The NIC could only buffer four packets

Where does the "4" come from? The article's diagram suggests that the NIC's buffer is "~35 KB", though I don't know where that number comes from either (I supposed measuring how long it takes until frames are dropped). "4" seems to be the number of 1 KB packets (the 3+1 from "packet size 1024 bMaxBurst 3"), so a transmission size (protocol-level "window size"), not a buffer size. I guess if you are referring to that as a different "buffer", that makes sense, but it doesn't seem to be the buffer the article is talking about.

But you are right with your main point regarding latency. My statement

> The monitor decides to send the adapter's packets on at only 2 Gbit/s

isn't really right: It's not that the monitor "decided" to only send 41 KiB instead of larger sizes; the 41 KiB is the maximum that the NIC can send because its `bMaxBurst = 3`, and the latency added by the monitor being a USB hub then limits the bandwidth to the mentioned ~2 Gbit/s.

I guess the key point not said anywhere is that `bMaxBurst = 3` and `wMaxPacketSize = 1024 B` are fixed protocol-level parameters that hubs like the monitor have no control over. So the 4 KiB windows are fixed from the NIC through the monitor to the Mac; the monitor cannot e.g. decide to buffer some of those to compensate for the latency it adds.

reply
Not all hubs and computers are equal here. Having experienced this with RTL8153, the combination of the Studio Display and ARM MacBooks is especially bad. Using an Intel MacBook with the display, or a different USB hub instead of the display, gets the full NIC bandwidth.
reply
Fair enough, but I still wouldn’t say that he monitor is at fault. It’s probably not operating outside the USB specification in any way, even if it takes longer to forward messages than other hubs. It may even be multiple hubs, internally.

It’s really the NIC’s fault because its buffer is too small to handle a little extra latency.

reply