>>> Tal Mizrahi <tal.mizrahi.phd@xxxxxxxxx> schrieb am 03.03.2020 um 07:05 in
Nachricht
<11168_1583215605_5E5DF3F5_11168_1246_1_CABUE3X=nhuzy1UMEFr1tuJNw9hY_ewYHqoX4fCq
_ZXThNK82g@xxxxxxxxxxxxxx>:
Hi!
I found another little issue while wondering what the document says about "precision":
In "5. Synchronization Aspects" the text claims "Further considerations may be discussed in this section, such as the required timestamp accuracy and precision". However "precision" is not mentioned there.
Basically I feel the definitions given there for precision and accuracy are quite vague.
Personally I feel the concept of precision (as opposed to resolution) should be handled.
Unfortunately POSIXC clock_getres() seems to return the precision for example:
The function clock_getres() finds the resolution (precision) of the
specified clock clk_id, and, if res is non-NULL, stores it in the
struct timespec pointed to by res. The resolution of clocks depends on
the implementation and cannot be configured by a particular process.
If the time value pointed to by the argument tp of clock_settime() is
not a multiple of res, then it is truncated to a multiple of res.
Regards,
Ulrich
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
