CN114615187B - Logic interface data communication method and device - Google Patents

Abstract

The invention discloses a logic interface data communication method and a logic interface data communication device, wherein interface configuration of a logic interface is mapped to a kernel network card interface corresponding to a member interface, when a data message accessing the logic interface is received, the received data message is sent to the mapped kernel network card interface, a response message of the kernel network card interface is received, and the response message is sent through the logic interface. Therefore, the kernel protocol stack is adopted to process and respond to the message, and the forwarding performance of the equipment is improved. Meanwhile, the workload of self communication protocol stack code adaptation and development is reduced, and the production development efficiency and the product stability are improved. The invention reduces the huge investment for developing dynamic routing list items of three-layer logic interfaces such as a link aggregation interface, a VLAN interface and the like.

Description

A logical interface data communication method and device

Technical Field

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

Background technique

The Data Plane Development Kit (DPDK) is mainly based on the Linux system. It is a collection of function libraries and drivers for fast data packet processing, which can greatly improve data processing performance and throughput, and improve the work efficiency of data plane applications. DPDK provides the kernel network card interface KNI (Kernel NIC Interface) to facilitate communication between DPDK applications and the Linux kernel. This interface allows packets to be received from user mode and then forwarded to the Linux protocol stack, that is, allowing 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, ifconfig, tcpdump) to manage the DPDK interface and communicate with itself.

However, for network devices that use DPDK, such as security access control gateways, DPDK does not provide such KNI interface library functions to manage and communicate with logical interfaces on the device, such as link aggregation interfaces, VLAN interfaces, and tunnel interfaces. Therefore, if you want to manage and communicate with logical interfaces, you must transplant and integrate your own protocol stack to manage the interface.

However, due to the complexity of the kernel protocol stack, redeveloping the virtual network card driver carried by the adaptation logic interface is a large workload and time-consuming.

Summary of the invention

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

In order to achieve the above purpose, the technical solution of this application is as follows:

A logical interface data communication method is 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 network card interface corresponding to a member interface;

Receive data packets for accessing the logical interface itself, and send the received data packets 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, mapping the interface configuration of the logical interface to a kernel network card interface corresponding to a member interface includes:

If there is no member interface under the logical interface, when adding member interfaces, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the first member interface;

When removing a member interface under 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 network card interface corresponding to the removed member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to the new first member interface.

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

When there are member interfaces under the logical interface, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to one of the member interfaces;

When removing a member interface under a logical interface, determine whether the kernel network card interface of the removed member interface has mapped the interface configuration. If so, delete the interface configuration of the kernel network card interface corresponding to the member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to another member interface.

Furthermore, the logical interface data communication method further includes:

When deleting the interface configuration of a logical interface, the interface configuration of the mapped kernel network card interface is deleted.

Furthermore, the logical interface data communication method further includes:

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

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, and the logical interface data communication device includes:

A 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 to receive data packets accessing the logical interface itself, and send the received data packets to the mapped kernel network card interface; receive the response packets from the kernel network card interface, and send them 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:

If there is no member interface under the logical interface, when adding member interfaces, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the first member interface;

When removing a member interface under 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 network card interface corresponding to the removed member interface, and map the interface configuration of the logical interface to the kernel network card 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, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to one of the member interfaces;

When removing a member interface under a logical interface, determine whether the kernel network card interface of the removed member interface has mapped the interface configuration. If so, delete the interface configuration of the kernel network card interface corresponding to the member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to another member interface.

Furthermore, the configuration module is also used to:

When deleting the interface configuration of a logical interface, the interface configuration of the mapped kernel network card interface is deleted.

Furthermore, the configuration module is also used to:

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

The present application proposes a method and device for logical interface data communication, which improves the forwarding performance of the device 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. At the same time, it reduces the workload of its own communication protocol stack code adaptation and development, improves product development efficiency and product stability, and 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.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a logical interface data communication method according to an embodiment of the present application;

FIG2 is a flow chart of a link aggregation interface communication method according to an embodiment of the present application;

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

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

FIG5 is a schematic diagram of the structure of a logical interface data communication device according to an embodiment of the present application.

Detailed ways

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

The present application provides a logical interface data communication method and device, which is applied to a network device based on DPDK. The logical interface on the network device communicates itself according to the method of the present application. In the present application, the logical interface is explained by taking the link aggregation interface and the VLAN interface as examples, which is also applicable to other logical interfaces. Link aggregation (English: LinkAggregation) is a computer network term, which 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 load sharing of the inbound/outbound traffic throughput among the member interfaces. The switch determines which member interface the network packet is sent from to the switch at the opposite end according to the interface load sharing strategy configured by the user. When the switch detects that the link of one of the member interfaces fails, it stops sending packets on this interface, and recalculates the sending interface of the message in the remaining links according to the load sharing strategy. After the failed interface is restored, it serves as the sending and receiving interface again. Link aggregation is a very important technology in increasing link bandwidth, achieving link transmission elasticity and engineering redundancy. A virtual local area network interface (VLAN interface) is a group of logical interfaces that are not restricted by physical locations and can be organized based on functions, departments, and applications. The communication between them is as if they are in the same network segment. In the embodiments of the present application, each physical interface in a link aggregation interface or a VLAN interface is collectively referred to as a member interface. For a link aggregation interface, its member interfaces are the physical interfaces participating in the link aggregation; similarly, for a VLAN interface, its member interfaces are the physical interfaces in the same VLAN.

An embodiment of the present application, as shown in FIG1 , 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 access control gateways, etc., have corresponding KNI interfaces for each physical interface on them. However, no corresponding KNI interface is provided for logical interfaces. Whether it is a physical interface or a logical interface, if it does not access itself, it will forward the data packet after receiving it. If it is a data packet for accessing the interface itself, it is its own communication data packet. For its own communication data packet, the physical interface allows the message to be received from the user state and then forwarded to the Linux protocol stack to realize its own communication through the KNI interface provided by DPDK, while DPDK does not provide such a KNI interface for the logical interface. Therefore, the technical solution of the present application is to hope to use the Linux protocol stack on the logical interface to realize the self-communication of the logical interface, without the need to develop additional virtual network card drivers adapted to the logical interface.

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

During the creation of a logical interface, the logical interface also needs to be configured. The interface configuration of the logical interface usually includes the IP address, interface status, maximum transmission unit MTU, etc. The interface status has two states: up and down. It should be noted that the interface configuration of the logical interface can be configured after the logical interface is created, or it can be configured after the member interface is added. This application does not limit this.

In order to utilize the Linux protocol stack on the logical interface to realize the communication of the logical interface itself, the present application adopts the method of mapping the interface configuration of the logical interface to the kernel network card interface corresponding to a member interface.

In a specific example, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to a member interface, including: when there is no member interface under the logical interface and member interfaces are started to be added, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the first member interface; when a member interface is removed under the logical interface, it is determined whether the removed member interface is the first member interface. If it is the first member interface, the interface configuration of the kernel network card interface corresponding to the removed member interface is deleted, and the interface configuration of the logical interface is mapped to the kernel network card 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 the member interface is configured for the logical interface. When the first member interface is added, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the first member interface. In other words, after the first member interface is added, it is possible to transfer the communication data packets accessing the logical interface itself to the Linux protocol stack for processing through the kernel network card interface corresponding to the first member interface. When subsequent member interfaces are added, no additional configuration is required.

Similarly, when removing a member interface under a logical interface, if the first member interface is removed, since the first member interface is removed, its corresponding kernel network card interface will no longer be able to provide services. At this time, it is necessary to delete the interface configuration of the kernel network card interface corresponding to the first member interface. Re-search for the first member interface under the logical interface, and after finding the new first member interface, map the interface configuration of the logical interface to the kernel network card interface corresponding to the new first member interface. In order to facilitate the determination of who is the new first member interface, the member interfaces added to the logical interface can be numbered sequentially, and the new first member interface can be determined based on the numbering. This will not be repeated here.

In this embodiment, when deleting the interface configuration of the logical interface, the interface configuration of the mapped kernel network card interface is deleted; when deleting the logical interface, 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 first member interface is also deleted accordingly. If the logical interface is deleted, the interface configuration of the kernel network card interface mapped by the first member interface is also deleted accordingly.

In another specific example, the interface configuration of the logical interface is mapped to a kernel network card interface corresponding to a member interface, including: when there is a member interface under the logical interface, mapping the interface configuration of the logical interface to the kernel network card interface corresponding to one of the member interfaces; when removing a member interface under the logical interface, determining whether the kernel network card interface of the removed member interface has mapped 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 logical interface to the kernel network card interface corresponding to another member interface.

Specifically, after the logical interface is created, the member interfaces under the logical interface are configured. Thereafter, the corresponding interface configuration is configured for the logical interface. If a member interface already exists, the interface configuration needs to be mapped to the kernel network card interface corresponding to a member interface. At this time, the member interface to be mapped can be selected based on the order number of the member joining, or a member interface can be selected arbitrarily, or based on the priority of the member interface. The priority of the member interface can be determined based on the available resources of the member interface, for example, based on its remaining bandwidth. The higher the remaining bandwidth, the higher its priority. Alternatively, the priority can be determined based on the number of existing users on the member interface. The fewer the number of users, the higher the priority. This example does not restrict how to select the member interface.

Correspondingly, when removing a member interface, determine whether the kernel network card interface of the removed member interface has mapped the interface configuration. If so, delete the interface configuration of the kernel network card interface corresponding to the member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to a newly selected member interface.

In this embodiment, when deleting the interface configuration of the logical interface, the interface configuration of the mapped kernel network card interface is deleted; when deleting the logical interface, 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 also deleted accordingly. If the logical interface is deleted, the interface configuration of the kernel network card interface mapped by the member interface is also deleted accordingly, which will not be repeated here.

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

In the previous steps, the interface configuration of the logical interface has been mapped to the kernel network card interface corresponding to a member interface. Therefore, when the logical interface receives a data packet accessing itself, the destination address of this data packet is the address of the logical interface, and the kernel network card 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.

After processing the received data message, the Linux protocol stack of the network device responds. The response message is re-sent to the logical interface through the kernel network card interface, matches the established forwarding table entry, and is sent out through the logical interface. The destination address of the response message is the source address of the original data message accessing itself.

Another embodiment of the present application, which can be combined with each optional solution in one or more of the above embodiments, takes a link aggregation interface as an example to describe a logical interface data communication method of the present application in detail, as shown in FIG2, including:

Step S201: Create a link aggregation interface and configure the IP address of the link aggregation.

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

Step S202: determine whether there is a member interface under the link aggregation interface. If there is no member interface, save the IP address of the link aggregation interface locally. If there is a member interface, map the IP address of the link aggregation interface to the kernel network card interface corresponding to the first member interface.

Specifically, this embodiment first determines whether there is a member interface under the link aggregation interface. If there is no member interface, the IP address of the link aggregation interface is saved locally. If it is found that a member interface begins to be 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, Ethernet1 is the first member interface to be added, and the IP address 192.168.1.110 is mapped to the kernel network card interface corresponding to Ethernet1.

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

Step S203: When removing a member interface under the link aggregation 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 network card interface corresponding to the removed member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to the new first member interface.

If you remove a member interface from a link aggregation interface, for example, remove member interface Ethernet1 from link aggregation interface aggregateport1, since member interface Ethernet1 is the first member interface, its corresponding kernel NIC interface maps the IP address 192.168.1.110 of the link aggregation interface. At this time, you need to delete the interface configuration of the kernel NIC interface corresponding to member interface Ethernet1. Find a new first member interface in the member interfaces under the link aggregation interface again. Assuming that member interface Ethernet2 is the first member interface at this time, map the IP address 192.168.1.110 of link aggregation interface aggregateport1 to the kernel NIC interface corresponding to Ethernet2. At this time, the IP address of the link aggregation interface is always mapped to the kernel NIC interface corresponding to a member interface, so that the link aggregation interface can communicate with itself.

It is easy to understand that if the removed member interface is not the first member interface, or the kernel network card 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 for the link aggregation interface is saved locally. At this time, there is no mapped kernel network card interface, and the link aggregation interface cannot achieve its own 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 also deleted accordingly.

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

In this embodiment, 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. Therefore, when the destination IP address of the data message received by the link aggregation interface is 192.168.1.110, it is the communication data message of the link aggregation interface itself. 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 message is sent to the kernel network card interface corresponding to the first member interface Ethernet1, and the data message is forwarded to the Linux protocol stack for processing. After the Linux protocol stack processes the data message, it returns a response message.

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

After processing the data message, the Linux protocol stack returns a response message, which is forwarded by the link aggregation interface, and the forwarding destination address is the source IP address of the original data message (the data message accessing the link aggregation interface itself).

For example, the destination address of the data message 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, thereby successfully responding to the communication accessing itself.

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

The present application discloses a logical interface data communication method, which improves the forwarding performance of the device by mapping the IP address of the logical interface to the kernel network card interface corresponding to the member interface, thereby using the kernel protocol stack to process and respond to its own message. At the same time, it reduces the workload of its own communication protocol stack code adaptation and development, improves product development efficiency and product stability, and reduces the huge investment in the development of dynamic routing table items of three-layer logical interfaces such as link aggregation interfaces and VLAN interfaces.

Figure 3 is an embodiment of the link aggregation interface's own communication. In this embodiment, the three physical interfaces of the DPDK-enabled security access control gateways FW2 and FW3 are added to a link aggregation interface as member interfaces, and the link aggregation interfaces of FW2 and FW3 are configured with their own IP addresses. Since FW2 and FW3 do not have an integrated protocol stack, the communication from network traffic to themselves is carried on their own Linux system. The IP address of the configured link aggregation interface is also synchronously mapped to the kernel network card interface corresponding to one of the three physical interfaces, generally the kernel network card 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 FW2 link aggregation interface is IP1, and the mapped kernel NIC interface is the kernel NIC interface KNI1 corresponding to the physical interface Ethernet1.

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

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

All data packets communicated between the PC and FW2 link aggregation interface are sent to the KNI1 interface, and the Linux protocol stack responds to the message interaction. Other data packets forwarded by the link aggregation interface are forwarded normally 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 secure access control gateway FW1 that uses DPDK. FW1 selects physical interfaces Ethernet4, Ethernet5, and Ethernet6 to join the VLAN and connects PC1, PC2, and PC3 respectively. When the VLAN interface is configured with an IP address, the IP address is synchronously mapped to the kernel network card interface corresponding to a physical interface. You can choose to map it to the kernel network card 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 network card interface is the kernel network card interface KNI4 corresponding to the physical interface Ethernet4.

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

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

PC1, PC2, PC3 are configured with IP addresses in the same network segment as the VLAN interface. When PC1, PC2, PC3 communicate with the VLAN interface, all messages are sent to the KNI4 interface, and the Linux protocol stack responds to the message interaction. Other data messages forwarded by the VLAN interface are forwarded normally 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 a data plane development kit DPDK, and the logical interface data communication device includes:

A 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 to receive data packets accessing the logical interface itself, and send the received data packets to the mapped kernel network card interface; receive the response packets from the kernel network card interface, and send them through the logical interface.

For the specific definition of the logical interface data communication device, please refer to the definition of the logical interface data communication method above, which will not be repeated here. Each module in the above-mentioned logical interface data communication device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of 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:

If there is no member interface under the logical interface, when adding member interfaces, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to the first member interface;

When removing a member interface under 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 network card interface corresponding to the removed member interface, and map the interface configuration of the logical interface to the kernel network card 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, the interface configuration of the logical interface is mapped to the kernel network card interface corresponding to one of the member interfaces;

When removing a member interface under a logical interface, determine whether the kernel network card interface of the removed member interface has mapped the interface configuration. If so, delete the interface configuration of the kernel network card interface corresponding to the member interface, and map the interface configuration of the logical interface to the kernel network card interface corresponding to 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, the interface configuration of the mapped kernel network card interface is deleted.

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, the interface configuration of the mapped kernel NIC interface is deleted.

The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims (10)

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

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 accessing the logic interface, and sending the received data message to a mapped kernel network card interface;

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

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

when a member interface is added under the logic interface, mapping the interface configuration of the logic interface to a kernel network card interface corresponding to the first member interface;

When removing the member interface 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 kernel network card interface corresponding to the new first member interface.

3. The method for data communication of a logical interface according to claim 1, wherein mapping the interface configuration of the logical interface to the kernel network card interface corresponding to one 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 removing member interfaces under the logic interfaces, judging whether the kernel network card interfaces of the removed member interfaces are mapped with interface configurations, if so, deleting the interface configurations of the kernel network card interfaces corresponding to the member interfaces, and mapping the interface configurations of the logic interfaces to the kernel network card interfaces corresponding to the other member interfaces.

4. The logical interface data communication method according to claim 1, wherein the logical interface data communication method further comprises:

and deleting the interface configuration of the mapped kernel network card interface when deleting the interface configuration of the logic interface.

5. The logical interface data communication method according to claim 1, wherein the logical interface data communication method further comprises:

and deleting the interface configuration of the mapped kernel network card interface when deleting the logic interface.

6. A logical interface data communication apparatus for use in a network device that develops a suite DPDK based on a data plane, the logical interface data communication apparatus 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 one member interface;

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

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

when a member interface is added under the logic interface, mapping the interface configuration of the logic interface to a kernel network card interface corresponding to the first member interface;

When removing the member interface 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 kernel network card interface corresponding to the new first member interface.

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

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 removing member interfaces under the logic interfaces, judging whether the kernel network card interfaces of the removed member interfaces are mapped with interface configurations, if so, deleting the interface configurations of the kernel network card interfaces corresponding to the member interfaces, and mapping the interface configurations of the logic interfaces to the kernel network card interfaces corresponding to the other member interfaces.

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

and deleting the interface configuration of the mapped kernel network card interface when deleting the interface configuration of the logic interface.

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

and deleting the interface configuration of the mapped kernel network card interface when deleting the logic interface.