From owner-freebsd-hackers Tue Nov 4 22:25:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16595 for hackers-outgoing; Tue, 4 Nov 1997 22:25:06 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from zippy.dyn.ml.org (root@tibet-23.ppp.hooked.net [206.80.9.151]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16587 for ; Tue, 4 Nov 1997 22:25:01 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id RAA03258; Tue, 4 Nov 1997 17:41:01 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 4 Nov 1997 17:41:01 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Charles Mott , hackers@hub.freebsd.org Subject: Re: gettimeofday() overhead In-Reply-To: <199711041315.XAA00406@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 4 Nov 1997, Mike Smith wrote: > Unfortunately, this requires access to /dev/kmem, and thus your process > must be running as root. IMHO this isn't really an acceptable tradeoff > unless the application already requires it. Naw, just setgid kmem. > OTOH, if +/- 1 second is good enough, a once-a-second timer and a local > call to gettimeofday() would be a simple and straightforward technique, > as was also suggested. Probably right, but more accuracy within reason can't hurt. - alex