Date: Wed, 26 Jul 2006 08:45:32 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: dwmalone@maths.tcd.ie Cc: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, csjp@FreeBSD.org, cvs-all@FreeBSD.org, phk@phk.freebsd.dk, sam@errno.com, jkim@FreeBSD.org Subject: Re: cvs commit: src/sys/net bpf.c Message-ID: <20060726.084532.-1350498521.imp@bsdimp.com> In-Reply-To: <200607252123.aa75409@salmon.maths.tcd.ie> References: <11815.1153858333@critter.freebsd.dk> <200607252123.aa75409@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200607252123.aa75409@salmon.maths.tcd.ie>
David Malone <dwmalone@maths.tcd.ie> writes:
: > I'm not sure I know what you mean by "trivial timecounter", but the
: > only reason we don't have a way to deregister a timecounter yet is
: > that so far I'm probably the only one who have ever need it :-)
:
: I was thinking about this recently too actually, as I was going to
: see how good the 64 bit counter on ath cards was in comparison to
: other things that were available. I'm not sure how much complexity
: a timecounter that could vanish at any moment would introduce - I
: didn't get that far yet.
I wrote a time counter and driver for the AT91RM9200 based on a 16-bit
counter that could also be used to timestamp a pps in about a day.
Timecounters are trivial to implement, assuming that you can read a
counter atomically.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060726.084532.-1350498521.imp>