14 Apr
2015
14 Apr
'15
11:05 a.m.
On 14/4/15 10:58 AM, Philip Homburg wrote:
This can be fixed by switching the measurement code to one of the alternative time sources in the Linux kernel that is not subject to these jumps. However that requires touching all time related code in the measurement code.
Is there an established way to work around this on the receiving end? ~paul