Dual-driver interface

• US 9,690,724 B2
• Filed: 09/17/2014
• Issued: 06/27/2017
• Est. Priority Date: 03/02/2004
• Status: Active Grant

• Current Assignee: Xilinx, Inc. (Advanced Micro Devices, Inc.)
• Original Assignee: SolarFlare Communications Incorporated (Advanced Micro Devices, Inc.)
• Inventors: Pope, Steve Leslie, Riddoch, David James
• Primary Examiner(s): Onamuti, Gbemileke J
• Application Number:
  US14/489,417
• Publication Number:
  US 20150006772A1
• Time in Patent Office: 1,014 Days
• Field of Search: 370463, 719313, 726 17
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247

Abstract

A network interface device capable of communication with a data processing system supporting an operating system and at least one application, the network interface device supporting communication with the operating system by means of: two or more data channels, each data channel being individually addressable by the network interface device and being capable of carrying application-level data between the network interface device and the data processing device; and a control channel individually addressable by the network interface device and capable of carrying control data between the network interface device, the control data defining commands and the network interface being responsive to at least one command sent over the control channel to establish at least one additional data channel.

Claims

1. A network interface device comprising:

a first hardware interface configured to connect said network interface device with a data processing system supporting an operating system and at least one application;

a second hardware interface configured to connect said network interface device with a network; and

at least one processor and at least one memory configured to;

communicate with a first driver of the data processing system and a second driver of the data processing system, wherein the first driver has a first event queue, the second driver has a second event queue;

individually address respective data to each driver independently and directly by placing an event data block on the event queue associated with the respective driver being addressed;

determine if the event data block is of a first type or a second type;

if the event data block is of the first type, place an event data block on the event queue associated with the first driver;

if the event data block is of the second type, place an event data block on the event queue associated with the second driver; and

subsequently request execution of the respective driver by raising an interrupt.

2. The network interface device of claim 1 wherein a transfer of data between the network interface device via the first hardware interface and the first driver is independent of the transfer of data between the network interface device via the first hardware interface and second driver.

3. The network interface device of claim 2 wherein the first and second drivers are vertically separate.

4. The network interface device of claim 1 wherein each of the drivers provide at least one channel for communication between the network interface device and the data processing system.

5. The network interface device of claim 4 wherein the at least one data channel is one of:

a data channel for the transfer of traffic data between the network interface device and the data processing system; and

a control channel for the transfer of control data between the network interface device and the data processing system.

6. A network interface device as claimed in claim 5, wherein at least one of the data channels is operable according to a network device identification specification (NDIS) interface.

7. A network interface device as claimed in claim 5, wherein the control channel is operable according to the windows device model (WDM).

8. A network interface device as claimed in claim 5, wherein the network interface device is capable of supporting a communication link with another network interface device and of transmitting over the communication link application-level data received over one the at least one data channels.

9. A network interface device as claimed in claim 5, wherein the network interface device is configured to transmit and/or receive data over a data channel in the form of data packets.

10. A network interface device as claimed in claim 5, wherein the network interface device is configured to transmit and/or receive data over a data channel in the form of internet protocol packets.

11. A network interface device as claimed in claim 5, wherein each channel is configured to be triggered by means of a single interrupt.

12. A network interface device as claimed in claim 11, wherein said at least one processor and at least one memory are configured to trigger said interrupt if a respective event queue includes event messages.

13. A network interface device as claimed in claim 11, wherein said at least one processor and at least one memory are configured to trigger said interrupt if a respective queue includes more than a predetermined number of event messages.

14. A network interface device as claimed in claim 11, wherein said at least one processor and at least one memory are configured to trigger said interrupt if an event message has been included in a respective event queue for longer than a predetermined period of time.

15. A network interface device as claimed in claim 11, wherein the said at least one processor and at least one memory are configured to trigger said interrupt if longer than a predetermined period of time has elapsed since a respective event queue was empty of messages.

16. A network interface device as claimed in claim 5, wherein said at least one processor and at least one memory are configured on deactivation of a control channel, to signal the or each data channel with a message indicative of deactivation of the control channel.

17. A method for transferring data comprising:

transferring data from a network interface device to a first driver of a data processing device supporting an operating system and at least one application, said first driver having a first event queue; and

transferring data between the network interface device and a second driver of the data processing device, said second driver having a second event queue, wherein said transferring data comprises;

individually addressing respective data to each driver independently and directly by placing an event data block on the event queue associated with the respective driver being addressed;

determining if the event data block is of a first type or a second type;

if the event data block is of the first type, place an event data block on the event queue associated with the first driver;

if the event data block is of the second type, place an event data block on the event queue associated with the second driver; and

subsequently requesting execution of the respective driver by raising an interrupt.