From owner-freebsd-stable  Sun Jan 23  8:36:27 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id D3A2314CEA
	for <stable@FreeBSD.ORG>; Sun, 23 Jan 2000 08:36:15 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA04102;
	Sun, 23 Jan 2000 11:36:09 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id LAA43285;
	Sun, 23 Jan 2000 11:36:08 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200001231636.LAA43285@rtfm.newton>
Subject: Re: kern/13644
In-Reply-To: <000a01bf655e$314bb6c0$021d85d1@youwant.to> from David Schwartz
 at "Jan 22, 2000 08:56:21 pm"
To: David Schwartz <davids@webmaster.com>
Date: Sun, 23 Jan 2000 11:36:08 -0500 (EST)
Cc: Mikhail Teterin <mi@kot.ne.mediaone.net>, stable@FreeBSD.ORG
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

David Schwartz once stated:

=> =FreeBSD:
=> ==> =>  If timeout is a non-nil pointer, it specifies a maximum
=> ==> =>  interval to wait for the selection to complete.

= While  the  pthreads case  is  clearly  a  bug,  in the  other  cases,
=FreeBSD's behavior seems  correct. The timeout is bounding  the time we
=wait for  the selection to complete.  However, the time to  get back to
=the  task includes  more  than  just the  time  spent  waiting for  the
=selection to complete.

It  appears, that  you,  as well  as other  developers,  speak from  the
implementation point of view. I only  look at the man-page. The man page
says, the time out  is the UPPER limit. The pthread  case is broken even
further...

Bruce,  it appeared,  tried to  say the  man-page is  broken, while  the
implementation is correct,  but remains  silent despite  me quoting  all
sorts of  other man-pages from all  sorts of other vendors,  who all say
(almost) the same thing:

	that the timeout is indeed the UPPER limit, and not the LOWER.

		-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message