From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 19 May 2014 13:22:05 -0400
To: lucio@proxima.alt.za, 9fans@9fans.net
Message-ID: <ae955481d7ff84e95d3a34bbc3e58d4b@ladd.quanstro.net>
In-Reply-To: <5d84162478be5e396c64b392d02b94ac@proxima.alt.za>
References: <5d84162478be5e396c64b392d02b94ac@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] syscall 53
Topicbox-Message-UUID: e8728bf6-ead8-11e9-9d60-3106f5b1d025

On Mon May 19 13:17:59 EDT 2014, lucio@proxima.alt.za wrote:
> > also, one cannot get close to 1ns precision with a system call.  a sy=
stem call
> > takes a bare minimum of 400-500ns on 386/amd64.
>=20
> Sure, but accessing /dev/time is, if I guess right, orders of
> magnitude slower, specially if you have to open the device first.

the full operation open/read/close/convert takes 6=C2=B5s on my machine,
and a system call takes about 750ns.

getting the kitchen time should not need better than 6=C2=B5s.  if this
were relative timing, i would understand, but it's not.

- erik