Wall-time is sensitive to tick rate in VxWorks 6.4 kernels targeting 2400s
Duane Voy reports:
Does any of the MOOC, ACNet, etc. code that we users load for normal front-end operation use the following?
struct timespec ts;
clock_gettime( CLOCK_REALTIME, &ts );
I have found another issue in the VxWorks kernel that we use in the Delivery Ring front-ends. When I set the system clock rate faster than the default 100 ticks per second, the time value returned by the above code speeds up proportionally. So in my case changing from the default 100 Hz to 500 results in time appearing to pass 5 times faster than reality!
I can imagine this having subtle effects in the control system software. Could this cause the network address tables being flushed without explanation for example?
He also provided evidence that it's used extensively throughout our products.