NETWORK INTERFACE AND PROTOCOL

• US 20110040897A1
• Filed: 10/22/2010
• Published: 02/17/2011
• Est. Priority Date: 09/16/2002
• Status: Active Grant

• Current Assignee: Xilinx, Inc. (Advanced Micro Devices, Inc.)
• Original Assignee: SolarFlare Communications Incorporated (Advanced Micro Devices, Inc.)
• Inventors: Clarke, David Julian, POPE, Steve Leslie, Roberts, Derek Edward, Riddoch, David James
• Granted Patent: US 9,112,752 B2
• Time in Patent Office: Days
• US Class Current: 709/250
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function

Abstract

A communication interface for providing an interface between a data link and a data processor, the data processor being capable of supporting an operating system and a user application, the communication interface being arranged to: support a first queue of data received over the link and addressed to a logical data port associated with a user application; support a second queue of data received over the link and identified as being directed to the operating system; and analyse data received over the link and identified as being directed to the operating system or the data port to determine whether that data meets one or more predefined criteria, and if it does meet the criteria transmit an interrupt to the operating system.

Claims

1. A communication interface for providing an interface between a data link and a data processor, the data processor being capable of supporting an operating system, a virtual address space and one or more data ports associated with the virtual address space, the communication interface being arranged to:

apply to a first queue located in the virtual address space data received over the link and identified as being directed to a particular logical data port;

apply to a second queue located in the address space of the operating system out-of-band data received over the link for the particular logical data port and identified as being directed to the operating system, the second queue being memory mapped into the virtual address space; and

analyse data received over the link and identified as being directed to the operating system or the data port to determine whether that data meets one or more predefined criteria, and if it does meet the criteria transmit an interrupt to the operating system, the predefined criteria being set such that, when the handling of the received data is blocked, the communication interface transmits an interrupt to the operating system on receiving data identified as being directed to that data port.

2. A communication interface as claimed in claim 1, wherein one of the predefined criteria is such that if the data received over the link matches one or more predetermined message forms then the communication interface will transmit an interrupt to the operating system.

3. A communication interface as claimed in claim 1, wherein the communication interface is arranged to, if the data meets one or more of the predefined criteria and one or more additional criteria, transmit an interrupt to the operating system and transmit a message to the operating system indicating a port to which the data was addressed.

4. A communication interface as claimed in claim 3, wherein the additional criteria are indicative of an error condition.

5. A communication interface as claimed in claim 1, wherein the communication interface is arranged to apply to a third queue data received over the link and addressed to the logical data port, and is arranged to apply to the first queue data units received over the link and of a form having a fixed length and to apply to the third queue data units received over the link and of a form having a variable length.

6. A communication interface as claimed in claim 5, wherein the data units of a fixed size include messages received over the link and interpreted by the communication interface as indicating an error status.

7. A communication interface as claimed in claim 5, wherein the data units of a fixed size include messages received over the link and interpreted by the communication interface as indicating a request for or acknowledgement of set-up of a connection.

8. A communication interface as claimed in claim 6, wherein the data units of a fixed size include messages received over the link and interpreted by the communication interface as indicating a data delivery event.

9. A communication interface as claimed in claim 1, wherein the communication interface is arranged to analyse the content of each data unit received over the link and to determine in dependence on the content of that data unit which of the said queues to apply the data unit to.

10. A communication interface as claimed in claim 1, wherein the communication interface is configurable by the operating system to set the said criteria.

11. A communication interface as claimed in claim 1, wherein one or both of the communication interface and the operating system is responsive to a message of a predetermined type to return a message including information indicative of the status of the port.

12. A communication system including a communication interface as claimed in claim 1 and the data processor, the data processor being arranged to set the predefined criteria such that, when the handling of the received data is blocked, the communication interface will transmit an interrupt to the operating system on receiving data identified as being directed to that data port.