TUNNELED WINDOW CONNECTION FOR PROGRAMMED INPUT OUTPUT TRANSFERS OVER A SWITCH FABRIC
Tunneled window connections are utilized in a switch fabric to perform programmed input output transfers. The window connections are based on global IDs. A management entity may enforce the tunneled window connections, improving security.
1 . A method of performing a programmed input output (PIO) transfer in a switch fabric, comprising:
defining visibility of at least one host end point to other host end points of a switch or switch fabric, including defining windows on these host end points and connections between them; and
tunneling PIO transfers between connected windows by routing PIO transfer between window segments of host end points based on a global ID.
2 . The method of claim 1 , wherein the routing includes performing a lookup to at least one table defined by the management entity to access stored connection information and apply it to the routing of a packet between two host end points
3 . The method of claim 1 , further comprising creating a connection between an application on a management CPU and a remote host node, receiving a request from an application running on the MCPU for a load store operation with a remote host node, and routing the transaction through the fabric using a address based routing that targets the TWC-H endpoint of the remote node.
4 . The method of claim 1 , wherein the PIO transfer is between two host end points, the method further comprising:
receiving a request from an application at an initiating node to create a connection to a remote node;
receiving a request from the application for a load/store operation with the remote node; and
routing the transaction using a global ID.
5 . The method of claim 1 , further comprising pre-pending an original packet with an ID routing prefix.
6 . The method of claim 1 , further comprising extracting a connection number from an address and performing a lookup of a target global ID and connection number in a lookup up table.
7 . The method of claim 6 , further comprising modifying the packet for transfer through packet by pre-pending or converting the packet to include the global ID.
8 . The method of claim 1 , further comprising extracting connection information at the target node.
9 . The method of claim 8 , further comprising utilizing an indexed table access, based on the extracted connection information, in order to process the tunneled load/store transfer request at the target node
10 . The method of claim 1 , wherein a management end point utilizes a segmented base address register and a segment mapping table to direct incoming traffic to a host end point.
11 . The method of claim 10 , wherein a host end point includes a segmented base address register to point to windows of other remote nodes.
12 . A method of performing a programmed input output (PIO) transfer in a PLX Express Fabric, comprising:
defining, by a management entity, tables in a global management end point of a switch and in host end points of the switch, the tables defining mappings between window segments of the initiating node and windows of the target node for routing transactions based on a global ID; and
performing a transaction between two end points of the switch fabric by routing the transaction based on a global ID.
13 . The method of claim 12 , wherein the management entity programs Ingress Tunnel Lookup Tables and Egress Tunnel Lookup Tables in host end points.
14 . The method of claim 13 , wherein a segment mapping table of the global management end point directs incoming traffic to Egress Lookup Table of a host end point.
15 . The method of claim 13 , wherein an Ingress Tunnel Lookup Table contains remote host Egress Lookup Table Entry indices to direct traffic at remote nodes.
16 . A PLX Express Fabric Switch, comprising:
a port for connection to a management entity or an internal management entity;
a global end point having a segmented base address register and a segment mapping table; and
a set of host end points communicatively coupled to the global end point manager, each host end point having ingress and egress lookup tables;
wherein the segment mapping table and the ingress and egress lookup tables are programmed to define window connections between end points for programmed input output transactions.
17 . The switch of claim 16 , wherein the segment mapping table and the ingress and egress lookup tables are programmed by a management entity.
18 . The switch of claim 16 , wherein the segment mapping table and the ingress and egress lookup table are programmed as data structures by serial EEPROM.
19 . The switch of claim 17 , wherein the hardware of the switch routes a transaction between a pair of connected windows based on a global ID.
20 . The switch of claim 17 , wherein the window connection is defined between two host end points to tunnel transactions between the host end points.
21 . The switch of claim 17 , where the window connection is defined between the global end point manager and an individual host end point.
22 . The method of claim 1 , wherein the switch fabric is a PCI Express Fabric.