This function acquires a spin lock so that the caller gains exclusive access to the resources, shared among driver functions, that the spin lock protects.
| Header file: | Ndis.h |
| Windows CE versions: | 2.0 and later |
VOID NdisAcquireSpinLock( IN PNDIS_SPIN_LOCK SpinLock );
In Windows CE, NDIS spin locks are implemented using critical sections.
The driver must initialize a variable of type NDIS_SPIN_LOCK with the NdisAllocateSpinLock function before it calls any other NDIS SpinLock function. The driver must provide resident storage for the spin lock( s ) it uses.
After acquiring a spin lock with this function, the caller releases that lock with a call to the NdisReleaseSpinLock function. A driver must call NdisReleaseSpinLock following each call to this function. Otherwise, a deadlock occurs, hanging the driver.
A spin lock acquired with the NdisDprAcquireSpinLock function must be released with the NdisDprReleaseSpinLock function.
A driver should never hold a spin lock for an extended period—more than a few instructions. Holding a spin lock for longer than 25 microseconds degrades both system and driver performance.
A miniport driver cannot use a spin lock to protect resources that its other functions share with the MiniportISR and/or the MiniportDisableInterrupt functions. Instead, a miniport must call the NdisMSynchronizeWithInterrupt function so that its MiniportSynchronizeISR function accesses such shared resources at the same DIRQL at which its MiniportISR and/or MiniportDisableInterrupt functions do.
A driver that calls this function runs at IRQL <=DISPATCH_LEVEL.
NdisDprAcquireSpinLock, NdisMSynchronizeWithInterrupt, NdisReleaseSpinLock