From owner-freebsd-chat@FreeBSD.ORG Mon Mar 26 14:34:43 2007 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10D0716A406 for ; Mon, 26 Mar 2007 14:34:43 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 6325B13C468 for ; Mon, 26 Mar 2007 14:34:42 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so1616123ugh for ; Mon, 26 Mar 2007 07:34:37 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=gi4hfv/JMrxyX6XS6JTk6cxGR041HaEq6qTs+EuwX+Q7ZqcQmC8X1O0teE9mynkVfWts5/RGOz9E0H0IT8yYuNwDb1YEBQjQGTU1+s0j7nQM//eT5lsX/phTAonAf7iWWYAXByyy921MO/3GLCHgI5Hz/guDacNGR4Ob0UiGGRI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=VHYb3dw6lHAcjcXpVB8tybSfOzzZ5J9pfGVYHHJf5YfF6XBeqIVDLdMPmb3OcquRivc1D45XBkmIOraZ0GEeCCeY0wvQVRUk4ntAYUTnLUbcnYmzEZIPbSj6/dTDD59TvmmF0pR7oGezaX0RsD6Tuuss+//jIG918d9d4mrUd54= Received: by 10.67.93.6 with SMTP id v6mr12257023ugl.1174919677601; Mon, 26 Mar 2007 07:34:37 -0700 (PDT) Received: from ?192.168.123.111? ( [84.2.7.169]) by mx.google.com with ESMTP id e1sm8115240ugf.2007.03.26.07.34.35; Mon, 26 Mar 2007 07:34:36 -0700 (PDT) Message-ID: <4607DA48.6040802@gmail.com> Date: Mon, 26 Mar 2007 16:35:52 +0200 From: deeptech71@gmail.com User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-chat@freebsd.org References: <200703251900.l2PJ0Z8w058298@lurza.secnetix.de> <4606D88E.4080503@gmail.com> <20070325215731.GA1517@kobe.laptop> <4607D66B.4070800@gmail.com> In-Reply-To: <4607D66B.4070800@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 64bit timestamp X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2007 14:34:43 -0000 deeptech71@gmail.com wrote: > Giorgos Keramidas wrote: >> On 2007-03-25 22:16, deeptech71@gmail.com wrote: >>> Oliver Fromme wrote: >>>> Ideally, two consecutive, non-parallel operations should give >>>> two different timestamps. That applies to creating or >>>> touching a file or other kind of resource, or even just >>>> calling the gettimeofday() function from within the same >>>> thread, or whatever. In reality that isn't the case today for >>>> FreeBSD for other reasons, but the timestamp accuracy of UFS2 >>>> would certainly be sufficient for that. >>> Actually, my intend wasn't to use it in filesystems, but >>> server-client apps, such as games, where 32bit integer timers >>> must be restarted every 3 weeks >> >> That's a bug in the applications themselves. The gettimeofday() >> call in any modern UNIX returns a `struct timeval', which >> contains *both* a time_t value of the current time with >> second-level accuracy and a tv_usec member with millisecond >> accuracy (or at least an approximation of a timestamp with >> millisecond accuracy). >> >> Any userlevel application which uses userlevel time counters and >> requires a restart every two or three weeks, because these >> userlevel timecounters have rolled back to zero, is broken and >> should be fixed. > > No, it's not a bug, the server and client communicates with lots of > packets timestamped with a synchronized time, and sending 64bit > timestamps would be too much bandwidth consuming. There's a restart > demand every hour or so, so it's not a problem... but the server is > limited for max 3 weeks. > sry, i wanted to say, 48bit or 64bit is acceptable, but 96bit is not