

High-performance asynchronous packet-based I/O to allow for the implementation of scalable applications. (See Chapter 6, “Security,” in Part 1 for a description of the Windows security model.) Uniform security and naming across devices to protect shareable resources. The design goals for the Windows I/O system are to provide an abstraction of devices, both hardware (physical) and software (virtual or logical), to applications with the following features: Finally, we’ll present the way device detection, driver installation, and power management work. We’ll look at the key data structures that describe devices, device drivers, and I/O requests, after which we’ll describe the steps necessary to complete I/O requests as they move through the system. Then we’ll examine the structure and components of the I/O system and the various types of device drivers. We’ll then cover the components that make up the I/O system, including the I/O manager, Plug and Play (PnP) manager, and power manager. In this chapter, we’ll first list the design goals of the I/O system, which have influenced its implementation.

The Windows I/O system consists of several executive components that together manage hardware devices and provide interfaces to hardware devices for applications and the system.
