Edit

Pausing a Binding

  • Article

After NDIS sends a protocol driver a network Plug and Play (PnP) pause event notification for a binding, the binding enters the Pausing state.

To notify the protocol driver of the PnP pause event, NDIS calls the ProtocolNetPnPEvent function with the NetEvent member of the NET_PNP_EVENT_NOTIFICATION structure is set to NetEventPause. The Buffer member contains an NDIS_PROTOCOL_PAUSE_PARAMETERS structure.

For a binding in the Pausing state, the protocol driver:

  • Should not initiate any new send requests.

  • Must wait for outstanding send requests to complete. The pause operation is not complete until NDIS calls the ProtocolSendNetBufferListsComplete function for all of the driver's outstanding send requests.

  • Should handle receive indications as usual. The underlying miniport driver waits for outstanding receive data to return before completing a pause operation. This ensures that there are no ongoing receive operations in the driver stack after the miniport driver is paused.

  • Should return new receive indications to NDIS immediately. If necessary, the driver can copy such receive indications before it returns them.

For more information about protocol driver send and receive operations, see Protocol Driver Send and Receive Operations.

A binding enters the Paused state after the protocol driver is done returning outstanding receive indications for the binding and NDIS has completed all of the outstanding send requests for the binding.

For a binding in the Paused state, the protocol driver:

  • Must not make any send requests.

  • Should return receive indications immediately. If necessary, the driver can copy such receive indications before it returns them.