Hi, Can the vlib_time_now return way-off different values in different workers threads/main thread even if it is called around the same time ?
I have the following situation -- I initialize a per worker data structure in the main thread with a call to vlib_time_now (by passing the vm of the corresponding worker threads). Then the workers start calling the vlib_time_now eventually. What I find at the start is that vlib_time_now return value as observed in the call in worker's context is way ahead of the vlib_time_now which was seeded in the initialization for that worker by the main thread. This does not happen on all setups. So wanted to find out if this is possible at all. At the moment I cured the problem by doing the initial seeding in the worker itself for the very first time so that the relative times seen by worker itself in calls to vlib_time_now are good. I am on VPP 18.01 Regards -Prashant
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11345): https://lists.fd.io/g/vpp-dev/message/11345 Mute This Topic: https://lists.fd.io/mt/28274759/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
