From owner-freebsd-arch Fri Nov 17 11:31:13 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 0BD1637B479; Fri, 17 Nov 2000 11:31:11 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAHJr9726016; Fri, 17 Nov 2000 20:53:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: John Hay , mark@grondar.za, arch@FreeBSD.ORG Subject: Re: new monotime() call for all architectures. In-Reply-To: Your message of "Fri, 17 Nov 2000 11:24:00 PST." Date: Fri, 17 Nov 2000 20:53:09 +0100 Message-ID: <26014.974490789@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Ok, I just thought the "mono" in his function name is for monotonic. If >> you are staying on one processor it will work, but if the timestamps >> have scheduling inbetween the timestamps and you land on a different >> processor it won't be monotonic anymore. > >It's close enough. :) If it isn't dealing properly with async PCC/TSC counters on SMP machines it shouldn't be called "monoanyting". I guess I totally object to the name now :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message