Apparatus and method for supporting received data processing in an offload of network protocol processing

• US 7,493,427 B2
• Filed: 07/14/2004
• Issued: 02/17/2009
• Est. Priority Date: 07/14/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Tracey, John Michael, Sahu, Sambit, Pradhan, Prashant, Freimuth, Douglas Morgan, Mraz, Ronald, Nahum, Erich M., Hu, Elbert C.
• Primary Examiner(s): Patel; Niketa I
• Assistant Examiner(s): Huson; Zachary K
• Application Number:
  US10/891,196
• Publication Number:
  US 20060015618A1
• Time in Patent Office: 1,679 Days
• Field of Search: 710/52
• US Class Current: 710/52
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: H04L 47/621 Individual queue per connection or flow, e.g. per VC
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/9052 with buffers of different sizes
• CPC Class Codes: H04L 49/9063 Intermediate storage in different physical parts of a node or terminal

Abstract

A number of improvements in network adapters that offload protocol processing from the host processor are provided. Specifically, an improved mechanism for handling receipt of data packets in a system utilizing an offload network adapter. The offload network adapter may include logic that permits the offload network adapter to delay notification of data reception to the host system in different ways. The advantage of delaying the notice of data packet reception to the host system is the potential for aggregation of several data packets, which can arrive immediately after the first one, for example, in a single notification. Given a stream with continuous data packet arrival, a value may be set, either statically or dynamically, for notification delay and this value may be configurable for the host system per communication socket.

Claims

1. A method, in a data processing system, for transferring data to a host system from a network adapter, comprising:

receiving, in the network adapter, the data for transferring to the host system;

determining whether a connection specific application buffer is allocated for a connection associated with the data;

determining whether to wait for a specific application buffer to be allocated for the connection associated with the data, responsive to a determination that a connection specific application buffer has not been allocated for the connection;

selecting a non-connection specific application buffer from a pool of buffers to receive the data responsive to a determination not to wait for a specific application buffer to be allocated;

transferring the data to the selected non-connection specific application buffer;

examining descriptors generated by the network adapter for the data;

determining whether the descriptors reference a consecutive physical address space; and

providing the descriptors to the host system in a single bulk transaction between the network adapter and the host system responsive to a determination that the descriptors reference a consecutive physical address space.

2. The method of claim 1, further comprising:

waiting for a connection specific application buffer to be allocated for the connection associated with the data, responsive to a determination to wait for a specific application buffer to be allocated.

3. The method of claim 2, wherein waiting for a connection specific application buffer includes:

determining whether a maximum wait time is met or exceeded; and

discontinuing waiting for a connection specific application buffer responsive to a determination that the maximum wait time is met or exceeded.

4. The method of claim 3, wherein the maximum wait time is determined based on historical data of the host system supplying connection specific application buffers.

5. The method of claim 1, wherein determining whether to wait for a connection specific application buffer to be allocated includes determining whether a wait parameter has been set in the network adapter.

6. The method of claim 1, wherein determining whether to wait for a connection specific application buffer includes determining, in the network adapter, whether to wait for a connection specific application buffer based on historical data of the host system supplying connection specific application buffers.

7. The method of claim 1, wherein selecting a non-connection specific application buffer from a pool of buffers to receive the data includes:

using characteristic information for each non-connection specific application buffer in the pool of buffers to determine a best match for the data.

8. The method of claim 7, wherein the characteristic information includes at least one of buffer size, buffers speed, and placement of the buffer in the host processor architecture.

9. The method of claim 1, further comprising:

determining whether the data should be injected into an L3 cache of the host system; and

transferring the data directly to the L3 cache using a cache injection mechanism responsive to a determination that the data should be injected into the L3 cache of the host system.

10. The method of claim 1, further comprising:

peeking at a header of the data to determine a type of the data; and

identifying a connection for routing the data based on the type of the data.

11. The method of claim 10, further comprising:

determining a size of the header based on peeking at the header; and

setting an offset for skipping over the header and accessing a payload of the data based on the size of the header.

12. A computer program product in a computer recordable medium for transferring data to a host system from a network adapter, comprising:

first instructions for receiving, in the network adapter, the data for transferring to the host system;

second instructions for determining whether a connection specific application buffer is allocated for a connection associated with the data;

third instructions for determining whether to wait for a specific application buffer to be allocated for the connection associated with the data, responsive to a determination that a connection specific application buffer has not been allocated for the connection;

fourth instructions for selecting a non-connection specific application buffer from a pool of buffers to receive the data responsive to a determination not to wait for a specific application buffer to be allocated;

fifth instructions for transferring the data to the selected non-connection specific application buffer;

sixth instructions for examining descriptors generated by the network adapter for the data;

seventh instructions for determining whether the descriptors reference a consecutive physical address space; and

eighth instructions for providing the descriptors to the host system in a single bulk transaction between the network adapter and the host system responsive to a determination that the descriptors reference a consecutive physical address space.

13. The computer program product of claim 12, further comprising:

ninth instructions for waiting for a connection specific application buffer to be allocated for the connection associated with the data, responsive to a determination to wait for a specific application buffer to be allocated.

14. The computer program product of claim 13, wherein the ninth instructions for waiting for a connection specific application buffer include:

instructions for determining whether a maximum wait time is met or exceeded; and

instructions for discontinuing waiting for a connection specific application buffer responsive to a determination that the maximum wait time is met or exceeded.

15. The computer program product of claim 14, wherein the maximum wait time is determined based on historical data of the host system supplying connection specific application buffers.

16. The computer program product of claim 12, wherein the third instructions for determining whether to wait for a connection specific application buffer to be allocated include instructions for determining whether a wait parameter has been set in the network adapter.

17. The computer program product of claim 12, wherein the third instructions for determining whether to wait for a connection specific application buffer include instructions for determining, in the network adapter, whether to wait for a connection specific application buffer based on historical data of the host system supplying connection specific application buffers.

18. The computer program product of claim 12, wherein the fourth instructions for selecting a non-connection specific application buffer from a pool of buffers to receive the data include:

instructions for using characteristic information for each non-connection specific application buffer in the pool of buffers to determine a best match for the data.

19. The computer program product of claim 18, wherein the characteristic information includes at least one of buffer size, buffers speed, and placement of the buffer in the host processor architecture.

20. The computer program product of claim 12, further comprising:

ninth instructions for determining whether the data should be injected into an L3 cache of the host system; and

tenth instructions for transferring the data directly to the L3 cache using a cache injection mechanism responsive to a determination that the data should be injected into the L3 cache of the host system.

21. The computer program product of claim 12, further comprising:

ninth instructions for peeking at a header of the data to determine a type of the data; and

tenth instructions for identifying a connection for routing the data based on the type of the data.

22. The computer program product of claim 21, further comprising:

eleventh instructions for determining a size of the header based on peeking at the header; and

ninth instructions for setting an offset for skipping over the header and accessing a payload of the data based on the size of the header.

23. A system for transferring data to a host system from a network adapter, comprising:

mechanism for receiving, in the network adapter, the data for transferring to the host system;

mechanism for determining whether a connection specific application buffer is allocated for a connection associated with the data;

mechanism for determining whether to wait for a specific application buffer to be allocated for the connection associated with the data, responsive to a determination that a connection specific application buffer has not been allocated for the connection;

mechanism for selecting a non-connection specific application buffer from a pool of buffers to receive the data responsive to a determination not to wait for a specific application buffer to be allocated;

mechanism for transferring the data to the selected non-connection specific application buffer;

mechanism for examining descriptors generated by the network adapter for the data;

mechanism for determining whether the descriptors reference a consecutive physical address space; and

mechanism for providing the descriptors to the host system in a single bulk transaction between the network adapter and the host system responsive to a determination that the descriptors reference a consecutive physical address space.

24. The system of claim 23, further comprising:

mechanism for waiting for a connection specific application buffer to be allocated for the connection associated with the data, responsive to a determination to wait for a specific application buffer to be allocated.

25. The system of claim 24, wherein the mechanism for waiting for a connection specific application buffer includes:

mechanism for determining whether a maximum wait time is met or exceeded; and

mechanism for discontinuing waiting for a connection specific application buffer responsive to a determination that the maximum wait time is met or exceeded.

26. The system of claim 25, wherein the maximum wait time is determined based on historical data of the host system supplying connection specific application buffers.

27. The system of claim 23, wherein the mechanism for determining whether to wait for a connection specific application buffer to be allocated includes mechanism for determining whether a wait parameter has been set in the network adapter.

28. The system of claim 23, wherein the mechanism for determining whether to wait for a connection specific application buffer includes mechanism for determining, in the network adapter, whether to wait for a connection specific application buffer based on historical data of the host system supplying connection specific application buffers.

29. The system of claim 23, wherein the mechanism for selecting a non-connection specific application buffer from a pool of buffers to receive the data includes:

mechanism for using characteristic information for each non-connection specific application buffer in the pool of buffers to determine a best match for the data.

30. The system of claim 29, wherein the characteristic information includes at least one of buffer size, buffers speed, and placement of the buffer in the host processor architecture.

31. The system of claim 23, further comprising:

mechanism for determining whether the data should be injected into an L3 cache of the host system; and

mechanism for transferring the data directly to the L3 cache using a cache injection mechanism responsive to a determination that the data should be injected into the L3 cache of the host system.

32. The system of claim 23, further comprising:

mechanism for peeking at a header of the data to determine a type of the data;

and mechanism for identifying a connection for routing the data based on the type of the data.

33. The system of claim 32, further comprising:

mechanism for determining a size of the header based on peeking at the header;

and mechanism for setting an offset for skipping over the header and accessing a payload of the data based on the size of the header.