Although current Linux systems are using VDSO for implementing clock_gettime/gettimeofday, they still have a nonnegligible overhead(usually more than 100 ns), and the latency is quite unstable(usually between 20 ~ 1000 ns) among different invocations in different frequency, and users have observed discrepant latency among different cpu cores under certain system configuration(e.g. isolcpus). Run test.cc to see how clock_gettime behaves on your machine.
All of these are not good for recording nanosecond timestamps in time-critical tasks where latency of getting timestamp itself should be minimized, nor for benchmarking a general program where stable and reliable timestamp latency is expected.
TSCNS uses rdtsc instruction and simple arithmatic operations to get the same nanosecond timestamp provided by clock_gettime, it's much faster and stable in terms of latency: in less than 10 ns. Actually the whole work is in just 8 consecutive CPU instructions without a function call on current X86-64 architecture.
TSCNS is also thread safe in the most simple and efficient way: it's read-only after initialization, so different threads can keep TSCNS's member variable in the cache for as long as they can.
The precision can be assured by careful calibration which we'll talk about later.
The most important factor in TSCNS is tsc frequency on the system, which it uses to convert tsc to ns. Linux kernel also maintains the same varable named int tsc_khz in arch/x86/kernel/tsc.c, which can be explored by dmesg | grep "tsc: Refined TSC clocksource calibration". Can we just read the frequency in dmesg and use it? No, because it's not accurate: As you can see, kernel measures the frequency in units of 1000, so you can only get a number with 7 digits precision. If you use that value, your ns timestamp will drift apart from system time. But if kernel maintains tsc frequency in khz, how could your timestamp drift with the same value? Because kernel uses int32 multiplication and shift operation to simulate a floating point multiplication(because kernel is prohibited from using floating point), it would result in slight computational error, which in turn results in additional floating point digits after the 7 ones that we couldn't see.
That said, TSCNS needs to find a way to find out those invisible digits: it calibrates. Just like how kernel calibrates its tsc clocksource with the help of hpet, TSCNS synchronizes its user space tsc with kernel tsc(it records two pairs of timestamps in different times to calculate the slope), but in a much more accurate manner(If kernel is not accurate, user has to accept; But if TSCNS is not accurate, user could be upset).
On initialization TNCNS will wait 10 ms to calibrate, and the user can manually calibrate again later to get a more precise tsc frequency.
Yes, do as below:
$ dmesg | grep "tsc: Refined TSC clocksource calibration"
[ 2.524929] tsc: Refined TSC clocksource calibration: 2194.843 MHz
$ ./cheat 2194843
tsc_ghz: 2.1948430943527049
This cheating method should be applicable to both linux-3.X.X and linux-4.X.X versions, but won't work if ntpd is used as it'll discipline the host clock frequency, however ntpdate won't adjust host clock frequency so it's ok to use. Also note that you need to re-calculate tsc_ghz every time system is rebooted, better put it in system boot script.
Take a test to see if you can get full marks, cheater.
Yes.
- The CPU must have
constant_tscfeature, which can searched in/proc/cpuinfo. - NTP/manual time change can not automatically be detected by TSCNS, it's always going forward in a steady speed after init()/calibrate(). But it can be re-inited by user at later times to be re-synced with system clock in a thread safe way, check comments above init() for details.
Initialization in normal case:
TSCNS tn;
tn.init();
// it's recommended to calibrate again a while later:
// std::this_thread::sleep_for(std::chrono::seconds(1));
// tn.calibrate();
Initialization if kernal tsc frequecy could be read and converted by the cheat program mentioned above, and ntpd is not used(ntpdate is ok to use):
TSCNS tn;
tn.init(tsc_ghz);Getting nanosecond timestamp in one step:
uint64_t ns = tn.rdns();Or just recording a tsc in time-critical tasks and converting it to ns in tasks which can be delayed:
// in time-critical task
uint64_t tsc = tn.rdtsc();
...
// in logging task
uint64_t ns = tn.tsc2ns(tsc);test.cc shows:
- Your system's tsc_ghz
- TSCNS's latency
- clock_gettime's latency and how unstable it could be
- If your tsc_ghz is precise enough and if ns from TSCNS is synced up with ns from system
- If tsc from different cores are synced up
Try running it.