From owner-cvs-src@FreeBSD.ORG Tue Nov 29 04:05:44 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CAF716A41F; Tue, 29 Nov 2005 04:05:44 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF27843D5D; Tue, 29 Nov 2005 04:05:43 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAT45XLV013678; Tue, 29 Nov 2005 15:05:33 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAT45SHl029187; Tue, 29 Nov 2005 15:05:32 +1100 Date: Tue, 29 Nov 2005 15:05:27 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86d5kkbygy.fsf@xps.des.no> Message-ID: <20051129145321.E33975@delplex.bde.org> References: <200511270055.jAR0tIkF032480@repoman.freebsd.org> <20051127230412.H28222@delplex.bde.org> <20051127125844.V81764@fledge.watson.org> <20051128002937.T17822@epsplex.bde.org> <86d5kkbygy.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-682181516-1133237127=:33975" Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Robert Watson , cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/sys time.h src/sys/kern kern_time.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 04:05:44 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-682181516-1133237127=:33975 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 28 Nov 2005, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Bruce Evans writes: >> I can see a use for making a timestamp after select() returns, not for >> timeout purposes since the timeout should normally be for emergencies an= d >> it's relative so it doesn't need the current time, but just to record wh= en >> things happen. > > IIRC, POSIX allows (but does not require) select(2) to modify the > provided struct timeval to reflect how much time remains until the > original deadline. Personally, I would find that very useful... This would be hard to use because it is unportable. IIRC, Linux did or does this and found mainly bugs with broken applications expecting the timeval to be const. Even with this, applications would still need to know when select() was called to recover the time when it returned. Adding deltas from select() to a previous timestamp wouldn't work very well the relative error in the deltas is large for small deltas (unless you pessimize select() to get a precise timestamp). Bruce --0-682181516-1133237127=:33975--