Granted Patent B2

US 12,192,116 · App. 18/235,860 · Granted Jan 7, 2025

Inventors: Boon S. Ang (Saratoga, CA); Wenyi Jiang (Fremont, CA); Guolin Yang (San Jose, CA); Jin Heo (Los Altos, CA); Srividya Murali (San Jose, CA)

Assignee: VMware LLC

H04L47/80H04L45/38H04L47/12H04L47/781H04L49/109H04L49/3009H04L49/70

Abstract

Claims (28)

1. A physical network interface card (PNIC) of a host computer executing a plurality of machines, the PNIC comprising:

a plurality of interfaces;

a flow processing offload (FPO) comprising:

a mapping table storing a plurality of mappings with each mapping associating a virtual port identifier (VPID) of an interface of one machine executing on the host computer with a physical port identifier (PPID) of an interface of the PNIC;

a flow entry table storing a plurality of flow entries, each flow entry in the plurality of flow entries associating a set of flow attributes with a VPID; and

the FPO, for a received data message, (1) identifying a flow entry that specifies a VPID as a destination of the data message, and (2) using the identified VPID to identify a mapping in the mapping table that associates the identified VPID to a PPID of the PNIC interface that should be used as an egress interface of the PNIC for sending out the received data message.

2. The PNIC of claim 1 , wherein the plurality of mappings between VPIDs and PPIDs is received at the PNIC from a flow processing and action generator that generates the mappings based on configuration data regarding VPIDs and PPIDs received by the flow processing and action generator.

3. The PNIC of claim 1 , wherein the flow entries are received from the flow processing and action generator that processes a first data message in each data message flow to identifies a destination of the first data message, generates a flow entry based on the identified destination, and provides the flow entry for storing in the flow table for the data message flow for use for subsequent data messages of the data message flow.

4. The PNIC of claim 3 , further comprising at least one processing unit for executing the flow processing and action generator.

5. The PNIC of claim 3 , wherein the flow processing and action generator executes on one of said machines that executes on the host computer.

6. The PNIC of claim 1 , wherein the mapping table is stored in a content addressable memory unit.

7. The PNIC of claim 1 , wherein the flow entry is stored in a content addressable memory unit.

8. The PNIC of claim 1 , wherein at least one PNIC interface is a physical function (PF) of a bus that is used to connect the PNIC to the host computer.

9. The PNIC of claim 8 , wherein the PF connects to a software switch executing on the host computer.

10. The PNIC of claim 1 , wherein at least one PNIC interface is a virtual function (VF) associated with a bus that is used to connect the PNIC to the host computer.

11. The PNIC of claim 10 , wherein the VF communicates with an interface of one machine.

12. The PNIC of claim 11 , wherein the VF communicates with the machine interface through a VF driver that executes on the host computer.

13. A method for processing flows on a host computer comprising a physical network interface card (PNIC) and a plurality of interfaces, and executing a plurality of machines, the method comprising:

storing, in a mapping table of a flow processing offload (FPO) of the PNIC, a plurality of mappings with each mapping associating a virtual port identifier (VPID) of an interface of one machine executing on the host computer with a physical port identifier (PPID) of an interface of the PNIC;

storing, in a flow entry table of the FPO, storing a plurality of flow entries, each flow entry in the plurality of flow entries associating a set of flow attributes with a VPID; and

configuring the FPO, for a received data message, (1) to identify a flow entry that specifies a VPID as a destination of the data message, and (2) to use the identified VPID to identify a mapping in the mapping table that associates the identified VPID to a PPID of the PNIC interface that should be used as an egress interface of the PNIC for sending out the received data message.

14. The method of claim 13 further comprising providing the plurality of mappings from a flow processing and action generator that generates the mappings based on configuration data regarding VPIDs and PPIDs received by the flow processing and action generator.

15. The method of claim 13 further comprising providing the flow entries from the flow processing and action generator that processes a first data message in each data message flow to identifies a destination of the first data message, generates a flow entry based on the identified destination, and provides the flow entry for storing in the flow table for the data message flow for use for subsequent data messages of the data message flow.

16. The method of claim 15 , wherein at least one processing unit of the PNIC executes the flow processing and action generator.

17. The method of claim 15 , wherein at least one processing unit of the host computer executes the flow processing and action generator.

18. The method of claim 13 , wherein the mapping table is stored in a content addressable memory unit.

19. The method of claim 13 , wherein the flow entry is stored in a content addressable memory unit.

20. The method of claim 13 , wherein at least one PNIC interface is a physical function (PF) of a bus that is used to connect the PNIC to the host computer.

Assignments (2)

Continuity (3)

References Cited (400)