Date:Sat, 14 Apr 2018 05:24:40 +1000
From:matthew green
Message-ID: <8304.1523647...@splode.eterna.com.au>
| i'd recommend going for at least 100ns intervals, if not 10ns.
I have implemented it in a way that the precision can be controlled
by
> On Apr 13, 2018, at 12:24 PM, matthew green wrote:
>
> we could also make this only relevant on ports with cpus that
> have faster cpus, leaving older systems with smaller logs.
> (the seconds part shouldn't change, i think, as there is no
> reason to believe any port has
Robert Elz writes:
> Date:Fri, 13 Apr 2018 05:21:16 -0400
> From:"Christos Zoulas"
> Message-ID: <20180413092116.b3b08f...@cvs.netbsd.org>
>
> | src/sys/kern: subr_prf.c
>
> | make this narrower by popular request.
>
> Would it perhaps be
In article <12933.1523625...@jinx.noi.kre.to>,
Robert Elz wrote:
>Date:Fri, 13 Apr 2018 05:21:16 -0400
>From:"Christos Zoulas"
>Message-ID: <20180413092116.b3b08f...@cvs.netbsd.org>
>
> |src/sys/kern: subr_prf.c
>
> |
Date:Fri, 13 Apr 2018 05:21:16 -0400
From:"Christos Zoulas"
Message-ID: <20180413092116.b3b08f...@cvs.netbsd.org>
| src/sys/kern: subr_prf.c
| make this narrower by popular request.
Would it perhaps be reasonable to just print