From owner-freebsd-net Wed Apr 21 23: 1:47 1999 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 3CB4815179 for ; Wed, 21 Apr 1999 23:01:25 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA17004; Wed, 21 Apr 1999 22:57:48 -0700 (PDT) Message-Id: <199904220557.WAA17004@implode.root.com> To: Alex Rousskov Cc: freebsd-net@FreeBSD.ORG Subject: Re: _Some_ acks delayed for 200 msec? In-reply-to: Your message of "Wed, 21 Apr 1999 23:46:00 MDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 21 Apr 1999 22:57:48 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Wed, 21 Apr 1999, David Greenman wrote: > >> I'm not familiar with what your application is doing over the wire, so I >> can only speculate. It sounds to me as though TCP_NODELAY wasn't actually >> set properly on the socket. Keep in mind that this option is not inherited >> in the accept()'ed file descriptor and thus the option must be set on that >> descriptor and not on the listen() socket. > >Oof! I've trusted the accept(2) man page that says: > > The accept() argument extracts the first connection request > on the queue of pending connections, creates a new socket with the > same properties of s and allocates a new file descriptor for the > socket. > >Apparently, "same properties" does not include TCP_NODELAY! This is the classic behavior of BSD, but I nonetheless think it's a bug not to duplicate certain options (especially TCP_NODELAY). It should probably be fixed. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message