 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
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.
VOID NdisAcquireSpinLock( IN PNDIS_SPIN_LOCK SpinLock );
Parameters
- SpinLock
- Pointer to an opaque spin lock, already initialized by the
caller.
Remarks
For Windows CE, note the following:
- NDIS spin locks are implemented using critical sections.
- A single miniport lock exists for a miniport that is held when
any of the
Miniport
XXXfunctions runs, except for
MiniportInitializeand
MiniportHalt. Typically, it
is not necessary to have separate driver created locks. In
particular, the
MiniportISRhandler is run
with the miniport lock held, so the use of
NdisMSynchronizeWithInterruptis unnecessary.
The driver must initialize a variable of type NDIS_SPIN_LOCK with the NdisAllocateSpinLockfunction before it calls any other NDIS SpinLockfunction. 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 NdisReleaseSpinLockfunction. A driver must call NdisReleaseSpinLockfollowing each call to this function. Otherwise, a deadlock occurs, causing the driver to stop responding.
A spin lock acquired with the NdisDprAcquireSpinLockfunction must be released with the NdisDprReleaseSpinLockfunction.
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.
Requirements
Runs on Versions Defined in Include Link to Windows CE OS 2.0 and later Ndis.h Ndislib.lib Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
See Also
MiniportHalt, MiniportInitialize, MiniportISR, NdisAllocateSpinLock, NdisDprAcquireSpinLock, NdisDprReleaseSpinLock, NdisMSynchronizeWithInterrupt, NdisReleaseSpinLock