From owner-freebsd-hackers Wed Aug 19 21:34:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13001 for freebsd-hackers-outgoing; Wed, 19 Aug 1998 21:34:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp1635.on.bellglobal.com [206.172.249.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12996 for ; Wed, 19 Aug 1998 21:34:51 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id AAA00436; Thu, 20 Aug 1998 00:33:39 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Thu, 20 Aug 1998 00:33:39 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Garance A Drosihn cc: joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: proposal to not change time_t In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Aug 1998, Garance A Drosihn wrote: > Actually, I think it'd be fine to split the extra 32 bits in half. > Use 16 bits to extend the range of time_t, and sixteen bits to > increase the resolution of timestamps in the filesystem. Hmm... Is there any way the filesystem could force times to be separated by at least one unit (255ths, 1024ths, whatever), and then only resort to using duplicate times when it is forced to by benchmark programs that touch 1024 files per second just for kicks? This would, I'm sure, be rather difficult to write actual code for (and fs coders just abound), but... -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message