Date: Thu, 20 Aug 1998 05:21:31 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: ac199@hwcn.org Cc: drosih@rpi.edu, joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: proposal to not change time_t Message-ID: <199808200521.WAA14742@usr02.primenet.com> In-Reply-To: <Pine.BSF.3.96.980820003001.392B-100000@localhost> from "Tim Vanderhoek" at Aug 20, 98 00:33:39 am
next in thread | previous in thread | raw e-mail | index | archive | help
> 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...
Trivial, actually...
if( oldsecond == current second) {
savesecond = currentsecond
saveunique = ++unique;
} else {
savesecond = currentsecond
saveunique = unique = 0;
}
A 16 bit value for saveunique for content modification time should
suffice, but there is sufficient spare for all thre timestamps (64
bit, 1 second resolution) should that be deemed necessary.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808200521.WAA14742>