Method and device for upgrading OVS-DPDK process

By switching the binding relationship between the network interface and the OVS-DPDK process when upgrading the OVS-DPDK process, the connection interruption caused by the reset of the network interface during the upgrade process is solved, ensuring that the traffic is forwarded normally.

CN118945053AInactive Publication Date: 2024-11-12NEW H3C TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202410986508.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-12
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

When upgrading the OVS-DPDK process, the existing technology needs to restart vswitchd, resulting in a reset of the network interface and causing the network connection to be interrupted.

Method used

By starting the target OVS-DPDK process, synchronize the configuration information of the original process, unbind the network interface and the PMD driver relationship, exit the original process, and avoid resetting the network interface.

Benefits of technology

It is implemented that when upgrading the OVS-DPDK process, the network interface does not need to be reset, and non-first packet traffic can pass normally, avoiding network connection interruption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945053A_ABST
    Figure CN118945053A_ABST
Patent Text Reader

Abstract

The invention provides a method and device for upgrading an OVS-DPDK process. The method comprises the following steps: starting a target OVS-DPDK process; the configuration information of the original OVS-DPDK process is synchronized with the target OVS-DPDK process; releasing the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establishing the binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; and exiting from the original OVS-DPDK process.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and more particularly to a method and device for upgrading an OVS-DPDK process. Background Art

[0002] With the rapid development of data centers, communication capabilities and computing capabilities have become two important development directions in data center infrastructure. As network transmission bandwidth increases, the computing resources of data centers are occupied by increasingly complex infrastructure operations, causing business processing to encounter bottlenecks. In order to cope with the exponential growth of data volume and complexity in data centers, DPU (Data Processing Unit) network cards came into being.

[0003] In the growing data center network, the requirements for processing complex data and processing traffic performance are increasing. As one of the infrastructures of the data center, OVS (Open vSwitch) introduces the DPDK (DataPlane Development Kit) architecture to improve forwarding performance. However, while OVS-DPDK greatly improves forwarding performance, due to the limitations of DPDK use, the higher the forwarding demand, the higher the CPU and memory usage, which further aggravates the shortage of computing resources; thus, the combination of OVS-DPDK and DPU network card has become one of the typical application scenarios of DPU network card. The fast path and slow path of OVS-DPDK (Data Plane Development Kit) are integrated in the vswitchd (Virtual Switch Daemon) module. vswitchd combined with PMD (Poll Mode Driver) can accelerate the forwarding and processing of data packets. PMD allows applications to bypass the network protocol stack of the operating system kernel, communicate directly with network devices, and process data packets of network cards. Related technologies In the process of upgrading OVS, vswitchd needs to be restarted. Restarting vswitchd will reload PMD. When PMD is reloaded, the system will reset the network interface, thus causing network connectivity to be lost. Summary of the invention

[0004] To overcome the problems existing in the related art, this specification provides a method and device for upgrading the OVS-DPDK process.

[0005] According to a first aspect of an embodiment of the present specification, a method for upgrading an OVS-DPDK process is provided, the method comprising: starting a target OVS-DPDK process; synchronizing the configuration information of an original OVS-DPDK process with the target OVS-DPDK process; releasing a binding relationship between a network interface and a PMD driver of the original OVS-DPDK process, and establishing a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; and exiting the original OVS-DPDK process.

[0006] According to the second aspect of the embodiments of this specification, a device for upgrading an OVS-DPDK process is provided, including: a startup module, used to start a target OVS-DPDK process; a synchronization module, used to synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process; a binding module, used to release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; and a withdrawal module, used to exit the original OVS-DPDK process.

[0007] According to a third aspect of an embodiment of this specification, a device for upgrading an OVS-DPDK process is provided, including:

[0008] processor;

[0009] a memory for storing processor-executable instructions;

[0010] Among them, the processor is configured to: start the target OVS-DPDK process; synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process; release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; exit the original OVS-DPDK process.

[0011] The technical solutions provided by the embodiments of this specification may have the following beneficial effects:

[0012] In the embodiment of this specification, during the process of upgrading the OVS-DPDK process, the binding relationship between the network interface and the OVS-DPDK process is switched so that the network interface does not need to be reset, so that non-first packet traffic can be forwarded normally through the network interface, avoiding network connection interruption.

[0013] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.

[0015] Figure 1 It is a schematic diagram of a system architecture shown in this specification according to an exemplary embodiment.

[0016] Figure 2 This is a flowchart of a method for upgrading an OVS-DPDK process according to an exemplary embodiment of the present specification.

[0017] Figure 3 It is a hardware structure diagram of the computer device where the file processing device in the embodiment of this specification is located.

[0018] Figure 4 It is a block diagram of a device for upgrading an OVS-DPDK process according to an exemplary embodiment of the present specification. DETAILED DESCRIPTION

[0019] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

[0020] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0021] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0022] Next, the embodiments of this specification are described in detail.

[0023] The following combination Figure 1 The system architecture of the method and device for upgrading the OVS-DPDK process in the embodiments of this specification is described. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of this specification can be applied, to help those skilled in the art understand the technical content of this specification, but it does not mean that the embodiments of this specification cannot be used in other devices, systems, environments or scenarios.

[0024] Figure 1 It is a schematic diagram of a system architecture shown in this specification according to an exemplary embodiment.

[0025] like Figure 1 As shown, the system architecture may include, for example, computing nodes and a DPU (Data Processing Unit) network card.

[0026] A computing node may include multiple namespaces (NAMESAPCE), such as NAMESAPCE1 and NAMESAPCE2. A namespace may include virtio-net (virtual network card).

[0027] The DPU network card may include OVS-DPDK and a hardware forwarding plane. OVS-DPDK may include a control plane and a data plane. The control plane may be, for example, a part of OVS-DPDK used to transmit instructions and calculate table entries, and may be used to implement message forwarding rules. The data plane may be a part of OVS-DPDK used to encapsulate and forward data messages, and may be used to implement fast message forwarding.

[0028] OVS-DPDK can be configured with representative interfaces (representor), such as representor0 and representor1. The representor provides an abstraction for representing the virtualized resources of the physical network card (NIC). It can map part of the NIC's resources (such as virtual functions, Virtual Function, VF) to the host machine for virtual switch management and operation. According to the embodiment of this specification, after the first packet of traffic is sent to the data plane of OVS-DPDK through the virtual representor, the control plane will unload the forwarding logic corresponding to the matching flow table to the hardware forwarding plane. Subsequent non-first packet traffic will be sent directly from the representor to the hardware forwarding plane, and the hardware forwarding plane will forward the traffic according to the flow table. In this way, the separation of the control plane and the data plane is achieved.

[0029] For example, the traffic sent from NAMESAPCE1 to NAMESAPCE2 can be called D1. NAMESAPCE1 can send traffic D1 to representative0. If D1 is the first packet traffic, it is sent to the data plane of OVS-DPDK by representative0. The OVS-DPDK control plane determines the flow table that matches D1, forwards D1 to representative1 according to the matching flow table (corresponding to path D2), and unloads the forwarding logic corresponding to the flow table matching D1 to the hardware forwarding plane (corresponding to path C1). Then representative1 forwards D1 to NAMESAPCE2. When representative0 receives D1 again later, it can send D1 directly to the hardware forwarding plane, and the hardware forwarding plane can forward D1 to representative1 according to the forwarding logic corresponding to the matching flow table (corresponding to path D3). Then representative1 forwards D1 to NAMESAPCE2. It can be understood that the above is an example of internal traffic forwarding in a computing node. If it is cross-node traffic, the cross-node traffic will eventually be sent to the corresponding node through the NIC (corresponding to path D4).

[0030] According to an embodiment of the present specification, when OVS-DPDK needs to be upgraded, the target OVS-DPDK process can be started. Then the configuration information of the original OVS-DPDK process can be synchronized with the target OVS-DPDK process. The binding relationship between the network interface and the PMD (Poll Mode Driver) of the original OVS-DPDK process is released, and the binding relationship between the network interface and the PMD driver of the target OVS-DPDK process is established. Next, the original OVS-DPDK process is exited.

[0031] The hardware forwarding plane involves the forwarding logic of traffic and the binding relationship between the physical network card port (NIC) and the representative interface on OVS-DPDK. The normal forwarding of traffic can be controlled and unloaded through the binding relationship of the hardware forwarding plane to ensure that the traffic of OVS-DPDK continues to flow during the upgrade process.

[0032] The following is a detailed description of the method for upgrading the OVS-DPDK process provided in the embodiments of this specification. Figure 2 As shown, Figure 2 This is a flowchart of a method for upgrading an OVS-DPDK process according to an exemplary embodiment of this specification. The method is applied to a DPU network card. The method for upgrading an OVS-DPDK process provided in an embodiment of this specification may include the following steps.

[0033] In step 210, the target OVS-DPDK process is started.

[0034] According to an embodiment of the present specification, the target OVS-DPDK process may be a target of an upgrade, and the original OVS-DPDK process may be an object to be upgraded.

[0035] In step 220, the configuration information of the original OVS-DPDK process is synchronized with the target OVS-DPDK process.

[0036] According to an embodiment of the present specification, the configuration information may include, for example, an openflow flow table, an ovsdb configuration, a dpcls flow table, interface information, and the like.

[0037] According to an embodiment of the present specification, the original OVS-DPDK process and the target OVS-DPDK process can communicate directly to synchronize configuration information. And / or, the configuration information of the original OVS-DPDK process can be backed up in advance. When the target OVS-DPDK process synchronizes the configuration information, the backed-up second configuration information can be restored to the target OVS-DPDK process to synchronize the configuration information.

[0038] In step 230, the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process is released, and a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process is established.

[0039] According to an embodiment of the present specification, a network interface may include, for example, a representative interface (representor) and a physical network card port.

[0040] At step 240, the original OVS-DPDK process is exited.

[0041] According to the embodiments of the present specification, during the upgrade of the OVS-DPDK process, since the representative interface and the physical network card port will not be reset, when the representative interface receives non-first packet traffic, the non-first packet traffic can be sent to the hardware forwarding plane. The hardware forwarding plane can determine the physical network card port corresponding to the non-first packet traffic based on the previously issued flow table, and then forward the non-first packet traffic through the physical network card port.

[0042] It can be seen that in the process of upgrading the OVS-DPDK process, by switching the binding relationship between the network interface and the OVS-DPDK process, the network interface does not need to be reconnected, so that the traffic can be forwarded normally through the network interface, avoiding network disconnection caused by network interface reconnection.

[0043] Optionally, the configuration information of the original OVS-DPDK process may include first configuration information and second configuration information. The second configuration information may be backed up in advance through the original OVS-DPDK process. When the target OVS-DPDK process synchronizes configuration information with the original OVS-DPDK process, on the one hand, the first configuration information may be sent to the target OVS-DPDK process through the original OVS-DPDK process, and on the other hand, the backed-up second configuration information may be restored to the target OVS-DPDK process. Exemplarily, in this embodiment, the first configuration information may include, for example, openflow flow tables and ovsdb (Open vSwitchDatabase, open source virtual switch database) configuration, etc., and the second configuration information may include, for example, DPCLS (DatapathClassifier, data path classifier) ​​flow tables and interface information, etc.

[0044] Optionally, after starting the target OVS-DPDK process, the representative interface can be configured to cache the first packet traffic when it is received. After exiting the original OVS-DPDK process, the cached first packet traffic can be processed by the target OVS-DPDK process; the representative interface is configured to send the first packet traffic to the target OVS-DPDK process when it is received.

[0045] Exemplarily, in this embodiment, after starting the target OVS-DPDK process, the status flag of the representative interface can be modified to a first predetermined flag. When the representative interface receives the first packet of traffic, it can pause sending the first packet of traffic to the original OVS-DPDK process according to the first predetermined flag, and cache the first packet of traffic. After exiting the original OVS-DPDK process, the status flag of the representative interface can be modified to a second predetermined flag. When the representative interface receives the first packet of traffic, it can resume sending the first packet of traffic to the target OVS-DPDK process according to the second predetermined flag. The first predetermined flag and the second predetermined flag can be set according to actual needs, for example, they can be numbers, letters, symbols, or any combination of numbers, letters and symbols.

[0046] Optionally, after starting the target OVS-DPDK process, the original OVS-DPDK process may be instructed to suspend sending flow tables to the hardware forwarding plane. After exiting the original OVS-DPDK process, the target OVS-DPDK process may resume sending flow tables to the hardware forwarding plane.

[0047] Another method for upgrading the OVS-DPDK process is shown below according to an exemplary embodiment. Based on the above embodiment, this embodiment describes a process of upgrading the OVS-DPDK process, including the following steps:

[0048] Step 1: Start the target OVS-DPDK process and notify the original OVS-DPDK process to synchronize the configuration.

[0049] More specifically, this step may include, for example:

[0050] a) Back up the openflow flow table and ovsdb configuration of the original OVS-DPDK process. Restore the backed up openflow flow table and ovsdb configuration to the target OVS-DPDK process;

[0051] b) The original OVS-DPDK process synchronizes the dpcls flow table, interface information, etc. to the target OVS-DPDK process.

[0052] Step 2: After the synchronization configuration is completed, the original OVS-DPDK process enters the switching preparation state.

[0053] More specifically, this step may include, for example:

[0054] a) Pause the sending of traffic and the unloading of flow tables (for example, corresponding Figure 1 D2 and C1 in );

[0055] b) Notify the hardware forwarding plane to maintain the forwarding state and suspend the flow table state update;

[0056] c) Set the interface status and configuration, for example, the state and configuration of the representor interface and the NIC interface can be set to ensure that the interface status and configuration will not change. In this way, the interface status and configuration can be locked to prevent accidental modification. The interface configuration can include, for example, the receiving interface queue, the sending interface queue, the number, etc. The interface status can include, for example, up (enabled) and down (disabled).

[0057] Step 3: The forwarding plane of the target OVS-DPDK process starts working, and the original OVS-DPDK process exits.

[0058] More specifically, this step may include, for example:

[0059] a) The original OVS-DPDK process exits, and the target OVS-DPDK process forwarding plane starts;

[0060] b) The network interface binding relationship is switched to the target OVS-DPDK process, and the interface is reconnected;

[0061] c) Notify the hardware forwarding plane to restore and update the flow table status and update the forwarding logic.

[0062] During the upgrade process, the hardware forwarding plane is responsible for forwarding non-first packet traffic. The entire forwarding process will not cause traffic interruption during the upgrade process. The interface in OVS-DPDK is an interface mapping, and there is no actual process of reinitializing the network card hardware, which will not cause traffic interruption during the network card reconnection process.

[0063] For the first packet flow, during the upgrade process, the packet reception from the representative interface will be suspended (for example, Figure 1 In addition, a message cache design is also made. The first packet of traffic that needs to be sent to the software for processing will be cached in the cache area. After the upgrade is completed, it will be processed with high priority and updated and uninstalled in the above step 3.

[0064] Corresponding to the embodiments of the aforementioned method, this specification also provides embodiments of a device for upgrading an OVS-DPDK process and a terminal used therein.

[0065] The embodiments of the device for upgrading the OVS-DPDK process in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor in which it is located reading the corresponding computer program instructions in the non-volatile memory into the memory and running them. From the hardware level, such as Figure 3 As shown, it is a hardware structure diagram of the computer device where the device for upgrading the OVS-DPDK process in the embodiment of this specification is located, except Figure 3 In addition to the processor 310, memory 330, network interface 320, and non-volatile memory 340 shown, the server or electronic device where the device 331 is located in the embodiment may also include other hardware according to the actual function of the computer device, which will not be described in detail.

[0066] like Figure 4 As shown, Figure 4 This is a block diagram of a device for upgrading an OVS-DPDK process according to an exemplary embodiment of the present specification, the device comprising:

[0067] A startup module 410 is used to start a target OVS-DPDK process;

[0068] A synchronization module 420, configured to synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process;

[0069] A binding module 430, used to release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and to establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process;

[0070] A module 440 is proposed for exiting the original OVS-DPDK process.

[0071] Optionally, the device may further include:

[0072] The first configuration module is used to configure the representative interface to cache the first packet traffic when receiving the first packet traffic after starting the target OVS-DPDK process;

[0073] A processing module, used to process the cached first packet traffic through the target OVS-DPDK process after exiting the original OVS-DPDK process;

[0074] The second configuration module is used to configure the representative interface to send the first packet traffic to the target OVS-DPDK process when receiving the first packet traffic after exiting the original OVS-DPDK process.

[0075] Optionally, the device may further include:

[0076] The sending module is used to send the non-first packet traffic to the hardware forwarding plane if the representative interface receives non-first packet traffic during the upgrade of the OVS-DPDK process;

[0077] A determination module is used for the hardware forwarding plane to determine the physical network card port corresponding to the non-first packet flow according to the flow table;

[0078] The forwarding module is used to forward non-first packet traffic through the physical network card port.

[0079] Optionally, the device may further include:

[0080] An instruction module, used to instruct the original OVS-DPDK process to stop sending flow tables to the hardware forwarding plane after starting the target OVS-DPDK process;

[0081] The sending module is used to send the flow table to the hardware forwarding plane through the target OVS-DPDK process after exiting the original OVS-DPDK process.

[0082] Optionally, the synchronization module includes:

[0083] The sending submodule is used to send the first configuration information to the target OVS-DPDK process through the original OVS-DPDK process.

[0084] Optionally, the device may further include:

[0085] A backup module, used to back up the second configuration information through the original OVS-DPDK process;

[0086] Synchronization modules can include:

[0087] The restore submodule is used to restore the backed-up second configuration information to the target OVS-DPDK process.

[0088] According to the embodiments of the present specification, during the process of upgrading the OVS-DPDK process, by switching the binding relationship between the network interface and the OVS-DPDK process, the network interface does not need to be reconnected, so that the traffic can be forwarded normally through the network interface, avoiding network interruption caused by reconnection of the network interface.

[0089] Correspondingly, the present specification also provides a device for upgrading an OVS-DPDK process, the device comprising a processor; a memory for storing processor executable instructions; wherein the processor is configured to: start a target OVS-DPDK process; synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process; release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; and exit the original OVS-DPDK process.

[0090] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0091] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0092] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0093] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention claimed herein. The specification is intended to cover any variations, uses or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not claimed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.

[0094] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0095] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for upgrading the OVS-DPDK process. It is characterized in that The method comprises: Start the target OVS-DPDK process; Synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process; Release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process, wherein the network interface includes a representative interface and a physical network card port; Exit the original OVS-DPDK process.

2. The method according to claim 1, It is characterized in that After starting the target OVS-DPDK process, the method further includes: The representative interface is configured to cache the first packet of traffic when the first packet of traffic is received; After exiting the original OVS-DPDK process, the method further includes: Processing the cached first packet traffic through the target OVS-DPDK process; The representative interface is configured to send the first packet of traffic to the target OVS-DPDK process when the first packet of traffic is received.

3. The method according to claim 1, It is characterized in that The method further comprises: During the upgrade of the OVS-DPDK process, if the representative interface receives non-first packet traffic, the non-first packet traffic is sent to the hardware forwarding plane; The hardware forwarding plane determines the physical network card port corresponding to the non-first packet flow according to the flow table; The non-first packet traffic is forwarded through the physical network card port.

4. The method according to claim 1, It is characterized in that After starting the target OVS-DPDK process, the method further includes: Instruct the original OVS-DPDK process to stop sending flow tables to the hardware forwarding plane; After exiting the original OVS-DPDK process, the method further includes: The flow table is sent to the hardware forwarding plane through the target OVS-DPDK process.

5. The method according to claim 1, It is characterized in that The synchronizing the configuration information of the original OVS-DPDK process with the target OVS-DPDK process includes: The first configuration information is sent to the target OVS-DPDK process through the original OVS-DPDK process.

6. The method according to claim 1, It is characterized in that The method further comprises: Backing up the second configuration information through the original OVS-DPDK process; The synchronizing the configuration information of the original OVS-DPDK process with the target OVS-DPDK process includes: The backed-up second configuration information is restored to the target OVS-DPDK process.

7. The method according to claim 5, It is characterized in that The first configuration information includes a dpcls flow table and interface information.

8. The method according to claim 6, It is characterized in that The second configuration information includes openflow flow table and ovsdb configuration information.

9. A device for upgrading the OVS-DPDK process, It is characterized in that The device comprises: Startup module, used to start the target OVS-DPDK process; A synchronization module, used to synchronize the configuration information of the original OVS-DPDK process with the target OVS-DPDK process; A binding module, used to release the binding relationship between the network interface and the PMD driver of the original OVS-DPDK process, and establish a binding relationship between the network interface and the PMD driver of the target OVS-DPDK process; Propose module for exiting the original OVS-DPDK process.

10. A device for upgrading the OVS-DPDK process, It is characterized in that The device comprises: processor; a memory for storing processor-executable instructions; The processor is used to execute processor-executable instructions to implement the method shown in any one of claims 1-8.

Citation Information

Patent Citations

  • Message forwarding method and device, server and storage medium

    CN110071880A

  • Method and device for hot upgrade of virtual switch

    CN116233038A

  • Multicast traffic replication method based on hardware unloading and related device

    CN116366534A

  • Hot upgrade method and device and electronic equipment

    CN117493027A

  • Intelligent network card hot upgrade method based on OVS-DPDK

    CN117857342A