Method for efficient routing in a network interface card

• US 9,390,056 B1
• Filed: 12/19/2011
• Issued: 07/12/2016
• Est. Priority Date: 12/19/2011
• Status: Active Grant

• Current Assignee: Chelsio Communications Incorporated
• Original Assignee: Chelsio Communications Incorporated
• Inventors: Noureddine, Wael, Eiriksson, Asgeir Thor
• Primary Examiner(s): Cox, Natisha
• Application Number:
  US13/330,513
• Time in Patent Office: 1,667 Days
• Field of Search: 709/219, 709/220, 370/389, 370/392
• US Class Current: 1/1
• CPC Class Codes: G06F 13/4022 using switching circuits, e.g. switching matrix, connection or expansion network G06F13/4009 takes precedence
• CPC Class Codes: G06F 15/1735 Network adapters, e.g. SCI, Myrinet protocol engines H04L69/12
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 67/2866 Architectures; Arrangements
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

Packet switching is facilitated between a source and a destination through a network interface card. In accordance with an aspect, a NIC is configured to switch ingress packets—coming from the network—selectively to one or multiple destinations (in a NIC which is capable of replicating packets) on the host computer, and alternatively or additionally (in a NIC which is capable of replicating packets) back to one or multiple destinations on the network. In multi-port NICs, this capability effectively allows a NIC to perform the basic functions of a standalone network switch as well as additional useful functions.

Claims

1. Network interface circuitry configured to couple a host computer and a network, comprising:

a plurality of ports configured to transmit packets to and receive packets from the network;

a memory configured to implement a plurality of receive queues for facilitating receipt of data by the host, the data being at least a portion of the packets received;

logic to, based on a least a portion of a packet received on one of the plurality of ports, indicate which destination of one of any one of the ports and the host to indicate as a destination of data of the packet, wherein indicating the destination as said one of said any of the ports is an indication that the data of the packet is to be transmitted back out to the network from the network interface circuitry via the indicated said port.

2. The network interface circuitry of claim 1, wherein:

the network interface circuitry is configured to offload protocol processing from a host stack; and

the logic includes logic to determine whether the network interface circuitry is to perform offload protocol processing with regard to the received packet.

3. The network interface circuitry of claim 1, wherein:

the indication of the host as the destination of the packet includes an indication of one of a plurality of receive queues by which the host receives the data of the packets.

4. The network interface circuitry of claim 1, wherein:

the logic is further configured to cause rewrite of a header of the packet,

whereby the network interface circuitry operates as a router for packets for which a header has been rewritten.

5. The network interface circuitry of claim 1, wherein:

the logic is configured to rewrite at least one of both a layer two and layer three header, and only a layer three header, to thereby accomplish routing of the received packet.

6. The network interface circuitry of claim 1, wherein:

when the destination is any one of the ports and the logic indicates that the network interface circuitry is to operate as a proxy for the data of the packet, the network interface circuitry is configured to interoperate over the network, with the network interface circuitry as an origin and a peer destination of a packet including the data, reachable via the destination port and over the network.

7. The network interface circuitry of claim 1, wherein the logic is further configured to selectively cause, based on indicating a destination of data of a packet, replication and multicast of the data of the packet.

8. The network interface circuitry of claim 1, wherein the logic is further configured to cause rewrite of a payload portion of the data of the packet.

9. The network interface circuitry of claim 1, wherein the logic is further configured to cause insertion of a tag in a header portion of the packet.

10. The network interface circuitry of claim 1, wherein the destination indication logic is responsive at least in part to a configuration area of the network interface circuitry that is configurable with values by software executing on the host computer.

11. The network interface circuitry of claim 6, wherein:

the network interface circuitry is configured to offload protocol processing from a host stack to terminate a connection between the host and a first peer with respect to the received packet; and

the logic includes logic to determine whether the network interface circuitry is to perform offload protocol processing with regard to the received packet and, further, whether the network interface circuitry is to operate as a proxy for the data of the protocol-processed packet, the network interface circuitry is configured to interoperate over the network, with the network interface circuitry as an origin and a peer destination of a packet including the data, reachable via the destination port and over the network.

12. The network interface circuitry of claim 6, wherein:

the network interface circuitry is further configured to provide a copy of at least a portion of the received packet to the host.

13. The network interface circuitry of claim 1, wherein:

the logic includes logic to replicate at least a portion of the data of the received packet resulting in at least one replicated packet, and

the logic further includes logic to process the at least one replicated packet based at least in part on the data included in the at least one replicated packet.

14. The network interface circuitry of claim 13, wherein:

the logic includes logic to replicate at least a portion of the received packet resulting in at least one replicated packet includes logic to associate a virtual address as a layer 2 address for the at least one replicated packet, and

the logic further includes logic to process the at least one replicated packet based at least in part on the associated virtual address.

15. The network interface circuitry of claim 1, wherein:

the destination indication logic includes logic to process at least a portion of the packet and to selectively prevent, based thereon, the packet from being transmitted to the network from the network interface circuitry.

16. A method of coupling a host computer and a network, comprising:

via a plurality of ports of network interface circuitry that couples the host computer and the network, transmitting packets to and receiving packets from the network;

configuring a memory to implement a plurality of receive queues for facilitating receipt of data by the host, the data being at least a portion of the packets received; and

operating logic to, based on a least a portion of a packet received on one of the plurality of ports, indicate which destination of one of any one of the ports and the host to indicate as a destination of data of the packet, wherein indicating the destination as said one of said any of the ports is an indication that the data of the packet is to be transmitted back out to the network from the network interface circuitry via the indicated said port.

17. The method of claim 16, wherein:

the network interface circuitry is configured to offload protocol processing from a host stack; and

operating the logic includes operating the logic to determine whether the network interface circuitry is to perform offload protocol processing with regard to the received packet.

18. The method of claim 16, wherein:

operating the logic further includes operating the logic to cause rewrite of a header of the packet

whereby the network interface circuitry operates as a router for packets for which a header has been rewritten.

19. The method of claim 16, wherein:

operating the logic further includes operating the logic to rewrite at least one of both a layer two and layer three header, and only a layer three header, to thereby accomplish routing of the received packet.

20. The method of claim 16, wherein operating the logic further includes operating the logic to selectively cause, based on indicating a destination of data of a packet, replication and multicast of the data of the packet.

21. The method of claim 16, wherein operating the logic further includes operating the logic to cause rewrite of a payload portion of the data of the packet.

22. The method of claim 16, wherein:

operating the logic further includes operating the logic to replicate at least a portion of the data of the received packet resulting in at least one replicated packet, and

operating the logic to process the at least one replicated packet based at least in part on the data included in the at least one replicated packet.

23. The method of claim 22, wherein:

operating the logic further includes operating the logic to replicate at least a portion of the received packet resulting in at least one replicated packet includes logic to associate a virtual address as a layer 2 address for the at least one replicated packet, and

operating the logic to process the at least one replicated packet based at least in part on the associated virtual address.

24. The method of claim 16, wherein:

operating the logic includes operating the logic to process at least a portion of the packet and to selectively prevent, based thereon, the packet from being transmitted to the network from the network interface circuitry.

25. Network interface circuitry configured to couple a host computer and a network, comprising:

a plurality of ports configured to transmit packets to and receive packets from the network;

a memory configured to implement a plurality of receive queues for facilitating receipt of data by the host, the data being at least a portion of the packets received;

logic to, based on a least a portion of a packet received on one of the plurality of ports, indicate which destination of one of any one of the ports and the host to indicate as a destination of data of the packet.