From owner-freebsd-hackers Tue Nov 4 22:44:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17526 for hackers-outgoing; Tue, 4 Nov 1997 22:44:00 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17519 for ; Tue, 4 Nov 1997 22:43:53 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (tc-if2-23.ida.net [208.141.171.80]) by srv.net (8.8.5/8.8.5) with SMTP id XAA09623; Tue, 4 Nov 1997 23:43:17 -0700 (MST) Date: Tue, 4 Nov 1997 23:42:43 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Alex cc: Mike Smith , hackers@hub.freebsd.org Subject: Re: gettimeofday() overhead In-Reply-To: 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, Alex wrote: > 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. > At this point, accessing the kernel time variable from user space is mainly a point of interest (this is the hackers group, right?). I can read up on how to access /dev/kmem, but how is the kernel symbol table accessed? -- Charles Mott