Subject: Re: monotonic time (was Re: CVS commit: basesrc)
To: Simon Burge <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 08/24/1999 19:11:14
On Wed, 25 Aug 1999 11:06:05 +1000
Simon Burge <firstname.lastname@example.org> wrote:
> Konrad Schroder wrote:
> > [[ cvs commit details for lfs_cleanerd deleted ]]
> > If "time"
> > is not monotonically increasing (e.g. clock is slaved to another system)
> > the optimization will result in segments being treated as corrupt
> > (uncleanable).
> I've wondered about this once or twice in the past. At a quick glance,
> it looks like we don't have a monotonic time source in the kernel that
> won't wrap around. ticks (in kern_clock.c) comes close, but on a 1024Hz
> 32 bit machine it wraps around every 24ish days... This monotonic value
> could be returned to userland with somethink like Solaris' gethrtime().
We have `mono_time' ... this is like `time', but is monotonically increasing,
hence the name.
-- Jason R. Thorpe <email@example.com>