From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <73d0faddf32ce1bc1d64f05fd113dece@proxima.alt.za>
To: 9fans@9fans.net
Date: Mon, 19 May 2014 16:01:22 +0200
From: lucio@proxima.alt.za
In-Reply-To: <9c783f88daab742653c28a777599956b@brasstown.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] syscall 53
Topicbox-Message-UUID: e84971bc-ead8-11e9-9d60-3106f5b1d025

> i indirectly heard "go needs it", but that is not really a reason
> i can understand technically.  why must it be a system call?

Actually, Go raised an important alert, quite indirectly: when using
high resolution timers, the issue of opening a device, reading it and
converting the input value to a binary value can and in this case is
very expensive.

Curiously, the actual symptom - I cannot remember how it came about -
was that using the timer leaked file descriptors, or, more likely,
gave the impression of leaking file descriptors.  But the reality is
that nanosecond accuracy cannot be achieved from reading a device by
conventional means.

++L