From owner-freebsd-arch Fri Nov 17 12: 8:37 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 420DC37B479 for ; Fri, 17 Nov 2000 12:08:35 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA14979; Fri, 17 Nov 2000 13:08:18 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA21404; Fri, 17 Nov 2000 13:08:17 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14869.36912.901949.718314@nomad.yogotech.com> Date: Fri, 17 Nov 2000 13:08:16 -0700 (MST) To: Poul-Henning Kamp Cc: mark@grondar.za, arch@FreeBSD.ORG Subject: Re: new monotime() call for all architectures. In-Reply-To: <26172.974492540@critter> References: <20001117135523.B20231@futuresouth.com> <26172.974492540@critter> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 :-) > > > >OK, how about bogotime(9)? ;) > > It's not returning units of any known time. "bogocount()" maybe... How about 'slushycounter()'? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message