| UID | title | description | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.lib | req.dll | req.irql | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | targetos | f1_keywords | topic_type | api_type | api_location | api_name | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:ndis.NDIS_INIT_MUTEX |
NDIS_INIT_MUTEX macro (ndis.h) |
The NDIS_INIT_MUTEX macro initializes a mutex object and sets it to a signaled state. |
netvista |
04/16/2018 |
|
NDIS_INIT_MUTEX |
ndis.h |
Universal |
Supported in NDIS 6.0 and later. |
Any level |
Windows |
|
|
|
|
|
The NDIS_INIT_MUTEX macro initializes a mutex object and sets it to a signaled state.
A pointer to a caller-supplied NDIS_MUTEX-type mutex object. NDIS_MUTEX is a wrapper for KMUTEX.
NDIS network drivers should use the NDIS_INIT_MUTEX macro to initialize a mutex.
The initial state of the mutex object is the signaled state. To acquire the mutex, call the NDIS_WAIT_FOR_MUTEX macro. To release the mutex, call the NDIS_RELEASE_MUTEX macro.
A driver cannot wait for a nonzero time interval on a mutex object at a raised IRQL or in an arbitrary thread context (that is, the context of whatever thread is current when a driver function is called).
Storage for a mutex object must reside in a driver context area or in a nonpaged pool that the caller allocated.
The NDIS_INIT_MUTEX macro is an NDIS wrapper for the KeInitializeMutex routine.