From owner-freebsd-current Thu Apr 2 14:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15132 for freebsd-current-outgoing; Thu, 2 Apr 1998 14:01:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15112 for ; Thu, 2 Apr 1998 14:00:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id XAA00368; Thu, 2 Apr 1998 23:58:24 +0200 (CEST) To: pb@fasterix.freenix.org (Pierre Beyssac) cc: gljohns@bellsouth.net (Glenn Johnson), freebsd-current@FreeBSD.ORG Subject: Re: error when compiling kernel with SOFTUPDATES In-reply-to: Your message of "Thu, 02 Apr 1998 22:55:49 +0200." <19980402225549.AY32283@@> Date: Thu, 02 Apr 1998 23:58:24 +0200 Message-ID: <366.891554304@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980402225549.AY32283@@>, Pierre Beyssac writes: >Poul-Henning Kamp writes: >> change "tv = time" to "getmicrotime(&tv);" > >Should getmicrotime() really be prefered in all cases ? From >kern_clock.c, it looks like microtime() has much less overhead when >you don't need a very accurate timestamp: You got that backwards, look at the code as well as the comments. microtime is expensive but precise. getmicrotime is fast but up to 1/hz old. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message