VOID
NdisMSetTimer(
IN PNDIS_MINIPORT_TIMER Timer,
IN UINT MillisecondsToDelay
);
NdisMSetTimer sets a timer to fire after a specified interval, thereby running an associated MiniportTimer function when the timer fires.
NdisMSetTimer causes the driver-supplied MiniportTimer function, which was associated with the timer object when MiniportInitialize called NdisMInitializeTimer, to run once after the given MillisecondsToDelay expires. Execution of the MiniportTimer function associated with the Timer passed to NdisMSetTimer is episodic, rather than periodic. A miniport must call NdisMSetTimer each time the associated timer function should be run.
By contrast, NdisMSetPeriodicTimer causes the associated MiniportTimer function to be run repeatedly whenever the given MillisecondsPeriod expires. At the initial call to NdisMSetPeriodicTimer, the timer object is queued until the MillisecondsPeriod expires, when the MiniportTimer function is run and the timer object is automatically requeued for the next interval.
As a general rule, a miniport should allocate and initialize two timer objects if it calls both NdisMSetPeriodicTimer and NdisMSetTimer. Such a driver is likely to have two MiniportTimer functions with different functionality, each associated with a particular timer object when it is initialized with NdisMInitializeTimer. For example, a MiniportTimer function that runs periodically might poll device state at regular intervals, while another MiniportTimer function might retry a particular runtime operation only if it times out on the NIC.
If a miniport calls NdisMSetTimer, NdisMCancelTimer, or NdisMSetPeriodicTimer with the same Timer pointer originally passed to NdisMSetTimer before the originally specified MillisecondsToDelay has expired, the current call cancels its preceding call to NdisMSetTimer. Any call to NdisMSet..Timer resets the given timer to expire at the interval specified in the most recent call and causes the associated MiniportTimer function to run when the most recently specified interval has expired.
Timer resolution on the host varies. Consequently, calling NdisMSetTimer with very small time-out values does not necessarily cause the execution of the MiniportTimer function exactly when the specified interval expires. The minimum practicable interval to specify on Windows NT platforms is ten milliseconds.
Callers of NdisMSetTimer run at IRQL <= DISPATCH_LEVEL.
MiniportInitialize, MiniportTimer, NdisMCancelTimer, NdisMInitializeTimer, NdisMSetPeriodicTimer