From owner-freebsd-bugs Thu Feb 8 18:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A502737B401 for ; Thu, 8 Feb 2001 18:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f192U3w59054; Thu, 8 Feb 2001 18:30:03 -0800 (PST) (envelope-from gnats) Date: Thu, 8 Feb 2001 18:30:03 -0800 (PST) Message-Id: <200102090230.f192U3w59054@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tony Finch Subject: Re: kern/24959: proper TCP_NOPUSH/TCP_CORK compatibility Reply-To: Tony Finch Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24959; it has been noted by GNATS. From: Tony Finch To: Garrett Wollman Cc: FreeBSD-gnats-submit@FreeBSD.ORG, Tony Finch Subject: Re: kern/24959: proper TCP_NOPUSH/TCP_CORK compatibility Date: Fri, 9 Feb 2001 02:22:49 +0000 Garrett Wollman wrote: >< 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