Abstract: A protocol bridge includes a cache for caching data from a plurality of data storage devices, and for servicing data requests from a plurality of initiators. Data is cached for every data access operation such that the most frequently accessed data remains replicated in the cache.

Abstract: A SAS expander or initiator places PHYs in a wide port into a persistent reduced power state by signaling to the connected SAS device that the SAS expander or initiator intends to route data traffic through other PHYs in the wide port. The SAS expander or initiator and connected SAS device agree to disuse certain PHYs so that the PHYs enter a reduced power state according to SAS standards.

Abstract: A protocol bridge includes a cache for caching data from a plurality of data storage devices, and for servicing data requests from a plurality of initiators. Data is cached for every data access operation such that the most frequently accessed data remains replicated in the cache.

Abstract: A SAS expander or initiator places PHYs in a wide port into a persistent reduced power state by signaling to the connected SAS device that the SAS expander or initiator intends to route data traffic through other PHYs in the wide port. The SAS expander or initiator and connected SAS device agree to disuse certain PHYs so that the PHYs enter a reduced power state according to SAS standards.

Abstract: A data-processing system and method are disclosed, which generally includes a plurality of components connected to a bus within a data-processing apparatus utilizing one or more input/output interfaces (e.g., IOCTL) in communication with the bus. A dynamic interface is implemented, which includes a plurality of interface modules that permits varying data-processing applications to scan, identify and interface with the plurality of components utilizing the input/output interface, thereby increasing data-processing application development efficiency relative to one or more components within the data-processing system.

Abstract: A data-processing apparatus, method and program product generally include identifying one or more SAS expanders and one or more link thereof associated with an SAS domain of a data-processing apparatus. Link and reset data can be automatically injected onto the link(s) and the SAS expander(s) associated with the SAS domain, in response to identifying the SAS expander(s) and one or more links thereof. The presence of the link(s) within the SAS domain can then be verified, in response to automatically injecting the link and reset data onto one or more links and one or more SAS expanders in order to test the links and the SAS expanders associated with the SAS domain.

Abstract: A data-processing apparatus, method and program product generally includes a graphical user interface, which is provided to generate a simulation of one or more target devices based one or more user inputs to the graphical user interface. The simulation of the target device(s) can be automatically generated device based on the particular user input(s) to the graphical user interface. A topology of the target device(s) can then be compiled based on the simulation of the target device(s). Such a topology is utilized for testing of the target device(s). The simulation of the device(s) can also be utilized to modify the target device(s) on a per-device basis. A script of errors is also compiled for injection into the target device(s) for testing of the target device(s). The target device can be, for example, an SAS device, an SMP device and/or an SATA device.

Abstract: A data-processing apparatus, method and program product generally include identifying one or more SAS expanders and one or more link thereof associated with an SAS domain of a data-processing apparatus. Link and reset data can be automatically injected onto the link(s) and the SAS expander(s) associated with the SAS domain, in response to identifying the SAS expander(s) and one or more links thereof. The presence of the link(s) within the SAS domain can then be verified, in response to automatically injecting the link and reset data onto one or more links and one or more SAS expanders in order to test the links and the SAS expanders associated with the SAS domain.

Abstract: A data-processing system and method are disclosed, which generally includes a plurality of components connected to a bus within a data-processing apparatus utilizing one or more input/output interfaces (e.g., IOCTL) in communication with the bus. A dynamic interface is implemented, which includes a plurality of interface modules that permits varying data-processing applications to scan, identify and interface with the plurality of components utilizing the input/output interface, thereby increasing data-processing application development efficiency relative to one or more components within the data-processing system.

Abstract: Disclosed is a SCSI target device simulator consisting of a personal computer, a SCSI host adapter board, and simulator software. The SCSI target device simulator is employed to test SCSI host adapter systems by simulating multiple SCSI target devices for test purposes. The simulated SCSI target devices may be configured to imitate a wide variety of different SCSI target device types, with an equally wide variety of configuration settings within a single SCSI target device type. A user may quickly create and change simulated SCSI target devices for a test system. The SCSI target device simulator may also be configured so that the simulated SCSI target devices respond in a specified manner to SCSI commands and SCSI task management commands. Controlling the simulated SCSI target device responses to SCSI commands and SCSI task management commands allows a user to easily configure and test a SCSI host adapter device for specific operational scenarios.

Abstract: An operating system's input/output control (IOCTL) interface can communicate with one or more device drivers, which may be implemented as Message Passing Technology (MPT) based drivers. At start-up and at user-defined intervals, Message Passing Interface (MPI) pass-through messages can be sent utilizing the IOCTL interface. Such messages can be formatted as Configuration Page Request messages, and can then return data that includes the current negotiated rates and widths for all devices connected via the bus. Whenever a drop in rate occurs for any device connected to the bus, the event will be logged, and the user informed. Utilizing such technology, device transfer rates can be automatically tracked performance degradation thereof reported.