Scalable routing and addressing
First Claim
1. A method of routing transactions via a shared infrastructure, the method comprising:
- at a first infrastructure point, generating an additional header comprising at least a source identifier and a target identifier for a transaction packet that comprises a header portion, a data portion and an end-to-end CRC portion;
routing the transaction packet with the additional header from the ingress point to a second point; and
at the second point, removing the additional header.
2 Assignments
0 Petitions
Accused Products
Abstract
PCI Express transactions can be transmitted via a shared PCI Express infrastructure. At an infrastructure ingress point an additional header comprising at least a source identifier and a target identifier is generated for a transaction packet that comprises a header portion, a data portion and an end-to-end CRC portion. The transaction packet is then transmitted with the additional header from the ingress point to an egress point. At the egress point the additional header is removed. The additional header can further include a resource key. It can further include protection information such as a CRC.
188 Citations
21 Claims
-
1. A method of routing transactions via a shared infrastructure, the method comprising:
-
at a first infrastructure point, generating an additional header comprising at least a source identifier and a target identifier for a transaction packet that comprises a header portion, a data portion and an end-to-end CRC portion;
routing the transaction packet with the additional header from the ingress point to a second point; and
at the second point, removing the additional header. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
- 14. An interconnect apparatus for a shared infrastructure, the interconnect apparatus comprising an additional header generator, the additional header generator being operable to receive a transaction packet including a header portion, a data portion and an end-to-end CRC portion, the additional header generator being further operable to generate an additional header for the transaction packet, which additional header comprises at least a source identifier and a target identifier.
-
21. A computer system comprising, at an infrastructure ingress point, an additional header generator, the additional header generator being operable to receive a transaction packet including a header portion, a data portion and an end-to-end CRC portion, the additional header generator being further operable to generate an additional header for the transaction packet, which additional header comprises at least a source identifier and a target identifier.
Specification