# US 2008/0307116 A1 · Routing Mechanism in PCI Multi-Host Topologies Using Destination ID Field

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0307116 A1
- Document ID: US20080307116A1
- Status: Published application
- Kind: A1
- Application number: 12/197,642
- Filed: 2008-08-25
- Published: 2008-12-11
- Earliest claimed: 2005-10-27
- Assignees: International Business Machines Corporation
- Inventors: William T. Boyd; Douglas M. Freimuth; William G. Holland; Steven W. Hunter; Renato J. Recio; Steven M. Thurber; Madeline Vega
- Web page: https://patentgrep.com/patent/US20080307116A1

## CPC

- G06F 13/4022: {using switching circuits, e.g. switching matrix, connection or expansion network (G06F13/4009 takes precedence)}
- H04L 2101/618: Details of network addresses
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Method and system for address routing in a distributed computing system, such as a distributed computing system that uses PCI Express protocol to communicate over an I/O fabric. A destination identifier is provided to identify a physical or virtual host or end point. When a physical or virtual host or end point receives a PCI data packet it compares a list of source identifiers with destination identifiers to determine if a source identifier included in the transaction packet is associated with a destination identifier included in the transaction packet to determine if the transaction packet has a valid association. If the transaction packet has a valid association, it is routed to the target device. The present invention enables each host that attaches to PCI bridges or switches and shares a set of common PCI devices to have its own PCI 64-bit address space and enables the routing of PCI transaction packets between multiple hosts and adapters, through a PCI switched-fabric bus using a destination identifier.

## Claims

### Claim at position 1

-10. (canceled)

### Claim 11

An address routing system in a distributed computing system for routing a transaction packet to a target device, comprising:
a transaction packet comprising at least a source identifier that identifies a source of a transaction by a bus value, a device value, and a function value, and a memory address that identifies a Peripheral Component Interconnect address to access in a target device;
a mechanism for determining if the transaction packet includes a destination identifier that identifies the target device to be accessed by the transaction packet, wherein a destination identifier is automatically inserted into a transaction packet by hardware on each Input/Output transaction;
responsive to a determination that the transaction packet includes a destination identifier, a mechanism for retrieving a record from a validation table using the destination identifier included in the transaction packet;
responsive to a determination that the transaction packet does not include a destination identifier, a mechanism for retrieving a destination identifier from a translation table using the memory address included in the transaction packet to lookup the destination identifier, for retrieving the record from the validation table using the destination identifier retrieved from the translation table, and for inserting the destination identifier retrieved from the translation table into the transaction packet;
a comparing mechanism for determining if the source identifier included in the transaction packet is associated with the destination identifier using the record from the validation table, wherein the validation table contains a record for each of a plurality of destination identifiers, and wherein the record for each of the plurality of destination identifiers indicates all associated source identifiers for one of the plurality of the destination identifiers;
responsive to a determination that the source identifier included in the transaction packet is associated with the destination identifier, a mechanism for retrieving at least one port that is associated with the destination identifier using at least one routing table to look up the at least one port, wherein a bridge or switch contains a routing table and one port of the at least one port, and wherein each port of the at least one port is used to reach the target device;
a mechanism for determining if the at least one port is destination identifier aware, wherein a port is destination identifier aware by supporting destination identifier routing;
responsive to a determination that the at least one port is destination identifier aware, a mechanism for placing the transaction packet in a queue for the at least port;
a routing mechanism for routing the transaction packet using the at least one port, wherein the transaction packet is routed to the target device through at least one bridge or switch of the at least one port, wherein the transaction packet is authorized to access the target device if the validation table indicates that the source identifier included in the transaction packet is associated with the destination identifier.

### Claim 12 (depends on 11)

The system according to claim 11, wherein the routing mechanism includes preventing access to the target device in response to a determination that the source identifier included in the transaction packet is not associated with the destination identifier.

### Claim 13

(canceled)

### Claim 14 (depends on 11)

The system according to claim 11, and further including:
removing the destination identifier from the transaction packet in response to a determination that the at least one port is not destination identifier aware.

### Claim 15 (depends on 11)

The system according to claim 11, and further including:
recalculating the ECRC data integrity check in response to a determination that the transaction packet includes a destination identifier.

### Claim 16 (depends on 11)

The system according to claim 11, wherein the target device comprises one of an Input/Output Adapter, a virtual Input/Output Adapter or a system image.

### Claim 17 (depends on 11)

The system according to claim 11, wherein the distributed computing system comprises a distributed computing system that uses Peripheral Component Interconnect Express protocol.

### Claim 18

A computer program product comprising:
a computer usable storage medium having encoded thereon computer usable program code executed on a computer for routing a transaction packet in a distributed computing system, the computer program product including:
computer usable program code configured for receiving a transaction packet comprising at least a source identifier that identifies a source of a transaction by a bus value, a device value, and a function value, and a memory address that identifies a Peripheral Component Interconnect address to access in a target device;
computer usable program code configured for determining if the transaction packet includes a destination identifier that identifies the target device to be accessed by the transaction packet, wherein a destination identifier is automatically inserted into a transaction packet by hardware on each Input/Output transaction;
responsive to a determination that the transaction packet includes a destination identifier, computer usable program code configured for retrieving a record from a validation table using the destination identifier included in the transaction packet;
responsive to a determination that the transaction packet does not include a destination identifier, computer usable program code configured for retrieving a destination identifier from a translation table using the memory address included in the transaction packet to lookup the destination identifier, retrieving the record from the validation table using the destination identifier retrieved from the translation table, and inserting the destination identifier retrieved from the translation table into the transaction packet;
computer usable program code configured for determining if the source identifier included in the transaction packet is associated with the destination identifier using the record from the validation table, wherein the validation table contains a record for each of a plurality of destination identifiers, and wherein the record for each of the plurality of destination identifiers indicates all associated source identifiers for one of the plurality of the destination identifiers;
responsive to a determination that the source identifier included in the transaction packet is associated with the destination identifier, computer usable program code configured for retrieving at least one port that is associated with the destination identifier using at least one routing table to look up the at least one port, wherein a bridge or switch contains a routing table and one port of the at least one port, and wherein each port of the at least one port is used to reach the target device;
computer usable program code configured for determining if the at least one port is destination identifier aware, wherein a port is destination identifier aware by supporting destination identifier routing;
responsive to a determination that the at least one port is destination identifier aware, computer usable program code configured for placing the transaction packet in a queue for the at least port;
computer usable program code configured for routing the transaction packet using the at least one port, wherein the transaction packet is routed to the target device through at least one bridge or switch of the at least one port, wherein the transaction packet is authorized to access the target device if the validation table indicates that the source identifier included in the transaction packet is associated with the destination identifier.

### Claim 19 (depends on 18)

The computer program product according to claim 18, wherein the computer program product further comprises:
computer usable program code configured for preventing access to the target device in response to a determination that the source identifier included in the transaction packet is not associated with the destination identifier.

### Claim 20 (depends on 18)

The computer program product according to claim 18, wherein the computer program product further comprises:
computer usable program code configured for removing the destination identifier from the transaction packet in response to a determination that the at least one port is not destination identifier aware.

### Claim 21 (depends on 18)

The computer program product according to claim 18, and further including: computer usable program code configured for recalculating the ECRC data integrity check in response to a determination that the transaction packet includes a destination identifier.
