NdisInitializeReadWriteLock (Compact 2013)

3/26/2014

This function initializes a read or write lock variable of type NDIS_RW_LOCK.


VOID NdisInitializeReadWriteLock(
  PNDIS_RW_LOCK Lock
);

Lock

[in] Points to an opaque variable that represents a lock. The caller can use this lock to gain write or read access to resources that are shared among non-ISR driver threads.

An NDIS_RW_LOCK variable is used to limit write access to shared resources to one non-ISR driver thread at a time. This NDIS_RW_LOCK can allow multiple non-ISR driver threads concurrent read access to those resources. Such read access is not permitted during a write access.

The Lock pointer that is passed to NdisInitializeReadWriteLock is a required parameter for all other Ndis..ReadWriteLock functions.

Before a driver calls the NdisAcquireReadWriteLock function to obtain write or read access to a resource, the driver must call NdisInitializeReadWriteLock to initialize the lock that is associated with that resource. The caller must provide nonpaged storage for the variable at Lock.

After calling NdisInitializeReadWriteLock, the driver can call NdisAcquireReadWriteLock to obtain either write or read access to the resource. Only one non-ISR driver thread at a time can obtain write access to the resource. When one non-ISR thread has write access, all read and write accesses by other non-ISR threads must wait until the write-access holder releases the lock. However, if a non-ISR thread has read access, other non-ISR threads can concurrently acquire read access.

Initialize and use this type of lock for resources that are frequently accessed for reading and infrequently accessed for writing.

As soon as resource access is complete, the driver calls the NdisReleaseReadWriteLock function.

Each lock that a driver initializes does one of the following:

  • protects a discrete set of shared resources from concurrent write and read access by driver threads that run at IRQL <= DISPATCH_LEVEL.
  • exposes a discrete set of shared resources to concurrent read access by driver threads that run at IRQL <= DISPATCH_LEVEL

Callers of NdisInitializeReadWriteLock can run at any IRQL. Usually a caller is running at IRQL = PASSIVE_LEVEL during initialization.

Header

ndis.h

Library

ndis.lib

Show: