Hacker News new | ask | show | jobs
by attentive 608 days ago
> I look at this article and consider the result pretty much as expected. Why? Because it pushes the flow control out of the kernel (and possibly network adapters) into userspace. TCP has flow-control and sequencing. QUICK makes you manage that yourself (sort of).

This implies that user space is slow. Yet, some(most?) of the fastest high-performance TCP/IP stacks are made in user space.
2 comments
formerly_proven 608 days ago
If the entire stack is in usermode and it's directly talking to the NIC with no kernel involvement beyond setup at all. This isn't the case with QUIC, it uses the normal sockets API to send/recv UDP.
link
WesolyKubeczek 608 days ago
You have to jump contexts for every datagram, and you cannot offload checksumming to the network hardware.
link