Abstract: A processor-based system (200) with a multipath I/O architecture, including a virtual host controller interface (vHCI) layer (280) between a common architecture layer (270) and a physical host controller interface layer (290), which may include convential host bus adapters (HBAs) coupled to target decives such as storage devices (240, 250) in a storage area network (SAN). Target drivers send I/O requests to a common architecture layer, which forwards them to the vHCI layer (280), which then sends them to HBAs for sending to the target devices (240, 250). A multipathing driver interface (MPXIO) layer (310) resides beneath the vHCI layer (280), and determines target device path information for the vHCI layer (280). Positioning the MPXIO layer (310) beneath the vHCI layer avoids the need for multipathing target drivers (360) above the common architecture layer.

Abstract: A processor-based system (200) with a multipath I/O architecture, including a virtual host controller interface (vHCI) layer (280) between a common architecture layer (270) and a physical host controller interface layer (290), which may include convential host bus adapters (HBAs) coupled to target decives such as storage devices (240, 250) in a storage area network (SAN). Target drivers send I/O requests to a common architecture layer, which forwards them to the vHCI layer (280), which then sends them to HBAs for sending to the target devices (240, 250). A multipathing driver interface (MPXIO) layer (310) resides beneath the vHCI layer (280), and determines target device path information for the vHCI layer (280). Positioning the MPXIO layer (310) beneath the vHCI layer avoids the need for multipathing target drivers (360) above the common architecture layer.

Abstract: One embodiment of the present invention provides a system that uses a file system operation to drive the process of configuring a computer system to operate with a device. During operation, the system receives an access request for the device. If a driver for the device has not been previously loaded, the system loads the driver for the device. Next, the system creates an instance of the driver for the device and attaches the instance so that the computer system is able to access the device. Finally, the system accesses the device to satisfy the request. In a variation of this embodiment, the access request specifies a path for the device, wherein the path includes one or more path components. Before loading the driver, the system first parses the path to identify the driver for the device as well as an address for the device from a path component. The system uses this address to identify the device prior to creating the instance of the driver for the device.