Date: Fri, 17 Nov 2000 14:10:37 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: Nate Williams <nate@yogotech.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, mark@grondar.za, arch@FreeBSD.ORG Subject: Re: new monotime() call for all architectures. Message-ID: <20001117141037.E19895@prism.flugsvamp.com> In-Reply-To: <14869.36912.901949.718314@nomad.yogotech.com> References: <20001117135523.B20231@futuresouth.com> <26172.974492540@critter> <14869.36912.901949.718314@nomad.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 17, 2000 at 01:08:16PM -0700, Nate Williams wrote: > > >> >> 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()'? falseticker()? (Okay, probably too NTP specfic) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001117141037.E19895>