| US 7,552,355 B2 | ||
| System for providing an alternative communication path in a SAS cluster | ||
| Parag Maharana, Fremont, Calif. (US); and Basavaraj Hallyal, Fremont, Calif. (US) | ||
| Assigned to LSI Logic Corporation, Milpitas, Calif. (US) | ||
| Filed on Feb. 24, 2005, as Appl. No. 11/64,684. | ||
| Prior Publication US 2006/0190764 A1, Aug. 24, 2006 | ||
| Int. Cl. G06F 11/00 (2006.01); G06F 11/20 (2006.01) | ||
| U.S. Cl. 714—4 [714/43; 714/736] | 7 Claims |
| 1. A system for providing a peer to peer communication for a SAS cluster wherein the SAS cluster includes a first node, a
second node and at least one SAS enclosure serially connected to the first and second nodes, comprising:
a first firmware detecting an asynchronous event occurrence;
a first driver communicatively coupled to the first firmware, the first driver receiving an asynchronous event notification
from the first firmware;
a first application communicatively coupled to the first driver, querying details of the asynchronous event occurrence, including
the details of the asynchronous event occurrence into an event notification message, and sending the event notification message
through an alternative path when the first driver signals the asynchronous event occurrence to the first application,
wherein the alternative path has been established between the first application and a second application, the second application
suitable for communicating with the first application through the alternative path, wherein the second application receives
the event notification message including the details of the asynchronous event occurrence in the first node;
a second firmware suitable for communicating with the first firmware through the at least one SAS enclosure; and
a second driver communicatively coupled to the second application, the second driver passing a command from the second application
to the second firmware, the command being based on the event notification message which has been sent from the first application
to the second application,
wherein the first node includes the first application, the first driver and the first firmware and the second node includes
the second application, the second driver, and the second firmware, the second firmware sends an acknowledgement to the second
application via the second driver after completing the command, the second application sends an ACK notification to the first
application via the alternative path upon reception of the acknowledgement from the second firmware.
|