Microsoft Technology Licensing, LLC

Nar Ganapathy

Mingtzong Lee

Mukund Sankaranarayan

Mitesh K Desai

Henrique Filgueiras

Mahmoud S Elhaddad

Martin Abadi

Peter W Wieland

John Joseph Richardson

Ulfar Erlingsson

Yesayi Hovnanyan

Ulfar Erlingson

Mahmoud Elhaddad

Technology for managing operational modes of a network adapter is disclosed. The technology includes features for selectively preempting (e.g., canceling, suspending, deferring, pausing, changing to a 'no-op' state, changing to a passive state, or otherwise deprioritizing) execution for a current operational mode of the network adapter, executing a requested network control operation, and optionally restoring the preempted operational mode. The operational mode may be selectively preempted based on priority information associated with the current operational mode and the requested network control operation.

Network mode conflict resolution

Technology for managing queuing resources of a shared network adapter is disclosed. The technology includes selectively transferring data from data transmission sources to a queue of the shared network adapter based on status indications from the shared network adapter regarding availability of queuing resources at the shared network adapter. In addition, the technology also includes features for selectively controlling transfer rates of data to the shared network adapter from applications, virtual network stations, other virtual adapters, or other data transmission sources. As one example, this selective control is based on how efficiently data from these data transmission sources are transmitted from the shared network adapter.

Management of multilevel queues for shared network adapters

A device driver includes a kernel mode and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. The device driver may include kernel stubs that are loaded into the operating system, and may be device specific code written. The stubs may be called by a reflector to handle exceptions caught by the stubs. A reset stub may be invoked by the reflector when the user-mode module or host terminates abruptly or detects an interrupt storm. The reset stub may also be invoked if errant direct memory access DMA operations are being performed by a hardware device. The reset stub may ensure that hardware immediately stops unfinished DMA from further transfer, and may be called by the user-mode driver module.

Synchronizing split user-mode/kernel-mode device driver architecture

A device driver includes a kernel stub and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the kernel stub may run an interrupt service routine and write information to shared memory. Control is passed to the user-mode module by a reflector. The user-mode module may then read the information from the shared memory to continue servicing the interrupt.

Split user-mode/kernel-mode device driver architecture

Growing community of inventors

Redmond, WA, United States of America

Nar Ganapathy