.png){kind=icon}
.png){kind=icon}
Return
The Case for Feed-Forward Clock Synchronization
.png){kind=icon}
OA
AI
DOI：10.1109/TNET.2011.2158443.png)
.png){kind=icon}
.png){kind=icon}
Share.png){kind=icon}
Save
Abstract
En 中文
Variable latencies due to communication delays or system noise is the central challenge faced by time-keeping algorithms when synchronizing over the network. Using extensive experiments, we explore the robustness of synchronization in the face of both normal and extreme latency variability and compare the feedback approaches of ntpd and ptpd (a software implementation of IEEE-1588) to the feed-forward approach of the RADclock and advocate for the benefits of a feed-forward approach. Noting the current lack of kernel support, we present extensions to existing mechanisms in the Linux and FreeBSD kernels giving full access to all available raw counters, and then evaluate the TSC, HPET, and ACPI counters' suitability as hardware timing sources. We demonstrate how the RADclock achieves the same microsecond accuracy with each counter.
Keywords:
Advanced configuration and power interface (ACPI)
clock source
feed-forward
high-precision event timer (HPET)
IEEE-1588
latency
Robust Absolute and Difference clock (RADclock)
robustness
synchronization
timestamp counter (TSC)
AI Summary
Key information extracted from the uploaded paper, including a brief overview, abstract, background, key highlights, visual analysis, and future outlook.
Journal
I
IF:
3.6
Papers:
4.4K
Citations:
9.5K