| |||||||||||||
TCP Fast Open: expediting web servicesTCP Fast Open: expediting web servicesPosted Aug 2, 2012 18:46 UTC (Thu) by pr1268 (subscriber, #24648)Parent article: TCP Fast Open: expediting web services
Perhaps I'm not totally understanding what's going on here (high-level): TFO seems more like a user-space fix (i.e. Apache HTTPD, Microsoft IIS, etc.). Are changes to the system calls socket(2), connect(2), etc. the reason this article is on the LWN Kernel Development page? Also, do I assume correctly that both client and server have to support TFO to realize the speed-up mentioned in the article? I certainly don't mean to criticize this article (or its placement here on LWN), just curious instead. Great article, thanks!
(Log in to post comments)
TCP Fast Open: expediting web services Posted Aug 3, 2012 2:22 UTC (Fri) by butlerm (subscriber, #13312) [Link]
Yes, both client and server need support for TCP Fast Open. That support amounts to a change to both the TCP stack and the TCP socket API, both of which are implemented by the kernel. Without kernel support (or a user space TCP implementation and the privileges necessary to use it) neither endpoint can make use of TFO.
|
|||||||||||||