System and method for routing I/O expansion requests and responses in a PCIE architecture

• US 8,745,292 B2
• Filed: 06/23/2010
• Issued: 06/03/2014
• Est. Priority Date: 06/23/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lais, Eric N., Craddock, David F., Gregg, Thomas A.
• Primary Examiner(s): Tsai, Henry
• Assistant Examiner(s): OBERLY, ERIC T
• Application Number:
  US12/821,245
• Publication Number:
  US 20110320653A1
• Time in Patent Office: 1,441 Days
• Field of Search: 710/65, 710/313, 710/315
• US Class Current: 710/65
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 13/387 for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• CPC Class Codes: G06F 13/4221 being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
• CPC Class Codes: G06F 2213/0026 PCI express

Abstract

A system for implementing non-standard input/output (I/O) adapters in a standardized I/O architecture, comprising an I/O hub communicatively coupled to an I/O bus and a plurality of I/O adapters at I/O adapter addresses, the I/O hub including logic for implementing a method comprising receiving requests from the plurality of I/O adapters, storing the I/O adapter addresses of a requester along with their corresponding target recipient addresses and operation codes, receiving a response from a responder, the response indicating that a request has been completed, determining that the response is in a format other than a format supported by the I/O bus, transforming the response into the format supported by the I/O bus, locating a stored I/O adapter address having a corresponding target recipient address that matches the responder address and a corresponding operation code that matches the responder operation code, and transmitting the response to the stored I/O adapter address.

Claims

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

an I/O hub communicatively coupled to an I/O bus and a plurality of I/O adapters at I/O adapter addresses, the I/O hub including logic for implementing a method comprising;

receiving a request from the plurality of I/O adapters, the request comprising a peripheral component interconnect (PCI) format and including an address of a target recipient and an operation code;

storing the I/O adapter addresses of a requester along with their corresponding target recipient addresses and operation codes;

transmitting the requests to the target recipients in a non-PCIe format;

receiving a response from a responder at a responder address, the response in a non-PCIe format and indicating that a request has been completed, the response comprising an address of a target recipient and a responder operation code;

transforming the response into a PCIe format;

locating a stored I/O adapter address having a corresponding target recipient address that matches the responder address and a corresponding operation code that matches the responder operation code;

transmitting the transformed response to the stored I/O adapter address;

determining that the request comprises 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,

wherein the transformed response comprises the operation code.

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 is 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 transformed request is in a format not supported by the I/O adapter and the requester.

6. The system of claim 1, further comprising:

transforming the response into a PCIe write request in response to determining that the response is not supported on the I/O bus; and

transmitting, via the I/O bus, the PCIe write request, the PCIe write request indicating that the request has been completed within a header of the PCIe write request.

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

receiving a request at an I/O hub from a plurality of I/O adapters, the request comprising a peripheral component interconnect (PCI) format and including an address of a target recipient and an operation code;

storing the I/O adapter addresses of a requester along with their corresponding target recipient addresses and operation codes;

transmitting the request to the target recipients in a non-PCIe format;

receiving a response from a responder at a responder address, the response in a non-PCIe format and indicating that a request has been completed, the response comprising an address of a target recipient and a responder operation code;

transforming the response into a PCIe format;

locating a stored I/O adapter address having a corresponding target recipient address that matches the responder address and a corresponding operation code that matches the responder operation code;

transmitting the transformed response to the stored I/O adapter address;

determining that the request comprises 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,

wherein the transformed response comprises the operation code.

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 is 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 transformed request is in a format not supported by the I/O adapter and the requester.

12. The method of claim 7, further comprising:

transforming the response into a PCIe write request in response to determining that the response is not supported on the I/O bus; and

transmitting, via the I/O bus, the PCIe write request, the PCIe write request indicating that the request has been completed within a header of the PCIe write request.

19. The method of claim 7, wherein the I/O adapter addresses of the requester along with their corresponding target recipient addresses and operation codes are stored in a DMA completion table, and wherein the operation code included in the transformed response enables an I/O adapter associated with the stored I/O adapter address to process the transformed response.

20. The method of claim 7, further comprising:

storing the I/O adapter addresses in a response address table (RAT) based on applying select logic to a header of the request;

extracting, by a multiplexor, a requester ID field from the header;

using the requester ID field to determine an address and partition on a host system; and

sending the request to the host system based on the determined address and partition on the host system,

wherein the partition indicates an area of system memory of the host system.

13. A computer program product comprising a non-transitory storage medium storing instructions, which when executed by a computer implement non-standard input/output (I/O) adapters in a standardized I/O architecture, the computer program product implementing a method, the method comprising:

receiving a request at an I/O hub from a plurality of I/O adapters, the request comprising a peripheral component interconnect (PCI) format and including an address of a target recipient and an operation code;

storing the I/O adapter addresses of a requester along with their corresponding target recipient addresses and operation codes;

transmitting the request to the target recipients in a non-PCIe format;

receiving a response from a responder at a responder address, the response in a non-PCIe format and indicating that a request has been completed, the response comprising an address of a target recipient and a responder operation code;

transforming the response into a PCIe format;

locating a stored I/O adapter address having a corresponding target recipient address that matches the responder address and a corresponding operation code that matches the responder operation code;

transmitting the transformed response to the stored I/O adapter address;

determining that the request comprises 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,

wherein the transformed response comprises the operation code.

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

15. The computer program product of claim 13, wherein the format of the request is an I/O expansion format.

16. The computer program product of claim 13, wherein the at least one I/O adapter comprises at least one I/O expansion adapter and at least one PCIe adapter.

17. The computer program product of claim 13, wherein the transformed request is in a format not supported by the I/O adapter and the requester.

18. The computer program product of claim 13, further comprising:

transforming the response into a PCIe write request in response to determining that the response is not supported on the I/O bus; and

transmitting, via the I/O bus, the PCIe write request, the PCIe write request indicating that the request has been completed within a header of the PCIe write request.