Dynamically-connected transport service

• US 8,213,315 B2
• Filed: 11/19/2009
• Issued: 07/03/2012
• Est. Priority Date: 11/19/2009
• Status: Active Grant

• Current Assignee: Mellanox Technologies Limited (NVIDIA Corporation)
• Original Assignee: Mellanox Technologies Limited (NVIDIA Corporation)
• Inventors: Crupnicoff, Diego, Kagan, Michael, Shahar, Ariel, Chapman, Hillel, Bloch, Noam
• Primary Examiner(s): Yao, Kwang B
• Assistant Examiner(s): Ngo, Nguyen
• Application Number:
  US12/621,523
• Publication Number:
  US 20110116512A1
• Time in Patent Office: 957 Days
• Field of Search: 370/229, 370/230, 370/230.1, 370/231, 370/235, 370/236, 370/395.2, 370/412, 370/419
• US Class Current: 370/236
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04Q 2213/13389 LAN, internet

Abstract

A method of communication includes receiving, in a network interface device, first and second requests from an initiator process running on an initiator host to transmit, respectively, first and second data to first and second target processes running on one or more target nodes, via a packet network. A single dynamically-connected initiator context is allocated for serving both the first and second requests. A first connect packet referencing the dynamically-connected (DC) initiator context is directed to the first target process so as to open a first dynamic connection with the first target process, followed by transmission of the first data over the first dynamic connection. The first dynamic connection is closed after the transmission of the first data, and a second connect packet is transmitted so as to open a second dynamic connection with the second target process, followed by transmission of the second data.

Claims

1. A method of communication, comprising:

receiving, in a network interface device coupled to an initiator host, first and second requests from an initiator process running on the initiator host to transmit, respectively, first and second data to first and second target processes running respectively on different first and second target nodes, via a packet network;

allocating in the network interface device a single dynamically-connected initiator context for serving both the first and second requests;

transmitting from the network interface device over the packet network a first connect packet referencing the dynamically-connected (DC) initiator context and directed to the first target process so as to open a first dynamic connection with the first target process, followed by transmission of the first data over the first dynamic connection; and

closing the first dynamic connection after the transmission of the first data, and transmitting a second connect packet referencing the DC initiator context and directed to the second target process so as to open a second dynamic connection with the second target process, followed by transmission of the second data over the second dynamic connection.

2. The method according to claim 1, and comprising receiving an acknowledgment packet from the first target node in response to transmitting the data.

3. The method according to claim 2, wherein the network interface device transmits the first data over the first dynamic connection without waiting for any acknowledgment from the first target node.

4. The method according to claim 2, wherein closing the first dynamic connection comprises waiting to close the first dynamic connection until the network interface device has received the acknowledgment packet.

5. The method according to claim 1, wherein closing the first dynamic connection comprises transmitting a disconnect packet over the first dynamic connection to the first target process.

6. The method according to claim 5, wherein the first target node does not acknowledge the disconnect packet, and wherein the second connect packet is transmitted immediately after transmitting the disconnect packet.

7. The method according to claim 1, wherein receiving the first and second requests comprises queuing, for execution by the network interface device, one or more first work queue elements (WQEs) referencing the first target process, followed by one or more second WQEs referencing to the second target process, and wherein the network interface device closes the first dynamic connection upon reaching a first one of the second WQEs for execution.

8. The method according to claim 1, and comprising, upon receiving the first connect packet at a target node, allocating a DC responder context for receiving the first data at the target node, and after closing the first dynamic connection, reallocating the DC responder context at the target node to receive further data from another DC initiator.

9. The method according to claim 8, wherein allocating the DC responder context comprises selecting the DC responder context from a group of DC responder contexts belonging to a DC target specified by the first connect packet.

10. The method according to claim 8, wherein receiving the first connect packet comprises receiving and counting multiple connect packets at the target node from the DC initiator context in response to retries by the network interface device, and reallocating the DC target context after all of the connect packets have been received.

11. A network communication device, comprising:

a host interface, which is coupled to receive from an initiator host first and second requests from an initiator process running on the initiator host to transmit, respectively, first and second data to first and second target processes running respectively on different first and second target nodes, via a packet network;

a network interface, coupled to the packet network; and

processing circuitry, which is configured, using a single dynamically-connected initiator context allocated to serve both the first and second requests, to transmit via the network interface a first connect packet referencing the dynamically-connected initiator context and directed to the first target process so as to open a first dynamic connection with the first target process, followed by transmission of the first data over the first dynamic connection, and to close the first dynamic connection after the transmission of the first data and to transmit via the network interface a second connect packet referencing the dynamically-connected initiator context and directed to the second target process so as to open a second dynamic connection with the second target process, followed by transmission of the second data over the second dynamic connection.

12. The device according to claim 11, wherein the processing circuitry is configured to receive and process an acknowledgment packet from the first target node in response to transmitting the first connect packet.

13. The device according to claim 12, wherein the processing circuitry is configured to transmit the first data over the first dynamic connection without waiting for any acknowledgment from the first target node.

14. The device according to claim 12, wherein the processing circuitry is configured to wait to close the first dynamic connection until the acknowledgment packet has been received.

15. The device according to claim 11, wherein the processing circuitry is configured to transmit a disconnect packet over the first dynamic connection to the first target process in order to close the first dynamic connection.

16. The device according to claim 15, wherein the first target node does not acknowledge the disconnect packet, and wherein the second connect packet is transmitted immediately after transmitting the disconnect packet.

17. The device according to claim 11, wherein the processing circuitry is configured to process a queue comprising one or more first work queue elements (WQEs) referencing the first target process, followed by one or more second WQEs referencing to the second target process, and to close the first dynamic connection upon reaching a first one of the second WQEs for execution.

18. A network communication system, comprising:

a first network interface device, which is coupled to an initiator host so as to receive first and second requests from an initiator process running on the initiator host to transmit, respectively, first and second data to first and second target processes running respectively on different first and second target nodes, via a packet network,

wherein the first network interface device is configured, using a single dynamically-connected initiator context allocated to serve both the first and second requests, to transmit via the network interface a first connect packet referencing the dynamically-connected initiator context and directed to the first target process so as to open a first dynamic connection with the first target process, followed by transmission of the first data over the first dynamic connection, and to close the first dynamic connection after the transmission of the first data and to transmit via the network interface a second connect packet referencing the dynamically-connected initiator context and directed to the second target process so as to open a second dynamic connection with the second target process, followed by transmission of the second data over the second dynamic connection; and

a second network interface device, which is coupled to a target host on the first target node and is configured upon receiving the first connect packet, to allocate a DC responder context for receiving the first data at the first target node, and after closing the first dynamic connection, to reallocate the DC responder context to receive further data from another DC initiator.

19. The system according to claim 18, wherein the second network interface device is configured to select the DC responder context from a group of DC responder contexts belonging to a DC target specified by the first connect packet.

20. The system according to claim 18, wherein the second network interface device is configured to count multiple connect packets received at the first target node from the DC initiator context in response to retries by the network interface device, and to reallocate the DC target context after all of the connect packets have been received.