3 ms·
That paper is a real disappointment with the places it doesnt go. Specifically, if QUIC is to have high performance and high power efficiency, just batching th
by londons_explore 6y ago
That paper is a real disappointment with the places it doesnt go.
Specifically, if QUIC is to have high performance and high power efficiency, just batching the packets isn't enough. Think of a usecase - a CDN wants to be able to send a block of data from disk to a client. It should be able to direct that data from the SSD to the network card without the CPU touching the data at all.
On the receive side, a mobile device should be able to download a big file to ram or flash with the main CPU asleep most of the time.
That means the network device should be encrypting the packets, doing the pacing, doing the retries, etc.
It may be that a quic specific set of options or syscalls is best for that, or it might be that the application should provide a "this is how to send my data" set of bytecode which the network hardware executes repeatedly.
But just batching UDP packets is a half way measure which isn't in the direction of the final goal.
- Klinky 6y agoWouldn't this mean the networking interface is now Layer 7? It has to understand how QUIC works. Sounds like Smart NIC, though that seems mainly enterprise focused.
- dpe82 6y agoOne step at a time. Right, that paper doesn't introduce life-shattering innovation but rather just fixes a long-standing issue with UDP performance in the Linux kernel. That ain't nothing. A large motivator to develop and deploy QUIC is that by implementing much of the stack as a userspace library the protocol can be iterated on at a pace impossible with TCP. BBR congestion control experiments are a great example of that; there's enormous value in quick iteration, even at the cost of compute efficiency. I agree with your sentiment though; I have to imagine eventually the protocol will settle down and hardware acceleration will become a thing - but imho not to the degree you propose.