Don't use rdtsc for high res timestamp on Linux as it's highly inaccurate (for now)
git-svn-id: https://svn.pjsip.org/repos/pjproject/trunk@387 74dad513-b988-da41-8d7b-12977e46ad98
This commit is contained in:
parent
4fda1ebb07
commit
2a81634f62
|
@ -23,7 +23,10 @@
|
|||
#include <stdlib.h>
|
||||
#include <ctype.h>
|
||||
|
||||
#if defined(PJ_HAS_PENTIUM) && PJ_HAS_PENTIUM!=0
|
||||
#if defined(PJ_HAS_PENTIUM) && PJ_HAS_PENTIUM!=0 && \
|
||||
defined(PJ_TIMESTAMP_USE_RDTSC) && PJ_TIMESTAMP_USE_RDTSC!=0 && \
|
||||
defined(PJ_M_I386) && PJ_M_I386!=0 && \
|
||||
defined(PJ_LINUX) && PJ_LINUX!=0
|
||||
static int machine_speed_mhz;
|
||||
static pj_timestamp machine_speed;
|
||||
|
||||
|
|
|
@ -99,6 +99,9 @@ static int timestamp_accuracy()
|
|||
"%d msec",
|
||||
(pj_uint32_t)(diff * 1000000 / freq.u64),
|
||||
msec));
|
||||
} else {
|
||||
PJ_LOG(3,(THIS_FILE, "....good. Timestamp is accurate down to"
|
||||
" nearest usec."));
|
||||
}
|
||||
|
||||
return 0;
|
||||
|
|
Loading…
Reference in New Issue