Reception according to a data transfer protocol of data directed to any of a plurality of destination entities for data extraction

• US 8,645,558 B2
• Filed: 06/15/2006
• Issued: 02/04/2014
• Est. Priority Date: 06/15/2005
• Status: Active Grant

• Current Assignee: Xilinx, Inc. (Advanced Micro Devices, Inc.)
• Original Assignee: SolarFlare Communications Incorporated (Advanced Micro Devices, Inc.)
• Inventors: Pope, Steven Leslie, Roberts, Derek Edward, Riddoch, David James, Law, Greg, Grantham, Steve, Slattery, Matthew
• Primary Examiner(s): Park, Jeong S
• Application Number:
  US11/916,973
• Publication Number:
  US 20120124121A1
• Time in Patent Office: 2,791 Days
• Field of Search: 709/230, 711/111, 719/328, 370466-467
• US Class Current: 709/230
• CPC Class Codes: G06F 13/00 Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units interface circuits for specific input/output devices G06F3/00 ; multiprogram control therefor G06F9/46; multiprocessor systems G06F15/16
• CPC Class Codes: G06F 13/14 Handling requests for interconnection or transfer
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 9/30181 Instruction operation extension or modification
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 49/9094 Arrangements for simultaneous transmit and receive, e.g. simultaneous reading/writing from/to the storage element
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/325 in the network layer [OSI layer 3], e.g. X.25 H04L69/16 takes precedence

Abstract

A data processing system arranged for receiving over a network, according to a data transfer protocol, data directed to any of a plurality of destination identities, the data processing system comprising: data storage (event queues 31-33) for storing data received over the network; and a first processing arrangement for performing processing in accordance with the data transfer protocol on received data in the data storage, for making the received data available to respective destination identities; and a response former arranged for: receiving a message (dashed line on FIG. 4) requesting a response indicating the availability of received data to each of a group of destination identities; and forming such a response; wherein the system is arranged to, in dependence on receiving the said message: identify received data that is directed to any destination identity that is both a member of the group and a member of a subset of the plurality of destination identities, and on which processing has not yet been performed; trigger processing by the first processing arrangement in accordance with the protocol on only the identified data; and subsequently form a response based at least partly on the result of the triggered processing, wherein the response (table 40-41) is formed so as to comprise a positive indication (41) of availability of data for a destination identity of the group if the triggered processing caused data to be made available to the respective destination identity.

Claims

1. A data processing system for receiving data from a network, and processing that data in accordance with a network protocol to extract traffic data therefrom, the data processing system having:

a memory;

a network interface for receiving the data from the network and storing the data in the memory;

an operating system for supporting one or more applications;

an application supported by the operating system; and

a protocol processing entity providing an application programming interface (API) configured to process the received data in accordance with a network protocol to extract traffic data therefrom, the protocol processing entity being arranged to perform protocol processing of the received data in the memory in response to signaling from a thread of the application to request whether data is available for one or more endpoints of the data processing system.

2. The data processing system as claimed in claim 1, wherein the protocol processing entity is a software entity that runs at a higher level than the operating system.

3. The data processing system as claimed in claim 2, wherein the protocol processing entity runs at user level.

4. The data processing system as claimed in claim 2, wherein the protocol processing entity is constituted by a function library.

5. The data processing system as claimed in claim 1, wherein the memory comprises a plurality of buffers each associated with a respective endpoint of the data processing system.

6. The data processing system as claimed in claim 1, wherein the memory comprises a buffer for storing data indicating events, and the network interface device is arranged to, on receiving data from the network, store it in the memory and also store data indicating a corresponding event in the event buffer.

7. The data processing system as claimed in claim 1, wherein the said signaling is a select( )and/or a poll( )call.

8. The data processing system as claimed in claim 7, wherein the call is resolved by the data processing system by means of a static linkage.

9. The data processing system as claimed in claim 7, wherein the call is resolved by the data processing system by means of a dynamic linkage.

10. The data processing system as claimed in claim 1, wherein the protocol processing entity is arranged to perform protocol processing of data in the context of the thread that signaled the protocol processing entity to do so.

11. The data processing system as claimed in claim 1 wherein the network protocol is TCP/IP.

12. The data processing system as claimed in claim 1, wherein the protocol processing entity supports BSD, Posix or Winsock network sockets.