Bus bridge device

• US 7,415,555 B2
• Filed: 07/21/2005
• Issued: 08/19/2008
• Est. Priority Date: 03/31/2003
• Status: Expired due to Fees

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Arataki, Nina
• Primary Examiner(s): Dang; Khanh
• Application Number:
  US11/185,853
• Publication Number:
  US 20050256998A1
• Time in Patent Office: 1,125 Days
• Field of Search: 710/300, 710/110, 710/305, 710/306, 710/310, 710/311, 710313-315, 710/260, 710266-269
• US Class Current: 710/110
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence

Abstract

A bus bridge device, which connects a first device executing a first process and a second device executing a second process in response to a request from the first device, includes a notifying unit that notifies, when a result of the second process is received from the second device, the result to the first device. The first device executes, after sending the request, a third process until the result is notified from the notifying unit.

Claims

1. A bus bridge device, connecting a first bus end a second bus, that transmits a processing request sent by a first device connected to the first bus to a second device connected to the second bus, the bus bridge device comprising a notifying unit that has a busy mode in which the notifying unit notifies, when the first device asks the results of the processing request and the result is not received from the second device, a busy message to the first device, releasing the first device to execute other processes, instead of a retry message notified in a retry mode asking the first device to retry.

2. The bus bridge device according to claim 1, wherein the notifying unit has a reply mode in which the notifying unit notifies the result of the processing request to the first device without being requested by the first device, when the result of the processing request is received from the second device.

3. The bus bridge device according to claim 2, wherein the notifying unit notifies the result to the first device by writing the result in a predetermined memory area of the first device.

4. The bus bridge device according to claim 1, wherein

the notifying unit has a interrupt mode in which the notifying unit notifies the result of the processing request to the first device by generating an interrupt to the first device without being requested by the first device, when the result of the processing request is received from the second device.

5. The bus bridge device according to claim 1, wherein the first bus and the second bus are peripheral-component-interconnect bus.

6. The bus bridge device according to claim 5, wherein the first device is a storage controller that controls a storage system,

the second device is a cache controller that provides a fast access to the storage system, and

the request is a write-data request from the storage controller to the cache controller.

7. A method for controlling a bus bridge device, connecting a first bus and a second bus, that transmits a processing request sent by a first device connected to the first bus to a second device connected to the second bus, the method comprising notifying, when the first device asks the results of the processing request and the result is not received from the second device, a busy message in a busy mode to the first device, releasing the first device to execute other processes, instead of a retry message notified in a retry mode asking the first device to retry.

8. The method according to claim 7, wherein the notifying includes notifying the result of the processing request in a reply mode to the first device without being requested by the first device, when the result of the processing request is received from the second device.

9. The method according to claim 8, wherein the notifying includes notifying the result to the first device by writing the result in a predetermined memory area of the first device.

10. The method according to claim 7, wherein the notifying includes notifying the result of the processing request in a interrupt mode to the first device by generating an interrupt to the first device without being requested by the first device, when the result of the processing request is received from the second device.