Non-standard I/O adapters in a standardized I/O architecture

• US 8,615,622 B2
• Filed: 06/23/2010
• Issued: 12/24/2013
• Est. Priority Date: 06/23/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gregg, Thomas A., Bayer, Gerd K., Craddock, David F., Jung, Michael, Lais, Eric N., Nass, Elke G.
• Primary Examiner(s): PHAN, RAYMOND NGAN
• Application Number:
  US12/821,242
• Publication Number:
  US 20110320675A1
• Time in Patent Office: 1,280 Days
• Field of Search: 710300-317, 710 8- 19, 710 1- 2, 710 62- 64
• US Class Current: 710/315
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• CPC Class Codes: G06F 13/404 with address mapping
• CPC Class Codes: G06F 2213/0026 PCI express

Abstract

A system for implementing non-standard I/O adapters in a standardized I/O architecture, the system comprising an I/O hub communicatively coupled to an I/O bus and at least one I/O adapter, the I/O hub including logic for implementing a method, the method comprising receiving a request to perform an operation on the I/O adapter from a requester at a requester address, the I/O adapter at a destination address, determining that the request is in a format other than a format supported by the I/O bus, the I/O bus expecting a requester identifier at a first location in a header of the request, reformatting the request into the format supported by the I/O bus, the reformatting comprising storing the requester address, the destination address and an operation code at the first location in the header of the reformatted request, and sending the reformatted request to the I/O adapter.

Claims

1. A system for implementing non-standard I/O adapters in a standardized I/O architecture, the system comprising:

an I/O hub communicatively coupled to an I/O bus and at least one I/O adapter, the I/O hub including logic for implementing a method, the method comprising;

receiving a request to perform an operation on the I/O adapter from a requester at a requester address, the I/O adapter at a destination address;

determining that the request is in a non-peripheral component interconnect (PCI) format, the I/O bus expecting a PCI formatted request with a requester identifier at a first location in a header of the request;

reformatting the request into the PCI format supported by the I/O bus, the reformatting comprising storing the requester address, the destination address and an operation code at the first location in the header of the PCI formatted request; and

sending the PCI formatted request to the I/O adapter.

2. The system of claim 1, wherein the I/O bus is a PCIe bus.

3. The system of claim 1, wherein the format of the request an I/O expansion format.

4. The system of claim 1, wherein the at least one I/O adapter comprises at least one I/O expansion adapter and at least one PCIe adapter.

5. The system of claim 1, wherein the PCI formatted request is in a format not supported by the I/O adapter and the requester.

6. The system of claim 1, further comprising:

determining that the request is a request to store data; and

storing information about the requester in the I/O hub in response to the determining, the information comprising;

the requester address; and

the operation code, the operation code identifying the operation that is to be performed.

7. A method for implementing non-standard I/O adapters in a standardized I/O architecture, the method comprising:

receiving at an I/O hub a request to perform an operation on an I/O adapter from a requester at a requester address, the I/O adapter at a destination address;

determining that the request is in a non-peripheral component interconnect (PCI) format, the I/O bus expecting a PCI formatted request with a requester identifier at a first location in a header of the request;

reformatting the request into the PCI format supported by the I/O bus, the reformatting comprising storing the requester address, the destination address and an operation code at the first location in the header of the PCI formatted request; and

sending the PCI formatted request to the I/O adapter.

8. The method of claim 7, wherein the I/O bus is a PCIe bus.

9. The method of claim 7, wherein the format of the request an I/O expansion format.

10. The method of claim 7, wherein the at least one I/O adapter comprises at least one I/O expansion adapter and at least one PCIe adapter.

11. The method of claim 7, wherein the PCI formatted request is in a format not supported by the I/O adapter and the requester.

12. The method of claim 7, further comprising:

determining that the request is a request to store data; and

storing information about the requester in the I/O hub in response to the determining, the information comprising;

the requester address; and

the operation code, the operation code identifying the operation that is to be performed.

13. A system for implementing non-standard I/O adapters in a standardized I/O architecture, the system comprising:

an I/O adapter communicatively coupled to an I/O bus; and

an I/O hub communicatively coupled to the I/O bus, the I/O hub including logic for implementing a method, the method comprising;

receiving a response, the response generated by a responder to indicate a completion of a request, the responder at an address, and the request initiated by the I/O adapter;

determining that the response is in a non-peripheral component interconnect (PCI) format, the I/O bus expecting a PCI formatted request with a completer identifier at a first location in a header of the response;

reformatting the response into the PCI format supported by the I/O bus, the reformatting comprising storing an identifier of the address of the responder, and a response code at the first location in the header of the PCI formatted response;

sending the reformatted response to the I/O adapter; and

receiving the PCI formatted response at the I/O adapter.

14. The system of claim 13, wherein the I/O bus is a PCIe bus.

15. The system of claim 13, wherein the format of the response is an I/O expansion format.

16. The system of claim 13, wherein the I/O adapter comprises an I/O expansion adapter, the I/O expansion adapter sharing the I/O bus with at least one PCIe adapter.

17. The system of claim 13, wherein the PCI formatted response is in a format not supported by the I/O adapter and the responder.

18. The system of claim 13, further comprising:

determining that the request is a request to store data; and

updating information about the request in the I/O hub in response to the determining, the information comprising flagging that the request has been completed.

19. A method for implementing non-standard I/O adapters in a standardized I/O architecture, the method comprising:

receiving a response at an I/O adapter, the response generated by a responder to indicate a completion of a request, the responder at an address, and the request initiated by the I/O adapter;

determining that the response is in a non-peripheral component interconnect (PCI) format, the I/O bus expecting a PCI formatted request with a completer identifier at a first location in a header of the response;

reformatting the response into the PCI format supported by the I/O bus, the reformatting comprising storing an identifier of the address of the responder, and a response code at the first location in the header of the PCI formatted response;

sending the PCI formatted response to the I/O adapter; and

receiving the PCI formatted response at the I/O adapter.

20. The method of claim 19, wherein the I/O bus is a PCIe bus.

21. The method of claim 19, wherein the format of the response is an I/O expansion format.

22. The method of claim 19, wherein the I/O adapter comprises an I/O expansion adapter, the I/O expansion adapter sharing the I/O bus with at least one PCIe adapter.

23. The method of claim 19, wherein the PCI formatted response is in a format not supported by the I/O adapter and the responder.

24. The method of claim 19, further comprising:

determining that the request is a request to store data; and

updating information about the request in the I/O hub in response to the determining, the information comprising flagging that the request has been completed.