CN114615187A - A logic interface data communication method and device - Google Patents

Abstract

The invention discloses a logical interface data communication method and device. By mapping the interface configuration of a logical interface to a kernel network card interface corresponding to a member interface, when receiving a data message accessing the logical interface itself, the received The data message is sent to the mapped kernel network card interface, and a response message from the kernel network card interface is received and sent through the logical interface. Therefore, the kernel protocol stack is used to process and respond to its own message, which improves the forwarding performance of the device. At the same time, it reduces the workload of its own communication protocol stack code adaptation and development, and improves product development efficiency and product stability. The invention reduces the huge investment in the development of dynamic routing table entries of three-layer logical interfaces such as link aggregation interfaces and VLAN interfaces.

Description

A logic interface data communication method and device

technical field

The present application belongs to the technical field of data communication, and in particular, relates to a data communication method and device for a logical interface based on a data plane development kit DPDK.

Background technique

The data plane development kit DPDK (Data Plane Development Kit) is mainly based on the Linux system. It is a set of function libraries and drivers for fast packet processing, which can greatly improve the data processing performance and throughput, and improve the work efficiency of data plane applications. DPDK provides KNI (Kernel NIC Interface) to facilitate communication between DPDK applications and the Linux kernel. This interface allows packets received from user mode to be forwarded to the Linux protocol stack, that is, allows user space applications to enter the Linux control plane. This interface is faster than the existing Linux TUN/TAP interface and allows standard Linux network tools (such as ethtool to be used) , ifconfig, tcpdump) to manage the DPDK interface and communicate with itself.

However, for network devices that use DPDK, such as security admission control gateways, and logical interfaces such as link aggregation interfaces, VLAN interfaces, tunnel interfaces, etc., DPDK does not provide such a KNI interface library function to perform interface processing. Manage and communicate with itself. Therefore, if you want to manage the logical interface and communicate with itself, you must transplant, integrate and encapsulate your own protocol stack to manage the interface.

However, due to the complexity of the kernel protocol stack, redeveloping the virtual NIC driver carried by the adaptation logical interface requires a lot of work and takes a long time.

SUMMARY OF THE INVENTION

The purpose of this application is to provide a logical interface data communication method and device, which can realize logical interface communication on DPDK-based network devices, reduce the workload of code adaptation and development of its own communication protocol stack, and improve product development efficiency and product stability. .

In order to achieve the above purpose, the technical solutions of the present application are as follows:

A logical interface data communication method, applied to a network device based on a data plane development kit DPDK, the logical interface data communication method comprising:

Create a logical interface and map the interface configuration of the logical interface to the kernel NIC interface corresponding to a member interface;

Receive the data message accessing the logical interface itself, and send the received data message to the mapped kernel network card interface;

Receive a response message from the kernel network card interface, and send it through the logical interface.

Optionally, the mapping of the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface includes:

When there is no member interface under the logical interface, when the member interface is added, the interface configuration of the logical interface is mapped to the kernel NIC interface corresponding to the first member interface;

When removing a member interface from a logical interface, determine whether the removed member interface is the first member interface. If it is the first member interface, delete the interface configuration of the kernel NIC interface corresponding to the removed member interface. Map the interface configuration of the logical interface to the kernel NIC interface corresponding to the new first member interface.

Optionally, the mapping of the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface includes:

When there are member interfaces under the logical interface, map the interface configuration of the logical interface to the kernel NIC interface corresponding to one of the member interfaces;

When removing a member interface from a logical interface, determine whether the kernel NIC interface of the removed member interface is mapped with the interface configuration. If so, delete the interface configuration of the kernel NIC interface corresponding to the member interface, and configure the interface configuration of the logical interface. Map to the corresponding kernel NIC interface of another member interface.

Further, the logical interface data communication method further includes:

When deleting the interface configuration of a logical interface, delete the interface configuration of the mapped kernel NIC interface.

Further, the logical interface data communication method further includes:

When deleting a logical interface, delete the interface configuration of the mapped kernel NIC interface.

The present application also proposes a logical interface data communication device, which is applied to a network device based on a data plane development kit DPDK. The logical interface data communication device includes:

The configuration module is used to create a logical interface and map the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface;

The self-communication module is used for receiving the data message accessing the logical interface itself, and sending the received data message to the mapped kernel network card interface; receiving the response message of the kernel network card interface, and sending it through the logical interface.

Optionally, the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface, and performs the following operations:

When there is no member interface under the logical interface, when the member interface is added, the interface configuration of the logical interface is mapped to the kernel NIC interface corresponding to the first member interface;

When removing a member interface from a logical interface, determine whether the removed member interface is the first member interface. If it is the first member interface, delete the interface configuration of the kernel NIC interface corresponding to the removed member interface. Map the interface configuration of the logical interface to the kernel NIC interface corresponding to the new first member interface.

Optionally, the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface, and performs the following operations:

When there are member interfaces under the logical interface, map the interface configuration of the logical interface to the kernel NIC interface corresponding to one of the member interfaces;

When removing a member interface from a logical interface, determine whether the kernel NIC interface of the removed member interface is mapped with the interface configuration. If so, delete the interface configuration of the kernel NIC interface corresponding to the member interface, and configure the interface configuration of the logical interface. Map to the corresponding kernel NIC interface of another member interface.

Further, the configuration module is also used for:

When deleting the interface configuration of a logical interface, delete the interface configuration of the mapped kernel NIC interface.

Further, the configuration module is also used for:

When deleting a logical interface, delete the interface configuration of the mapped kernel NIC interface.

A logical interface data communication method and device proposed in the present application, by mapping the IP address of the logical interface to the kernel network card interface corresponding to the member interface, so as to use the kernel protocol stack to process and respond to its own message, thereby improving the forwarding performance of the device. At the same time, it reduces the workload of its own communication protocol stack code adaptation and development, and improves product development efficiency and product stability. It reduces the huge investment in the development of dynamic routing entries for Layer 3 logical interfaces such as link aggregation interfaces and VLAN interfaces.

Description of drawings

FIG. 1 is a flowchart of a logical interface data communication method according to an embodiment of the present application;

FIG. 2 is a flowchart of a communication method for a link aggregation interface according to an embodiment of the present application;

3 is a schematic diagram of a network connection of a link aggregation interface according to an embodiment of the present application;

4 is a schematic diagram of a network connection of a VLAN interface according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a logical interface data communication apparatus according to an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

A logical interface data communication method and device provided by the present application are applied to a DPDK-based network device, and the logical interface on the network device communicates itself according to the method of the present application. In this application, the logical interface is described by taking the link aggregation interface and the VLAN interface as examples, and the same applies to other logical interfaces. Link Aggregation (English: LinkAggregation) is a computer network term that refers to the aggregation of multiple physical interfaces to form a logical interface. Each physical interface is a member interface in the logical interface to achieve outbound/inbound traffic throughput. In the load sharing of each member interface, the switch determines from which member interface the network packet is sent to the peer switch according to the interface load sharing policy configured by the user. When the switch detects that the link of one of the member interfaces is faulty, it stops sending packets on this interface, and recalculates the sending interface of the packets in the remaining links according to the load sharing policy. After the faulty interface recovers, it takes over again. Transceiver interface. Link aggregation is an important technology in increasing link bandwidth, realizing link transmission elasticity and engineering redundancy. Virtual LAN interface (VLAN interface) is a group of logical interfaces. These interfaces are not limited by physical location. They can be organized according to factors such as functions, departments, and applications, and communicate with each other as if they are in the same the same in the network segment. In the embodiments of the present application, each physical interface in the link aggregation interface or the VLAN interface is collectively referred to as a member interface. For a link aggregation interface, its member interfaces are all physical interfaces participating in the link aggregation; for a VLAN interface, its member interfaces are all physical interfaces in the same VLAN.

An embodiment of the present application, as shown in FIG. 1, provides a logical interface data communication method, including:

Step S110: Create a logical interface, and map the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface.

Currently, network devices that use DPDK, such as security admission control gateways, have corresponding KNI interfaces for each physical interface. However, for logical interfaces, there is no corresponding KNI interface. Whether it is a physical interface or a logical interface, after receiving a data packet, if it does not access itself, it forwards it. And if it is a data packet of the access interface itself, it is a data packet of its own communication. For its own communication data packets, the physical interface allows the KNI interface provided by the DPDK to allow the packet to be received from the user mode and then forwarded to the Linux protocol stack to realize its own communication, while the DPDK does not provide such a KNI interface for the logical interface. Therefore, the technical solution of the present application is to hope that the Linux protocol stack can also be used on the logical interface to realize the self-communication of the logical interface, without additionally developing and adapting the virtual network card driver carried by the logical interface.

Usually, when creating a logical interface, generally speaking, you can create a logical interface first, and then add member interfaces to the created logical interface. For example, create a link aggregation interface aggregateport1 on network device A, and then add the physical interface Ethernet1 and physical interface Ethernet2 of network device A to aggregateport1. For another example, create a VLAN interface VLAN10 on the network device A, and then add the physical interface Ethernet1 and the physical interface Ethernet2 of the network device A to the VLAN10. The created link aggregation interfaces aggregateport1 and VLAN10 are logical interfaces, and the physical interfaces Ethernet1 and Ethernet2 are member interfaces.

In the process of creating a logical interface, it is also necessary to configure the logical interface. The interface configuration of the logical interface usually includes the IP address, the interface status, and the maximum transmission unit (MTU) and so on. The interface state has two states: up and down. It should be noted that, the interface configuration of the logical interface may be configured after the logical interface is created, or may be configured after the member interface is added, which is not limited in this application.

In order to realize the self-communication of the logical interface by using the Linux protocol stack on the logical interface, the present application implements by mapping the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface.

In a specific example, mapping the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface includes: when there is no member interface under the logical interface, when the member interface starts to be added, the interface configuration of the logical interface is mapped to the first member interface. The kernel NIC corresponding to each member interface; when removing a member interface from a logical interface, determine whether the removed member interface is the first member interface, and if it is the first member interface, delete the removed member interface The interface configuration of the corresponding kernel NIC interface maps the interface configuration of the logical interface to the kernel NIC interface corresponding to the new first member interface.

Specifically, after the logical interface is created, the interface configuration of the logical interface is configured. At this time, there is no member interface under the logical interface, and the interface configuration of the logical interface is saved locally. Then configure the member interface for the logical interface, and map the interface configuration of the logical interface to the kernel NIC interface corresponding to the first member interface when the first member interface is added. That is to say, after the first member interface is added, the communication data packets of the access logical interface itself can be transferred to the Linux protocol stack for processing through the kernel network card interface corresponding to the first member interface. When subsequent member interfaces are rejoined, no additional configuration is required.

Similarly, when a member interface is removed from a logical interface, if the first member interface is removed, since the first member interface is removed, the corresponding kernel NIC interface will no longer be able to provide services. In this case, the first member interface needs to be deleted. Interface configuration of the kernel NIC interface corresponding to each member interface. The first member interface under the logical interface is searched again, and after the new first member interface is found, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the new first member interface. To facilitate judging who is the new first member interface, you can sequentially number the member interfaces added to the logical interface, and determine the new first member interface according to the number, which is not repeated here.

In this embodiment, when the interface configuration of the logical interface is deleted, the interface configuration of the mapped kernel network card interface is deleted; when the logical interface is deleted, the interface configuration of the mapped kernel network card interface is deleted.

Specifically, if the interface configuration of the logical interface is deleted, the interface configuration of the kernel network card interface mapped to the first member interface is correspondingly deleted. If the logical interface is deleted, the interface configuration of the kernel network card interface mapped by the first member interface is also deleted correspondingly.

In another specific example, mapping the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface includes: when there are member interfaces under the logical interface, mapping the interface configuration of the logical interface to the corresponding one of the member interfaces When a member interface is removed from a logical interface, determine whether the kernel NIC interface of the removed member interface is mapped with an interface configuration, if so, delete the interface configuration of the kernel NIC interface corresponding to the member interface, and set the The interface configuration of a logical interface is mapped to the corresponding kernel NIC interface of another member interface.

Specifically, after the logical interface is created, the member interface under the logical interface is configured, and then the corresponding interface configuration is configured for the logical interface. If it is found that there is already a member interface, the interface configuration needs to be mapped to the kernel NIC interface corresponding to a member interface. . At this time, to select the member interface for mapping, you can select the first member interface according to the order number of the member joining, or you can select a member interface arbitrarily, or select the member interface according to the priority of the member interface. The priority of the member interface may be determined according to the available resources of the member interface, for example, according to its remaining bandwidth. The higher the remaining bandwidth, the higher the priority. Or determine the priority according to the number of existing users on the member interface. The lower the number of users, the higher the priority. This example does not restrict how to select member interfaces.

Correspondingly, when removing a member interface, it is judged whether the kernel network card interface of the removed member interface is mapped with the interface configuration, if so, delete the interface configuration of the kernel network card interface corresponding to the member interface, and configure the interface configuration of the logical interface. Map to the kernel NIC interface corresponding to a newly selected member interface.

In this embodiment, when the interface configuration of the logical interface is deleted, the interface configuration of the mapped kernel network card interface is deleted; when the logical interface is deleted, the interface configuration of the mapped kernel network card interface is deleted.

Specifically, if the interface configuration of the logical interface is deleted, the interface configuration of the kernel network card interface mapped by the member interface is correspondingly deleted. If the logical interface is deleted, the interface configuration of the kernel NIC interface mapped by the member interface is correspondingly deleted, and details are not repeated here.

Step S120: Receive a data packet accessing the logical interface itself, and send the received data packet to the mapped kernel network card interface.

In the previous steps, the interface configuration of the logical interface has been mapped to the kernel NIC interface corresponding to a member interface. Therefore, when the logical interface receives a data packet that accesses itself, the destination address of the data packet is the address of the logical interface. , the kernel NIC interface will forward the data packet to the Linux protocol stack for processing.

Step S130: Receive a response message from the kernel network card interface, and send it through the logical interface.

The Linux protocol stack of the network device processes the received data packet, and then responds. The response packet is re-sent to the logical interface through the kernel network card interface, matches the established forwarding entry, and is sent out through the logical interface. The destination address is the source address of the data packet that originally accessed itself.

In another embodiment of the present application, this embodiment can be combined with each optional solution in one or more of the above embodiments, and a link aggregation interface is used as an example to describe a logical interface data communication method of the present application in detail, as shown in FIG. 2 . shown, including:

Step S201 , creating a link aggregation interface, and configuring an IP address of the link aggregation.

The interface configuration of the link aggregation interface in this embodiment is described by taking an IP address as an example. For example, create a link aggregation interface aggregateport1 on network device A, and then add the physical interface Ethernet1 and physical interface Ethernet2 of network device A to aggregateport1. Configure an IP address for the link aggregation interface aggregateport1. For example, the configured IP address is 192.168.1.110.

Step S202, judging whether there is a member interface under the link aggregation interface, if there is no member interface, then save the IP address of the link aggregation interface locally, and if there is a member interface, map the IP address of the link aggregation interface to the first link aggregation interface. The kernel NIC interface corresponding to the member interface.

Specifically, this embodiment first determines whether there is a member interface under the link aggregation interface, and if there is no member interface, the IP address of the link aggregation interface is stored locally. If it is found subsequently that a member interface is added to the link aggregation interface, the IP address of the link aggregation interface is mapped to the kernel network card interface corresponding to the first member interface. For example, if Ethernet1 is the first member interface added, the IP address 192.168.1.110 is mapped to the corresponding kernel NIC interface of Ethernet1.

If there are member interfaces under the link aggregation interface, the IP address of the link aggregation interface is mapped to the kernel network card interface corresponding to the first member interface according to the order number of the member interfaces. For example, if Ethernet1 is the first member interface added, the IP address 192.168.1.110 is mapped to the corresponding kernel NIC interface of Ethernet1.

Step S203, when removing the member interface under the link aggregation interface, determine whether the removed member interface is the first member interface, and if it is the first member interface, then delete the interface configuration of the kernel network card interface corresponding to the removed member interface, Map the interface configuration of the logical interface to the kernel NIC interface corresponding to the new first member interface.

If the member interface is removed from the link aggregation interface, for example, the member interface Ethernet1 is removed from the link aggregation interface aggregateport1, since the member interface Ethernet1 is the first member interface, the corresponding kernel NIC interface maps the IP of the link aggregation interface. The address is 192.168.1.110. In this case, you need to delete the interface configuration of the kernel NIC interface corresponding to the member interface Ethernet1. Find the new first member interface in the member interfaces under the link aggregation interface again. Assuming that member interface Ethernet2 is the first member interface, map the IP address 192.168.1.110 of the link aggregation interface aggregateport1 to the corresponding one of Ethernet2. Kernel NIC interface. At this time, the IP address of the link aggregation interface is always mapped to the kernel NIC interface corresponding to a member interface, which can realize the communication of the link aggregation interface itself.

It is easy to understand that, if the removed member interface is not the first member interface, or the kernel NIC interface corresponding to the removed member interface is not mapped to the IP address of the link aggregation interface, no processing is required.

In particular, if there is no member interface under the link aggregation interface after the member interface is removed, the IP address configured on the link aggregation interface is saved locally. At this time, there is no mapped kernel NIC interface, and the link aggregation interface cannot be implemented. self-communication.

When the IP address of the link interface is deleted, or the link aggregation interface is deleted, the IP address of the kernel network card interface mapped by the first member interface is correspondingly deleted.

Step S204: Receive a data packet accessing the link aggregation interface itself, and send the received data packet to the kernel network card interface corresponding to the first mapped member interface.

In this embodiment, the kernel network card interface corresponding to the first member interface Ethernet1 maps the IP address of the link aggregation interface 192.168.1.110. Therefore, when the destination IP address of the data packet received by the link aggregation interface is 192.168.1.110, it is Self-communication data packets to the link aggregation interface. Since the kernel network card interface corresponding to the first member interface Ethernet1 maps the IP address 192.168.1.110 of the link aggregation interface, the data packet is sent to the kernel network card interface corresponding to the first member interface Ethernet1, so the data packet is forwarded to Linux The protocol stack processes the data packets, and the Linux protocol stack returns a response packet after processing the data packets.

Step S205: Receive a response packet returned by the kernel network card interface corresponding to the first member interface, and send it through the link aggregation interface.

After the Linux protocol stack processes the data packet, it returns a response packet. The response packet is forwarded by the link aggregation interface, and the forwarded destination address is the original data packet (the data packet accessing the link aggregation interface itself) source IP address.

For example, the destination address of the data packet accessing the link aggregation interface itself is 192.168.1.110, and the source IP address is 192.168.220. Then the destination address of the response message is 192.168.220, thus successfully responding to the self-communication accessing itself.

It is easy to understand that the embodiment in FIG. 2 is described by taking a link aggregation interface as an example, and the same applies to other logical interfaces, such as VLAN interfaces, and will not be repeated here.

The present application provides a logical interface data communication method. By mapping the IP address of the logical interface to the kernel network card interface corresponding to the member interface, the kernel protocol stack is used to process and respond to its own message, thereby improving the forwarding performance of the device. At the same time, it reduces the workload of its own communication protocol stack code adaptation and development, and improves product development efficiency and product stability. It reduces the huge investment in the development of dynamic routing entries for Layer 3 logical interfaces such as link aggregation interfaces and VLAN interfaces.

Fig. 3 is an embodiment of the communication of the link aggregation interface itself. In this embodiment, the three physical interfaces of the security admission control gateways FW2 and FW3 applying DPDK are added to a link aggregation interface in the form of member interfaces, And configure their own IP addresses for the link aggregation interfaces of FW2 and FW3 respectively. Since FW2 and FW3 do not have an integrated protocol stack, the communication from network traffic to themselves is carried on the built-in Linux system. The IP address of the configured link aggregation interface is The address is also synchronously mapped to the kernel NIC interface corresponding to one of the three physical interfaces, which is generally the kernel NIC interface corresponding to the first member interface of the link aggregation interface.

Taking FW2 as an example, the three physical interfaces Ethernet1, Ethernet2, and Ethernet3 are added to the link aggregation interface as member interfaces. Assume that the IP address of the link aggregation interface of FW2 is IP1, and the mapped kernel NIC interface is the one corresponding to the physical interface Ethernet1. Kernel NIC interface KNI1.

When removing a member interface, if the physical interface Ethernet1 is removed, delete the IP address mapped by KNI1, and remap the kernel NIC interface, for example, map it to the kernel NIC interface KNI2 corresponding to the physical interface Ethernet2.

When deleting the IP address of the link aggregation interface, or when deleting the link aggregation interface, delete the IP address mapped by KNI1.

All data packets communicated between the PC and the FW2 link aggregation interface are sent to the KNI1 interface, and the Linux protocol stack responds to the packet exchange. Other data packets forwarded through the link aggregation interface are normally forwarded by the link aggregation interface.

Figure 4 is an embodiment of VLAN interface self-communication. In this embodiment, a VLAN interface is created on the security admission control gateway FW1 that applies DPDK, and FW1 selects physical interfaces Ethernet4, Ethernet5, and Ethernet6 to join the VLAN, and connects PC1 and PC2 respectively. , PC3. When an IP address is configured on a VLAN interface, the IP address is synchronously mapped to the kernel NIC interface corresponding to a physical interface. You can choose to map it to the kernel NIC interface corresponding to the first physical interface added to the VLAN among the physical interfaces Ethernet4, Ethernet5, and Ethernet6. Assume that the IP address of the VLAN interface on FW1 is IP10, and the mapped kernel NIC interface is the kernel NIC interface KNI4 corresponding to the physical interface Ethernet4.

If one of the physical interfaces Ethernet4, Ethernet5, and Ethernet6 is removed or the working status becomes down, it is necessary to detect and determine whether to remap the kernel NIC interface. For example, if Ethernet4 is removed, the IP address mapped by KNI4 should be deleted, and the interface of the kernel network card should be remapped, such as mapping to the interface KNI5 of the kernel network card corresponding to the physical interface Ethernet5.

When the IP address of the VLAN interface is modified or deleted, the IP address of the mapped kernel NIC interface needs to be deleted, for example, the IP address mapped by KNI4 needs to be deleted.

PC1, PC2, PC3 are configured with the IP address of the VLAN interface on the same network segment. When PC1, PC2, PC3 communicates with the VLAN interface, they are all sent to the KNI4 interface, and the Linux protocol stack responds to the message exchange. Other data packets forwarded by the VLAN interface are normally forwarded by the VLAN interface.

Another embodiment of the present application, as shown in FIG. 5 , further provides a logical interface data communication device, which is applied to a network device based on the data plane development kit DPDK, and the logical interface data communication device includes:

The configuration module is used to create a logical interface and map the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface;

The self-communication module is used for receiving the data message accessing the logical interface itself, and sending the received data message to the mapped kernel network card interface; receiving the response message of the kernel network card interface, and sending it through the logical interface.

For the specific limitation of the logical interface data communication apparatus, reference may be made to the above limitation on the logical interface data communication method, which will not be repeated here. Each module in the above-mentioned logical interface data communication device may be implemented in whole or in part by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

Corresponding to the above logical interface data communication method, optionally, the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface, and performs the following operations:

When there is no member interface under the logical interface, when the member interface is added, the interface configuration of the logical interface is mapped to the kernel NIC interface corresponding to the first member interface;

When removing a member interface from a logical interface, determine whether the removed member interface is the first member interface. If it is the first member interface, delete the interface configuration of the kernel NIC interface corresponding to the removed member interface. Map the interface configuration of the logical interface to the kernel NIC interface corresponding to the new first member interface.

Optionally, the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface, and performs the following operations:

When there are member interfaces under the logical interface, map the interface configuration of the logical interface to the kernel NIC interface corresponding to one of the member interfaces;

When removing a member interface from a logical interface, determine whether the kernel NIC interface of the removed member interface is mapped with the interface configuration. If so, delete the interface configuration of the kernel NIC interface corresponding to the member interface, and configure the interface configuration of the logical interface. Map to the corresponding kernel NIC interface of another member interface.

Corresponding to the above-mentioned logical interface data communication method, the configuration module described in this application is also used for:

When deleting the interface configuration of a logical interface, delete the interface configuration of the mapped kernel NIC interface.

Corresponding to the above-mentioned logical interface data communication method, the configuration module described in this application is also used for:

When deleting a logical interface, delete the interface configuration of the mapped kernel NIC interface.

The above-mentioned embodiments only represent several embodiments of the present application, and the descriptions thereof are specific and detailed, but should not be construed as a limitation on the scope of the invention patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims (10)

1. A logic interface data communication method is applied to network equipment based on a data plane development kit DPDK, and is characterized in that the logic interface data communication method comprises the following steps:

creating a logic interface, and mapping the interface configuration of the logic interface to a kernel network card interface corresponding to a member interface;

receiving a data message for accessing the logic interface, and sending the received data message to a mapped kernel network card interface;

and receiving a response message of the kernel network card interface, and sending the response message through the logic interface.

2. The logical interface data communication method according to claim 1, wherein mapping the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface comprises:

no member interface exists under the logic interface, and when the member interface is added, the interface configuration of the logic interface is mapped to the kernel network card interface corresponding to the first member interface;

and when the member interface is removed under the logic interface, judging whether the removed member interface is the first member interface, if so, deleting the interface configuration of the kernel network card interface corresponding to the removed member interface, and mapping the interface configuration of the logic interface to the new kernel network card interface corresponding to the first member interface.

3. The logical interface data communication method according to claim 1, wherein mapping the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface comprises:

when a member interface exists under the logical interface, mapping the interface configuration of the logical interface to a kernel network card interface corresponding to one member interface;

when the member interface is removed under the logic interface, judging whether the kernel network card interface of the removed member interface maps the interface configuration, if so, deleting the interface configuration of the kernel network card interface corresponding to the member interface, and mapping the interface configuration of the logic interface to the kernel network card interface corresponding to another member interface.

4. The logical interface data communication method of claim 1, further comprising:

and when the interface configuration of the logical interface is deleted, deleting the interface configuration of the mapped kernel network card interface.

5. The logical interface data communication method of claim 1, further comprising:

and when the logical interface is deleted, deleting the interface configuration of the mapped kernel network card interface.

6. A logic interface data communication device is applied to network equipment based on a data plane development kit DPDK, and is characterized by comprising:

the configuration module is used for creating a logic interface and mapping the interface configuration of the logic interface to a kernel network card interface corresponding to a member interface;

the self communication module is used for receiving a data message for accessing the logic interface and sending the received data message to the mapped kernel network card interface; and receiving a response message of the kernel network card interface, and sending the response message through the logic interface.

7. The logical interface data communication apparatus according to claim 6, wherein the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to one member interface, and performs the following operations:

no member interface exists under the logic interface, and when the member interface is added, the interface configuration of the logic interface is mapped to the kernel network card interface corresponding to the first member interface;

and when the member interface is removed under the logic interface, judging whether the removed member interface is the first member interface, if so, deleting the interface configuration of the kernel network card interface corresponding to the removed member interface, and mapping the interface configuration of the logic interface to the new kernel network card interface corresponding to the first member interface.

8. The logical interface data communication apparatus according to claim 6, wherein the configuration module maps the interface configuration of the logical interface to a kernel network card interface corresponding to one member interface, and performs the following operations:

when the member interface exists under the logic interface, the interface configuration of the logic interface is mapped to the inner core network card interface corresponding to one member interface;

when the member interface is removed under the logic interface, judging whether the kernel network card interface of the removed member interface maps the interface configuration, if so, deleting the interface configuration of the kernel network card interface corresponding to the member interface, and mapping the interface configuration of the logic interface to the kernel network card interface corresponding to another member interface.

9. The logical interface data communication apparatus of claim 6, wherein the configuration module is further to:

and when the interface configuration of the logical interface is deleted, deleting the interface configuration of the mapped kernel network card interface.

10. The logical interface data communication apparatus of claim 6, wherein the configuration module is further to:

and when the logical interface is deleted, deleting the interface configuration of the mapped kernel network card interface.

Images