News for hackers. Stuff that matters.

A comment on Working Group Last Call: QUIC protocol drafts. Parent comment

Re:Working Group Last Call: QUIC protocol drafts by cryptonector on Wednesday June 10, 2020 @12:14PM (#23478787)
The fact that UDP involves much smaller PCBs than TCP alone will drive adoption of HTTP/3 because it will free up a fair bit of memory.

More availability of HTTP version gateways in load balancers and other reverse proxies is all that's needed, and that's coming along.

[ Parent | on HN ]
Re:Working Group Last Call: QUIC protocol drafts by moreati on Wednesday June 10, 2020 @04:58PM (#23482031)
Protocol Control Block for anyone else wondering https://www.oreilly.com/library/view/tcpip-illustrated/02016...
[ Parent | on HN ]
Re:Working Group Last Call: QUIC protocol drafts by the8472 on Wednesday June 10, 2020 @06:09PM (#23482750)
You still need to keep your unacknowledged data buffered somewhere. If the kernel isn't holding it then it's in userspace.
[ Parent | on HN ]
Re:Working Group Last Call: QUIC protocol drafts by microcolonel on Wednesday June 10, 2020 @01:07PM (#23479468)
More specifically no PCB, for UDP itself.
[ Parent | on HN ]
Re:Working Group Last Call: QUIC protocol drafts by cryptonector on Wednesday June 10, 2020 @06:10PM (#23482755)
It's not nil. For "connected" UDP sockets, it's smaller than TCP's, but not nil because, well, buffers. And for non-connected UDP sockets there's still buffers. The main thing is that you can have much less buffer space because you might always be willing to drop packets. Ultimately you can have much lower memory pressure from those buffers and the smaller PCBs.
[ Parent | on HN ]