Protected Member Functions
|virtual bool||DoRealtime (void)|
|Return true if this synchronizer is actually synchronizing to a realtime clock. The simulator sometimes needs to know this. |
|virtual uint64_t||DoGetCurrentRealtime (void)|
|Retrieve the value of the origin of the underlying normalized wall clock time in nanosecond units. |
|virtual void||DoSetOrigin (uint64_t ns)|
|Establish a correspondence between a simulation time and a wall-clock (real) time. |
|virtual int64_t||DoGetDrift (uint64_t ns)|
|Declaration of method used to retrieve drift between the real time clock used to synchronize the simulation and the current simulation time. |
|virtual bool||DoSynchronize (uint64_t nsCurrent, uint64_t nsDelay)|
|Wait until the real time is in sync with the specified simulation time. |
|virtual void||DoSignal (void)|
|Declaration of the method used to tell a posible simulator thread waiting in the DoSynchronize method that an event has happened which demands a reevaluation of the wait time. |
|virtual void||DoSetCondition (bool cond)|
|Declaration of the method used to set the condition variable that tells a posible simulator thread waiting in the Synchronize method that an event has happened which demands a reevaluation of the wait time. |
Enable this synchronizer using:
DefaultValue::Bind ("Synchronizer", "WallClockSynchronizer");
before calling any simulator functions.
The simulation clock is maintained as a 64-bit integer in a unit specified by the user through the TimeStepPrecision::Set function. This means that it is not possible to specify event expiration times with anything better than this user-specified accuracy.
There are a couple of more issues at this level. Posix clocks provide access to several clocks we could use as a wall clock. We don't care about time in the sense of 0430 CEST, we care about some piece of hardware that ticks at some regular period. The most accurate posix clock in this respect is the CLOCK_PROCESS_CPUTIME_ID clock. This is a high-resolution register in the CPU. For example, on Intel machines this corresponds to the timestamp counter (TSC) register. The resolution of this counter will be on the order of nanoseconds.
Now, just because we can measure time in nanoseconds doesn't mean we can put our process to sleep to nanosecond resolution. We are eventualy going to use the function clock_nanosleep () to sleep until a simulation Time specified by the caller.
MORE ON JIFFIES, SLEEP, PROCESSES, etc., as required
Nanosleep takes a struct timespec as an input so we have to deal with conversion between Time and struct timespec here. They are both interpreted as elapsed times.
|virtual void ns3::WallClockSynchronizer::DoSetCondition||(||bool||)||
|virtual void ns3::WallClockSynchronizer::DoSignal||(||void||)||