System for addressing network end-points using route handles

• US 20050243816A1
• Filed: 04/30/2004
• Published: 11/03/2005
• Est. Priority Date: 04/30/2004
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Gardner, Edward A., Helliwell, Richard Perham, Wrenn, Richard Fitzhugh
• Granted Patent: US 7,466,699 B2
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 49/9047 including multiple buffers, e.g. buffer pools

Abstract

A system for addressing end-points in a network wherein a transmission is sent between a source end-point and a destination end-point via a respective source port and a destination port connected by a fabric. A payload offset and buffer pool handle are included in a network header sent with the transmission. The buffer pool handle is used to determine a specific queue of pool buffers within the destination port. A pool buffer descriptor, describing a header buffer and a payload buffer each within the destination end-point, is dequeued from a queue indicated by the buffer pool handle. The payload offset in the network header is then decoded to locate a first number of bytes of data in the transmission to be transferred into the header buffer a second number of bytes of data to be transferred into the payload buffer.

Claims

1. A method for addressing end-points in a network wherein each one of a plurality of ports in the network is coupled to at least one of the end-points, and wherein a transmission is sent between a source end-point and a destination end-point via a respective source port and a destination port connected by a fabric, the method comprising the steps of:

including a payload offset and buffer pool handle in a network header sent with the transmission;

wherein the buffer pool handle is used to determine a specific queue of pool buffers within the destination port;

receiving the transmission at the destination port;

dequeueing a pool buffer descriptor from a queue indicated by the buffer pool handle, wherein the pool buffer descriptor describes a header buffer and a payload buffer within the destination end-point; and

decoding the payload offset in the network header to locate a first number of bytes of data in the transmission to be transferred into the header buffer, and a second number of bytes of data to be transferred into the payload buffer.

2. The method of claim 1, wherein the buffer pool handle includes a buffer pool index for determining a specific queue of pool buffers within the destination port.

3. The method of claim 1, including the step of transferring the first number of bytes of data into the header buffer and the second number of bytes of data to into the payload buffer.

4. The method of claim 1, including the steps of:

generating at least one route master for each said port, wherein the route master describes a full route that indicates relationships between the source end-point, the destination end-point, the source port, and the destination port;

including, in the network header, a full route handle that encodes the source and destination end-points and the source and destination ports of the route over which the transmission is delivered;

using the full route handle to look up the route master in the destination port'"'"'s database; and

using information contained in the route master to index a table whose entries include indicia of each said port, to verify whether the route on which the transmission was sent indicates the source port.

5. The method of claim 4, wherein each transmission includes an S_ID that indicates the source port of a current port login, and wherein a verification is made that the transmission is received from the correct said port by performing the steps of:

including a route master index in the full route handle;

determining the route master using the route master index;

verifying whether the route master is in the active state;

determining the source port from which the message should have been sent using the remote port attribute of the route master; and

comparing the S_ID of the received message against the port ID of the remote port indicated by the route master to verify that the received S_ID corresponds to the current port login.

6. The method of claim 1, wherein the first number of bytes of data in the transmission to be transferred into the header buffer is the header size and the second number of bytes of data to be transferred into the payload buffer is the payload size, including the steps of:

storing the header size and the payload size into the pool buffer descriptor; and

queueing the pool buffer descriptor back to a completion queue at the destination end-point to indicate that a transmission has been received.

7. A method for addressing end-points in a network wherein each one of a plurality of ports in the network is coupled to at least one of the end-points, and wherein a transmission is sent between a source end-point and a destination end-point via a respective source port and a destination port connected by a fabric, the method comprising the steps of:

generating at least one route master for each said port, wherein the route master describes a full route, indicating relationships between the source end-point, the destination end-point, the source port, and the destination port;

including, in the network header, a full route handle that encodes the source and destination end-points and the source and destination ports of the route over which the transmission was delivered;

using the full route handle to look up the route master in the destination port'"'"'s database; and

using information contained in the route master to index a table whose entries include indicia of each said port, to verify whether the route on which the transmission was sent indicates the source port.

8. The method of claim 7, wherein each transmission includes an S_ID that indicates the source port of a current port login, and wherein a verification is made that the transmission is received from the correct said port by performing the steps of:

including a route master index in the full route handle;

determining the route master using the route master index;

verifying whether the route master is in the active state;

determining the source port from which the message should have been sent using the remote port attribute of the route master; and

comparing the S_ID of the received message against the port ID of the remote port indicated by the route master to verify that the received S_ID corresponds to the current port login.

9. A method for addressing end-points in a network wherein each one of a plurality of ports in the network is coupled to at least one of the end-points, and wherein a transmission is sent between a source end-point and a destination end-point via a respective source port and a destination port connected by a fabric, the method comprising the steps of:

generating at least one route master for each said port, wherein the route master describes a full route indicating relationships between the source end-point, the destination end-point, the source port, and the destination port;

including a payload offset, buffer pool handle, and full route handle in a network header sent with the transmission;

wherein the buffer pool handle includes a buffer pool index used to index a specific queue of pool buffers within the destination port;

receiving the transmission;

using the full route handle to look up the route master in the destination port'"'"'s database;

using information contained in the route master to index a table whose entries include indicia of each said remote port, to verify whether the route on which the transmission was sent includes the source port;

dequeueing a pool buffer descriptor from a queue indicated by the destination end-point and the buffer pool index, wherein the pool buffer descriptor contains indicia of a header buffer and a payload buffer each within the destination end-point; and

decoding the payload offset in the network-header to locate a first number of bytes of data in the transmission to be transferred into the header buffer and a second number of bytes of data to be transferred into the payload buffer.

10. The method of claim 9, wherein each transmission includes an S_ID that indicates the source port of a current port login, and wherein a verification is made that the transmission is received from the correct said port by performing the steps of:

including a route master index in the full route handle;

determining the route master using the route master index;

verifying whether the route master is in the active state;

determining the source port from which the message should have been sent using the remote port attribute of the route master; and

comparing the S_ID of the received message against the port ID of the remote port indicated by the route master to verify that the received S_ID corresponds to the current port login.

11. The method of claim 9, wherein the first number of bytes of data in the transmission to be transferred into the header buffer is the header size and the second number of bytes of data to be transferred into the payload buffer is the payload size, including the steps of:

storing the header size and the payload size into the pool buffer descriptor; and

queueing the pool buffer descriptor back to a completion queue at the destination end-point to indicate that a transmission has been received.

12. The method of claim 9, including the step of transferring the first number of bytes of data into the header buffer and the second number of bytes of data to into the payload buffer.

13. The method of claim 9, wherein the network header follows a Fibre Channel header in the transmission.

14. A system for addressing end-points in a network wherein each one of a plurality of ports in the network is coupled to at least one of the end-points, and wherein a transmission is sent between a source end-point and a destination end-point via a respective source port and a destination port connected by a fabric, the system comprising:

a network header, sent with the transmission, including a payload offset and buffer pool handle, wherein the buffer pool handle is used to determine a specific queue of pool buffers within the destination port;

a header buffer and a payload buffer; and

a pool buffer descriptor, describing the header buffer and the payload buffer, located in a queue indicated by the buffer pool handle;

wherein the payload offset in the network header is decoded to locate a first number of bytes of data in the transmission to be transferred into the header buffer a second number of bytes of data to be transferred into the payload buffer.

15. The system of claim 14, wherein the buffer pool handle includes a buffer pool index for determining a specific queue of pool buffers within the destination port.

16. The system of claim 14, further including:

at least one route master corresponding to each said port, wherein the route master describes a full route that indicates relationships between the source end-point, the destination end-point, the source port, and the destination port;

a full route handle, located in the network header, that encodes the source and destination end-points and the source and destination ports of the route over which the transmission is delivered;

wherein the full route handle provides indicia of the route master in the destination port'"'"'s database; and

wherein the route master includes indicia of a table whose entries include indicia of each said port, for verifying whether the route on which the transmission was sent includes both the source port and the destination port.

17. The system of claim 16, further including a route master index in the full route handle, wherein a port ID is assigned to the source port and the route master includes a remote port attribute comprising indicia of the remote port;

wherein;

the route master is determined using the route master index;

the source port from which the message should have been sent is determined using the remote port attribute of the route master; and

the S_ID of the received message is compared with the port ID of the remote port indicated by the route master to verify that the received S_ID corresponds to the current port login.

18. The system of claim 16, wherein the first number of bytes of data in the transmission to be transferred into the header buffer is the header size and the second number of bytes of data to be transferred into the payload buffer is the payload size, and wherein:

the header size and the payload size are stored into the pool buffer descriptor; and

the pool buffer descriptor is queued back to a completion queue at the destination end-point to indicate that a transmission has been received.