Date: Wed, 29 Apr 1998 00:47:14 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Terry Lambert <tlambert@primenet.com> Cc: root <root@enigami.com>, current@FreeBSD.ORG Subject: Re: mono_time? Message-ID: <Pine.BSF.3.95.980429004631.29103B-100000@current1.whistle.com> In-Reply-To: <199804290236.TAA08885@usr01.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
but it's been replaced bu soething else.. when all the clocks changed recently On Wed, 29 Apr 1998, Terry Lambert wrote: > > Can anyone tell me what is going on with mono_time? There are a couple of > > files in the kernel source that use it, as does CAM, and there is even a > > man page that references it, but it doesn't seem to actually be defined > > anywhere! > > > > Now, I am guessing that this was in vogue a while back, and is now a passing > > fad, as the CAM stuff built in the past, but doesn't (at least for me) any > > more. So, what should replace it? > > The system clock can be drift adjusted by syncing with an external > timebase. > > If the drift adjustment is for a fast clock, this will cause time > to go back into the past. > > If time goes back into the past, some events that should not recurr > will end up being "replayed" as time moves into the future again. > > To combat this, you need a clock which is not subject to drift > adjustment. > > Such a clock would be a "monotonically increasing value". > > Or a "mono_time", for short. > > > 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-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980429004631.29103B-100000>