On Mon, 19 May 2014 13:25:42 EDT erik quanstrom <quans...@quanstro.net> wrote: > > i would be very surprised if there were any gain in accuracy. the > accuracy is going to be dominated by the most inaccurate term, and > that's likely going to be timesync, and on the order of milliseconds.
Speaking of time and accuracy.... I am adding some logic to synchronize with the PPS signal from the GPS device that I hooked up to a RaspberryPi. With this change the TOD clock should be accurate to within 10 to 20 µs. So I for one welcome the new syscall! [Though its introduction could've been better managed] But using a TOD clock for measuring performance seems wrong since it will also have to account for leapseconds (at the moment timesync happily ignores leapseconds).
