Editing TAP Precision Time APIs
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
[[File:Screenshot_2020-07-01_16.35.12.png|right]] | [[File:Screenshot_2020-07-01_16.35.12.png|right]] | ||
==Workstream #3== | ==Workstream #3== | ||
[https://www.opencompute.org/wiki/Time_Appliance_Project | [https://www.opencompute.org/wiki/Time_Appliance_Project Time Appliances Project] | ||
The ''clock_gettime'' API was designed a couple of decades ago. The time is encoded as number of units between now and a half of a century ago. In theory, this encoding should be sufficient for any use of the phenomenon. For the majority of the systems, representing the time as an offset from the epoch works well. The changes in the last few decades were improvements related to the size of the unit; the unit shrank from seconds to nanoseconds. | The ''clock_gettime'' API was designed a couple of decades ago. The time is encoded as number of units between now and a half of a century ago. In theory, this encoding should be sufficient for any use of the phenomenon. For the majority of the systems, representing the time as an offset from the epoch works well. The changes in the last few decades were improvements related to the size of the unit; the unit shrank from seconds to nanoseconds. | ||