From owner-freebsd-current Tue Apr 28 19:36:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15560 for freebsd-current-outgoing; Tue, 28 Apr 1998 19:36:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15555 for ; Tue, 28 Apr 1998 19:36:39 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA06348; Tue, 28 Apr 1998 19:36:29 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd006293; Tue Apr 28 19:36:20 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA08885; Tue, 28 Apr 1998 19:36:18 -0700 (MST) From: Terry Lambert Message-Id: <199804290236.TAA08885@usr01.primenet.com> Subject: Re: mono_time? To: root@enigami.com (root) Date: Wed, 29 Apr 1998 02:36:18 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199804280114.VAA02892@singularity.enigami.com> from "root" at Apr 27, 98 09:14:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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