From owner-freebsd-hackers  Wed Jan  8 21:02:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id VAA00293
          for hackers-outgoing; Wed, 8 Jan 1997 21:02:26 -0800 (PST)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00276
          for <freebsd-hackers@freebsd.org>; Wed, 8 Jan 1997 21:02:23 -0800 (PST)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id AAA08448; Thu, 9 Jan 1997 00:02:15 -0500 (EST)
Message-Id: <199701090502.AAA08448@whizzo.transsys.com>
X-Mailer: exmh version 2.0alpha 12/3/96
To: Charles Henrich <henrich@crh.cl.msu.edu>
cc: freebsd-hackers@freebsd.org
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: is time() valid in kernel? 
References: <199701090435.XAA06374@crh.cl.msu.edu> 
In-reply-to: Your message of "Wed, 08 Jan 1997 23:35:51 EST."
             <199701090435.XAA06374@crh.cl.msu.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 09 Jan 1997 00:02:15 -0500
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I think that you want to use microtime() to capture the current time 
whilst timestamping events in the kernel.  There's some code that I
submitted a while ago which timestamps messages queued to UDP sockets
based on a socket option; take a look at /sys/netinet/udp_usrreq.c
for the code.

louie