Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clarify time scale semantic issue

Browse Source
This commit is contained in:
kardel 2006-06-10 11:42:07 +00:00
parent 4eff7fe074
commit ced596e186
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
sys/netipsec/ipsec_osdep.h
View File

@ -1,4 +1,4 @@
/* $NetBSD: ipsec_osdep.h,v 1.19 2006/06/10 11:30:37 kardel Exp $ */
/* $NetBSD: ipsec_osdep.h,v 1.20 2006/06/10 11:42:07 kardel Exp $ */
/* $FreeBSD: /repoman/r/ncvs/src/sys/netipsec/ipsec_osdep.h,v 1.1 2003/09/29 22:47:45 sam Exp $ */
/*
@ -167,9 +167,10 @@ if_handoff(struct ifqueue *ifq, struct mbuf *m, struct ifnet *ifp, int adjust)
* 7. Elapsed Time: time_second as time in seconds.
* Original FreeBSD fast-ipsec code references a FreeBSD kernel global,
* time_second().
* (Non-timecounter) NetBSD: kludge #define to use mono_time.tv_sec.
* this does not match the semantics from FreeBSD where time_second
* is UTC time not monotonic or uptime.
* (Non-timecounter) NetBSD: kludge #define to use time.tv_sec.
* XXX is this the right time scale - shouldn't we measure timeout/life times
* using a monotonic time scale (time_uptime, mono_time) - why if the FreeBSD
* base code using UTC based time for this ?
*/
#if defined(__NetBSD__) && !defined(__HAVE_TIMECOUNTER)
#include <sys/kernel.h>