Date: Thu, 8 Feb 2001 18:30:03 -0800 (PST) From: Tony Finch <dot@dotat.at> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/24959: proper TCP_NOPUSH/TCP_CORK compatibility Message-ID: <200102090230.f192U3w59054@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/24959; it has been noted by GNATS. From: Tony Finch <dot@dotat.at> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: FreeBSD-gnats-submit@FreeBSD.ORG, Tony Finch <dot@dotat.at> Subject: Re: kern/24959: proper TCP_NOPUSH/TCP_CORK compatibility Date: Fri, 9 Feb 2001 02:22:49 +0000 Garrett Wollman <wollman@khavrinen.lcs.mit.edu> wrote: ><<On Fri, 9 Feb 2001 01:35:01 +0000, Tony Finch <dot@dotat.at> said: > >> I still think it's a bad idea to mix the two features together like >> this: applications should be able to get predictably non-T/TCP >> behaviour if they so choose. > >I'm still puzzled as to what difference you think this makes to an >application. According to the CVS log the reason the test for TF_NOPUSH was added to tcp_listen was so that applications would disallow T/TCP connections by default even if net.inet.tcp.rfc1644 is turned on. Only applications explicitly coded to accept T/TCP connections would do so. I guess this is because T/TCP has a bad reputation. So if servers start turning on TCP_NOPUSH for performance reasons then they also as a side effect start accepting T/TCP TAO connections, which some people would consider to be a bug. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at NORTH UTSIRE SOUTH UTSIRE FORTIES: NORTHWEST BACKING SOUTH OR SOUTHWEST 4 OR 5, DECREASING 3 FOR A TIME. SNOW SHOWERS. MAINLY GOOD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102090230.f192U3w59054>