Network interface card stability testing methods, electronic devices, storage media and software products

Abstract

This application discloses a network card stability testing method, electronic device, storage medium, and program product, relating to the field of computer technology. This application involves setting the network card controller to have a normal installation version of network firmware and an abnormal image version of network firmware burned in. When running the normal installation version of network firmware and the abnormal image version of network firmware, network card stability testing is performed. The abnormal image version of network firmware can be configured according to actual needs, enabling comprehensive acquisition of test data. This allows for subsequent performance test result comparison and analysis based on test data from different versions to identify network card defects, thus achieving comprehensive network card stability testing.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a network card stability testing method, electronic device, storage medium, and program product. Background Technology

[0002] The application scenarios of FPGAs (Field-Programmable Gate Arrays) have expanded from traditional industrial control to cutting-edge fields such as AI and autonomous driving. Their core value lies in hardware flexibility, parallel efficiency, and low latency. With the evolution of toolchains and the rise of heterogeneous computing, FPGAs are transforming from "dedicated accelerators" to "reconfigurable computing platforms," ​​becoming key components for solving complex problems. Typical signals for choosing FPGAs include: scenarios requiring hardware acceleration but with undefined protocols, extreme sensitivity to latency / power consumption, or the need for rapid prototyping. For example, in smart NICs, FPGAs, due to their flexibility, programmability, high performance, and reconfigurability, have become core components for accelerating and intelligentizing network functions and are widely used in smart NICs. However, as the controller of smart NICs, FPGA development is complex, different versions have significant differences in performance and energy efficiency, and bitstream timing differences can lead to functional abnormalities. Summary of the Invention

[0003] This application provides a network card stability testing method, electronic device, storage medium, and program product to at least solve the problem in related technologies where the controller is affected by different versions, resulting in incomplete stability test data.

[0004] This application provides a method for testing the stability of a network interface card (NIC), wherein the NIC's controller is programmed with both a normal installation version of the network firmware and an abnormal image version of the network firmware. The method includes:

[0005] When the network firmware of the normal installation version is running in the network card, the network card is subjected to service performance testing, and the network performance data stream value of the network card is monitored;

[0006] The service performance test results of the network card are determined based on the network performance data stream values.

[0007] In response to the normal installed version of the network firmware completing the service performance test, the normal installed version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware.

[0008] When the abnormal image version of network firmware is running in the network card, a storage network flow test is performed on the network card, and the bandwidth value of the network card is monitored.

[0009] The storage read / write performance test results of the network card are determined based on the bandwidth value.

[0010] This application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of any of the above-described network interface card stability testing methods.

[0011] When the network firmware of the normal installation version is running in the network card, the network card is subjected to service performance testing, and the network performance data stream value of the network card is monitored;

[0012] The service performance test results of the network card are determined based on the network performance data stream values.

[0013] In response to the normal installed version of the network firmware completing the service performance test, the normal installed version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware.

[0014] When the abnormal image version of network firmware is running in the network card, a storage network flow test is performed on the network card, and the bandwidth value of the network card is monitored.

[0015] The storage read / write performance test results of the network card are determined based on the bandwidth value.

[0016] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-described network interface card stability testing methods:

[0017] When the network firmware of the normal installation version is running in the network card, the network card is subjected to service performance testing, and the network performance data stream value of the network card is monitored;

[0018] The service performance test results of the network card are determined based on the network performance data stream values.

[0019] In response to the normal installed version of the network firmware completing the service performance test, the normal installed version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware.

[0020] When the abnormal image version of network firmware is running in the network card, a storage network flow test is performed on the network card, and the bandwidth value of the network card is monitored.

[0021] The storage read / write performance test results of the network card are determined based on the bandwidth value.

[0022] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described network interface card stability testing methods:

[0023] When the network firmware of the normal installation version is running in the network card, the network card is subjected to service performance testing, and the network performance data stream value of the network card is monitored;

[0024] The service performance test results of the network card are determined based on the network performance data stream values.

[0025] In response to the normal installed version of the network firmware completing the service performance test, the normal installed version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware.

[0026] When the abnormal image version of network firmware is running in the network card, a storage network flow test is performed on the network card, and the bandwidth value of the network card is monitored.

[0027] The storage read / write performance test results of the network card are determined based on the bandwidth value.

[0028] This application enables network card stability testing by configuring the network card controller to have both a normal installation version of the network firmware and an abnormal image version of the network firmware burned in. The abnormal image version of the network firmware can be configured according to actual needs, and comprehensive test data can be obtained. This allows for subsequent performance test result comparison and analysis based on test data from different versions to identify network card defects and achieve comprehensive network card stability testing. Attached Figure Description

[0029] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a diagram illustrating the application environment of a network card stability testing method in one embodiment of this application.

[0031] Figure 2 This is a flowchart illustrating a network interface card (NIC) stability testing method in one embodiment of this application.

[0032] Figure 3 This is a logic diagram of a network card stability testing method in one embodiment of this application;

[0033] Figure 4 This is a schematic diagram illustrating the process of upgrading or switching between normal installed version network firmware and abnormal image version network firmware in one embodiment of this application.

[0034] Figure 5 This is a schematic diagram of the first type of network card stability testing method in one embodiment of this application;

[0035] Figure 6 This is a schematic diagram of a second type of network card stability testing method in one embodiment of this application;

[0036] Figure 7 This is a structural block diagram of a network card stability testing device in one embodiment of this application;

[0037] Figure 8 This is an internal structural diagram of a computer device in one embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0039] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0040] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0041] Smart network interface cards (NICs) primarily include encryption / decryption, firewall, TCP / IP, and HTTP processing, making them ideal for high-traffic web servers. They can offload all network, security, and storage functions from the host server, freeing up valuable processing power so the server can focus on running critical applications and operating systems more efficiently. Smart NICs can also perform virtualization, load balancing, and data path optimization.

[0042] Smart NICs are programmable network interface cards (NICs). They are flexible, programmable network interface cards capable of performing network traffic processing workloads typically handled by the CPU, such as TCP / IP and HTTP processing. Smart NICs require FPGA (Field-Programmable Gate Array) assistance; the core of a Smart NIC is to use an FPGA to assist the CPU in handling network loads, achieving hardware acceleration. Smart NICs support localized programming of both the data plane and control plane, allowing users to customize network functions according to their needs. Smart NICs typically contain multiple ports and an internal switch, enabling rapid data forwarding and intelligent mapping to relevant applications. Smart NICs can detect and manage network traffic, providing real-time network monitoring and troubleshooting capabilities.

[0043] The network card stability testing method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. Terminal 102 can test the stability of the network card in server 104. The network card has a controller, preferably an FPGA (Field Programmable Gate Array). Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. Server 104 can be a standalone server or a server cluster consisting of multiple servers.

[0044] like Figure 2 As shown, an embodiment of this application provides a method for testing network card stability. The network card controller has a normal installed version of network firmware and an abnormal image version of network firmware burned into it. The network card stability testing method includes the following steps:

[0045] Step S1: In response to the network card running a normal installed version of network firmware, perform a service usage performance test on the network card and monitor the network performance data stream value of the network card.

[0046] Step S2: Determine the network card's service usage performance test results based on the network performance data stream values;

[0047] Step S3: In response to the normal installation version of the network firmware completing the service performance test, the normal installation version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware.

[0048] Step S4: In response to the network interface card (NIC) running an abnormal image version of the network firmware, perform a storage network flow test on the NIC and monitor the bandwidth value of the NIC.

[0049] Step S5: Determine the network card's storage read / write performance test results based on the bandwidth value.

[0050] The normal installation version of the network firmware is the service version that matches the network card's attributes, while the abnormal image version of the network firmware is the service version that does not match the network card's attributes. For example, if an FM8 rpd file is written to an FM7 device, then the FM8 rpd file will be an abnormal image version of the network firmware. The rpd file is the programming data file.

[0051] This embodiment sets the network card controller to have both a normal installation version of the network firmware and an abnormal image version of the network firmware burned in. When running the normal installation version of the network firmware and the abnormal image version of the network firmware, the stability test of the network card is performed. The abnormal image version of the network firmware can be set according to actual needs. It can comprehensively acquire test data so that subsequent performance test results can be compared and analyzed based on the test data of different versions to find the defects of the network card and achieve comprehensive network card stability testing.

[0052] like Figure 3 As shown, in this embodiment, the network card stability testing method further includes:

[0053] Obtain the storage space of the controller in the network card to be tested, and divide the storage space into tool reserved space, image file space and application file space according to the storage address;

[0054] An abnormal image version of network firmware was burned into the image file space. The abnormal image version of network firmware includes functions such as flash memory burning, network port and communication interface. The abnormal image version of network firmware does not match the device type of the network card.

[0055] Burn the normal installation version of the network firmware into the application file space. The normal installation version of the network firmware is matched with the device type of the network card.

[0056] like Figure 3 As shown, an abnormal image version of network firmware is written at the Flash start address 0x01400000 (general).

[0057] In this embodiment, the network card stability testing method further includes:

[0058] Determine whether the network firmware of the normal installation version and the network firmware of the abnormal image version exist independently of each other;

[0059] In response to the fact that the normal installation version network firmware and the abnormal image version network firmware do not exist independently, the normal installation version network firmware and the abnormal image version network firmware are merged to create a first programming data file; when upgrading the normal installation version network firmware or the abnormal image version network firmware, the corresponding network firmware in the first programming data file is upgraded.

[0060] Since the normal installation version network firmware and the abnormal image version network firmware exist independently, the normal installation version network firmware is made into a second programming data file; when the normal installation version network firmware is upgraded, the second programming data file is upgraded; when the abnormal image version network firmware is upgraded, the abnormal image version network firmware in the image file space is upgraded.

[0061] As shown in the figure, in the topology diagram for the storage network stream testing, the host, network card, switch, and test server are interconnected.

[0062] First, modify the configuration of the grub (multi-boot manager) for the SOC (controller) big page and IOMMU (Input-Output Memory Management Unit).

[0063] Add the following to the end of the kernel cmdline in the grub (multi-boot manager) configuration file (vi / etc / default / grub) of the controller (SOC): default_hugepagesz=1G hugepagesz=1G hugepages=7 iommu=pt intel_iommu=on;

[0064] Update the grub file: grub2-mkconfig -o / boot / efi / EFI / ctyunos / grub.cfg;

[0065] Reboot the system.

[0066] Next, install the SPDK (Storage Applications) software and configure it in the same directory as the compressed file soc_sw.tar containing the software source files.

[0067] Finally, check the FPGA's operation on the SOC side under the abnormal image version of network firmware (Golden version): After the SOC side of the network card (SmartNIC) is powered on, it will preferentially enter the normal installed version of network firmware (APP image) by default. If the normal installed version of network firmware is invalid, it will directly enter the abnormal image version of network firmware. Log in to the SOC side of the network card (SmartNIC) and use the mailbox remote system update (RSU) command to switch. After the remote system update (RSU), you can rescan for PCIe devices by rescanning or restarting the network card, but you cannot shut down the network card. Shutting down will preferentially enter the normal installed version of network firmware by default.

[0068] like Figure 4 As shown, in this embodiment, the network card stability testing method further includes:

[0069] When upgrading the network firmware in response to the normal installation version, perform an in-band update on the abnormal image version network firmware according to the update content of the normal installation version network firmware, obtain the manager associated with the normal installation version network firmware, and perform an out-of-band update on the manager.

[0070] Responding to the burning of abnormal image version network firmware within the image file space or the upgrade of abnormal image version network firmware, the network card is restarted.

[0071] like Figure 4 As shown, in this embodiment, the network card stability testing method further includes:

[0072] When upgrading in response to an abnormal image version of the network firmware, perform an in-band update on the normal installation version of the network firmware based on the update content of the abnormal image version of the network firmware, obtain the manager (BMC) associated with the abnormal image version of the network firmware, and perform an out-of-band update on the manager.

[0073] The method for configuring the host is as follows:

[0074] a. Add the following to the end of the kernel cmdline (kernel command line parameters) in the grub configuration file on the backend host (vi / etc / default / grub): default_hugepagesz=1G hugepagesz=1G hugepages=20, save the configuration, and then reboot;

[0075] b. Install the SPDK (Storage Applications) RPM package on the cloud disk backend host; rpm -ivh spdk-22.01-4.ctl2.x86_64.rpm;

[0076] c. Execute `kill -9 `pidof nvmf_tgt` to kill the existing process (if it exists);

[0077] d. Then execute the start-nvmf.sh script to start the nvmf target process (you need to change target_ip in the script to the corresponding IP beforehand).

[0078] Specifically, the controller IP in the network interface card (NIC) must be configured, and the SoC and target IPs must be able to communicate.

[0079] a. Configure the network card IP address: ifconfig ens6f7 10.61.0.21 netmask 255.255.248.0 up;

[0080] b. Restart bss.service using systemctl to start the SPDK process;

[0081] c. Then execute the attach-nvme-disk.sh script to mount the disk (you need to change the target_ip in the script to the IP set by the storage backend beforehand).

[0082] Among them, storage network streaming test:

[0083] a. Configure IP

[0084] Configure host pf0 (MAC address 00:01:02:03:04:00) to correspond to the network interface IP address 12.0.0.3 / 24;

[0085] The host network card IP address is configured as 12.0.0.8 / 24.

[0086] Configure the MTU (Maximum Transfer Unit) of the host being tested to 4000: ifconfig ethx mtu 4000;

[0087] b. Flow test

[0088] Run the following command on the host being tested: iperf -s -P 4 -D;

[0089] On the host, run: iperf -c 12.0.0.8 -i 1 -t 10000 -P 4.

[0090] In this embodiment, in response to the normal installation version of the network firmware completing the service performance test, the normal installation version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware, including:

[0091] Configure the network card to start with the normal installed version of network firmware when the network card is powered on;

[0092] In response to switching the normal installed version of the network firmware to the abnormal image version of the network firmware, the version switch is triggered via remote system update command via email. The normal installed version of the network firmware is disabled to shut down the normal installed version of the network firmware, the network card is switched to the abnormal image version of the network firmware, and the network card is restarted after the function switch to rescan the solid-state drive device.

[0093] Among them, in response to the network card being powered off and then powered on again, the network card is controlled to start the normal installed version of network firmware.

[0094] like Figure 5 As shown, in this embodiment, in response to an abnormal image version of network firmware running in the network card, the network card is subjected to a storage network flow test, and the bandwidth value of the network card is monitored, including:

[0095] The types of storage and network flow tests that can be performed on a network card include storage flow test and network flow test.

[0096] When testing the storage read / write performance, throughput limits, or latency of the network interface card, a storage flow test is performed.

[0097] When testing the network interface card's bandwidth capacity, packet loss rate, latency jitter, or protocol processing capabilities, network flow testing is performed.

[0098] Specifically, such as Figure 5 As shown, the storage streaming test includes:

[0099] The storage application (SPDK), the first physical network port function module (PF1), and the second physical network port function module (PF2) are set in the controller (SOC) of the network card. The first physical network port function module and the second physical network port function module are connected through the storage application.

[0100] Configure a first address table (mac0) and a second address table (mac1) in the network card. The first address table and the second address table are connected to the test server through a switch.

[0101] The host machine is configured to include a semi-virtualized block device driver (virtio-blk) and a semi-virtualized network communication driver (virtio-net). The first address table is connected to the second physical network port function module, the first physical network port function module is connected to the semi-virtualized block device driver (virtio-blk), and the semi-virtualized network communication driver (virtio-net) is connected to the second address table.

[0102] After the test server is connected to the network card through the switch, the network card sends a one-way stream to the semi-virtualized block device driver (virtio-blk). The host sends data back to the network card through the opposite link. The test server monitors the data stream and bandwidth and determines whether it is greater than the preset bandwidth value. If it is, the network card's storage read and write performance is recorded as qualified; otherwise, the network card's storage read and write performance is recorded as unqualified.

[0103] The test server connects to the switch and then connects to the semi-virtualized network communication driver (virtio-net) via the second address table. The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value. If it does, it records that the network card's storage read / write performance is qualified; otherwise, it records that the network card's storage read / write performance is unqualified.

[0104] The paravirtio block device driver (virtio-blk) is a paravirtualization driver used in virtualization technology to implement high-performance block devices (such as virtual disks), and it is part of the virtio standard framework. It significantly improves disk performance in virtualized environments by optimizing storage I / O communication between virtual machines (VMs) and the host machine.

[0105] Among them, the paravirtualization network communication driver (virtio-net) is a paravirtualization driver used for network communication in a virtualization environment. It provides efficient network data transmission between the host and the virtual machine through the virtio framework.

[0106] Understandably, when performing service performance tests on the network card in response to the normal installation version of network firmware running in the network card, and monitoring the network performance data stream values ​​of the network card, the method of performing storage network flow testing on the network card when running an abnormal image version of network firmware can be the same as the storage flow testing method, including:

[0107] The controller in the network card is configured with a storage application (SPDK), a first physical network port function module (PF1), and a second physical network port function module (PF2). The first physical network port function module and the second physical network port function module are connected through the storage application.

[0108] Configure a first address table (mac0) and a second address table (mac1) in the network card. The first address table and the second address table are connected to the test server through a switch.

[0109] The host machine is configured to include a semi-virtualized block device driver (virtio-blk) and a semi-virtualized network communication driver (virtio-net). The first address table is connected to the second physical network port function module, the first physical network port function module is connected to the semi-virtualized block device driver (virtio-blk), and the semi-virtualized network communication driver (virtio-net) is connected to the second address table.

[0110] After the test server is connected to the network card via a switch, the network card sends a one-way data stream to the semi-virtualized block device driver (virtio-blk). The host sends data back to the network card via the opposite link. The test server monitors the data stream and bandwidth and determines whether it is greater than the preset bandwidth value. If it is, the network card's service performance is recorded as qualified; otherwise, the network card's service performance is recorded as unqualified.

[0111] The test server connects to the switch and then connects to the semi-virtualized network communication driver (virtio-net) through the second address table. The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value. If it does, it records that the network card's service performance is qualified; otherwise, it records that the network card's service performance is unqualified.

[0112] That is, such as Figure 5 As shown, when running the network firmware in a normal installation version or an abnormal image version, the network performance test of the network card includes two types of test data: the controller performance data stream from the host machine to the network card and the network performance data stream of the test server.

[0113] The link for the controller performance data flow from the host machine to the network card is as follows: the test server, the switch, the first address table (mac0) of the network card controller, the first physical network port function module (PF1), the storage application (SPDK), the second physical network port function module (PF2), and the semi-virtualized block device driver (virtio-blk) of the host machine.

[0114] The network performance data flow link of the test server is as follows: test server, switch, second address table (mac1) of the network card controller, and semi-virtualized network communication driver (virtio-net) of the host.

[0115] Specifically, such as Figure 6 As shown, in this embodiment, the network traffic interception test includes:

[0116] Configure a first address table (mac0) and a second address table (mac1) in the network card. The first address table and the second address table are connected to the test server through a switch.

[0117] Configure a third physical network port function module (PF3) in the network card controller. Configure the host to include a first network card function module (PF0), a second network card function module (PF1), and a third network card function module (PF2). The first network card function module is connected to the second address table, the second network card function module is connected to the first address table, and the third network card function module is connected to the third physical network port function module.

[0118] The control traffic is routed from the second network interface card (NIC) functional module to the first address table, then through the switch to the test server and back to the second NIC functional module.

[0119] The control traffic flows from the first network interface card (NIC) functional module to the second address table, then through the switch to the test server and back to the first NIC functional module;

[0120] Control the flow between the third network card function module and the third physical network port function module;

[0121] The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value. If it does, the network card's network transmission performance is recorded as qualified; otherwise, the network card's network transmission performance is recorded as unqualified.

[0122] Understandably, when performing service performance tests on the network card in response to the normal installation version of network firmware running in the network card, and monitoring the network performance data stream values ​​of the network card, the network flow test method can be the same as the network flow test method used when performing storage network flow tests on the network card while the abnormal image version of network firmware is running, including:

[0123] Configure a first address table (mac0) and a second address table (mac1) in the network card. The first address table and the second address table are connected to the test server through a switch.

[0124] Configure a third physical network port function module (PF3) in the network card controller. Configure the host to include a first network card function module (PF0), a second network card function module (PF1), and a third network card function module (PF2). The first network card function module is connected to the second address table, the second network card function module is connected to the first address table, and the third network card function module is connected to the third physical network port function module.

[0125] The control traffic is routed from the second network interface card (NIC) functional module to the first address table, then through the switch to the test server and back to the second NIC functional module.

[0126] The control traffic flows from the first network interface card (NIC) functional module to the second address table, then through the switch to the test server and back to the first NIC functional module;

[0127] Control the flow between the third network card function module and the third physical network port function module;

[0128] The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value. If it does, it records that the network card's service transmission performance is qualified; otherwise, it records that the network card's service transmission performance is unqualified.

[0129] That is, such as Figure 6As shown, when the network firmware is running in a normal installation version or an abnormal image version, the network interface card (NIC) is tested for storage network flow. The data stream includes the second NIC functional module (pf1) of the host, the first NIC functional module (pf0) of the host, the third NIC functional module (pf2) of the host, and the third physical network port functional module (PF3) of the NIC controller.

[0130] The data flow link of the second network interface card (PAC) module (PF1) of the host machine is as follows: the test server, the switch, the first address table (mac0) of the network interface card controller, and the second network interface card (PAC) module (PF1) of the host machine.

[0131] The data flow link of the first network interface card (NIC) functional module (pf0) of the host is: the test server, the switch, the second address table (mac1) of the NIC controller, and the first NIC functional module (pf0) of the host.

[0132] The data flow link between the third network interface card (NIC) functional module (PF2) of the host and the third physical network port functional module (PF3) of the NIC controller is: the third physical network port functional module (PF3) of the NIC controller and the third NIC functional module (PF2) of the host.

[0133] In this embodiment, when performing storage network flow testing on the network card, the following steps are also included:

[0134] Determine if the network card has undergone storage network flow testing. If so, stop the storage input / output performance test and execute the disk suspending script to delete the disk. Otherwise, perform the storage network flow testing and skip executing the disk suspending script.

[0135] In this embodiment, when performing storage network flow testing on the network card, the following steps are also included:

[0136] Set the maximum transmission rate threshold for the first, second, and third network interface card (NIC) modules in the host machine. When the transmission rate of any of the first, second, or third NIC modules exceeds the maximum transmission rate threshold, a speed reduction process will be implemented.

[0137] As shown in the figure, this embodiment performs the following steps for network traffic testing of the network card:

[0138] Step 1: Configure the SoC environment

[0139] Modify the GRUB configuration for SoC big pages and IOMMU;

[0140] Add the following line to the end of the kernel cmdline in the SoC's grub configuration file (vi / etc / default / grub): default_hugepagesz=1G hugepagesz=1G hugepages=7 iommu=pt intel_iommu=on;

[0141] Update the grub file: grub2-mkconfig -o / boot / efi / EFI / ctyunos / grub.cfg;

[0142] Reboot the system.

[0143] Step 2: Configure the host network card IP.

[0144] If you have run a hybrid streaming test before, you need to stop the host-side fio first;

[0145] Execute the detach-nvme-disk script to delete the disk. You can skip this step if you have not already mounted the disk.

[0146] 1) Hot-swap 3 network cards on the SoC side, and set the MTU to 9000 (-m specifies the MAC address table, which can be configured by yourself);

[0147] snictool -p -r 0;

[0148] snictool -p -r 1;

[0149] snictool -p -a port0 -f 0 -u 9000 -m 00:01:02:03:04:00;

[0150] snictool -p -a port1 -f 1 -u 9000 -m 00:02:02:03:04:00;

[0151] snictool -p -a port2 -f 2 -u 9000 -m 00:03:02:03:04:00.

[0152] 2) The IP and network card names of the three elastic network cards configured on the host side need to be modified according to the actual situation. You can first use the ifconfig command to check the MAC address of the network card and confirm the network cards corresponding to pf0, pf1, and pf2.

[0153] # Load the driver;

[0154] modprobe virtio_net virtio_ring virtio_pci;

[0155] # Find the PF corresponding to the network card based on the MAC address (snictool -p -l);

[0156] ip a;

[0157] # pf0;

[0158] ifconfig ens3 12.12.12.67 / 24;

[0159] # pf1;

[0160] ifconfig eth1 13.13.13.67 / 24;

[0161] # pf2;

[0162] ifconfig eth2 14.14.14.23 / 24.

[0163] Step 3: Configure the peer IP address

[0164] 1) Configure the host network card IP address for testing;

[0165] ifconfig xxx 12.12.12.13 / 24;

[0166] ifconfig xxx 13.13.13.13 / 24;

[0167] 2) Configure the SoC pf3 IP (the SoC needs to load the driver before it can see the pf, and the pf3 name is fixed as ens6f3);

[0168] modprobe virtio_net;

[0169] modprobe virtio_ring;

[0170] modprobe virtio_pci;

[0171] ifconfig ens6f3 hw ether cc1cce91d38f;

[0172] ifconfig ens6f3 14.14.14.24 / 24.

[0173] Step 4: Configure traffic splitting rules on the SoC side:

[0174] for i in $(seq 0 7); do snictool -c -d 2 $i; done;

[0175] snictool -e -b 1;

[0176] snictool -e -a 0;

[0177] # pf0<->mac0;

[0178] snictool -c -w -e 0x80 0xffff -q 0 -v 0x65;

[0179] snictool -c -w -e 0x65 0xffff -q 0 -v 0x80;

[0180] # pf1<->mac1;

[0181] snictool -c -w -e 0x81 0xffff -q 0 -v 0x66;

[0182] snictool -c -w -e 0x66 0xffff -q 0 -v 0x81;

[0183] # pf2<->soc pf3;

[0184] snictool -c -w -e 0x3 0xffff -q 0 -v 0x82;

[0185] snictool -c -w -e 0x82 0xffff -q 0 -v 0x3;

[0186] 5. IPERF stream testing (UDP large packet 8000, speed limit 24G)

[0187] The host uses iperf 2.0.8; the SoC uses iperf 2.1.6. The MTU of the network interface card used for the streaming is 9000. The MTU of both the SoC and the host is already 9000 in the steps.

[0188] The speed will be reduced once the performance threshold is exceeded; the speed limit should be strictly followed according to the procedure.

[0189] The first test step is: HOST---MAC stream attack.

[0190] Start the iperf client and iperf server.

[0191] Start the iperf server on the host, soc, and test host respectively:

[0192] iperf -s -w 1M -u -D;

[0193] The host sends data to the test host. In this example, the streaming rate is limited to 24G.

[0194] iperf -c 12.12.12.13 -i 1 -b 8G -w 1M -t 3000 -u -l 8000 -P 3;

[0195] iperf -c 13.13.13.13 -i 1 -b 8G -w 1M -t 3000 -u -l 8000 -P 3;

[0196] The host being tested sends a stream to the host.

[0197] iperf -c 12.12.12.67 -i 1 -b 8G -w 1M -t 3000 -u -l 8000 -P 3;

[0198] iperf -c 13.13.13.67 -i 1 -b 8G -w 1M -t 3000 -u -l 8000 -P 3.

[0199] Test step two: HOST---SOC streaming

[0200] Start the iperf client and iperf server.

[0201] Start the iperf server on both the host and soc:

[0202] iperf -s -w 1M -u -D;

[0203] The host is pushing traffic to the SoC, with a speed limit of 45G.

[0204] iperf -c 14.14.14.24 -i 1 -b 15G -w 1M -t 3000 -u -l 8000 -P 3.

[0205] The SoC is streaming to the host, with a speed limit of 45G.

[0206] iperf -c 14.14.14.23 -i 1 -b 15G -w 1M -t 3000 -u -l 8000 -P 3.

[0207] The above test steps can be summarized as follows: There are three PFs on the host side. PF usually refers to Physical Function.

[0208] First, traffic is diverted from pf1 on the host to mac0 under the SOC, then through the switch to the test server and back to pf1;

[0209] Secondly, the host's pf0 stream flows to mac1 under the SOC, then through the switch to the test server and back to pf0;

[0210] Finally, the host and soc side PF2 and PF3 exchange bandwidth; the test server monitors the network performance data flow to determine whether the claimed bandwidth value is met, thereby verifying the stability performance test.

[0211] In this embodiment, the network card stability testing method further includes:

[0212] Obtain test data for normal installed network firmware and various abnormal image versions of network firmware, and obtain the corresponding links for the test data. Classify and statistically analyze the test data according to the links.

[0213] By comparing test data from normal installed network firmware versions and various abnormal image versions of network firmware belonging to the same link, the defective functions of the network card are identified, and the corresponding code is adjusted accordingly.

[0214] Specifically, as shown in Table 1, Table 1 presents the test data statistics for storage network testing when the network card is in the normal installed version of the network firmware and various abnormal image versions of the network firmware.

[0215] Table 1

[0216]

[0217] As shown in Table 2, Table 2 presents the test data statistics for performance testing of network cards with normal installed network firmware and various abnormal image versions of network firmware.

[0218] Table 2

[0219]

[0220] In this embodiment, the network card stability testing method further includes:

[0221] In response to network card service performance failures or storage read / write performance failures, the system records network card test data and issues warning messages.

[0222] Among them, by setting early warning information, the defective functions of the network card can be accurately identified and the corresponding codes can be used. The early warning information can be used to make accurate adjustments, optimize the network performance of the network card, and achieve the goal of optimizing the stability of the network card.

[0223] This application can compare and analyze the performance test results when running normal installed network firmware and abnormal image version network firmware to identify the defective functions of the network card, and adjust the corresponding code for the defective functions to optimize the stability of the network card.

[0224] The application scenarios of FPGAs have expanded from traditional industrial control to cutting-edge fields such as AI and autonomous driving. Their core value lies in hardware flexibility, parallel efficiency, and low latency. With the evolution of toolchains and the rise of heterogeneous computing, FPGAs are transforming from "dedicated accelerators" to "reconfigurable computing platforms," ​​becoming key components for solving complex problems. Typical signals for choosing FPGAs include scenarios requiring hardware acceleration but with undefined protocols, extreme sensitivity to latency / power consumption, or the need for rapid prototyping. The above-mentioned solutions are used to verify the stability of FPGA versions. From the design stage, through a layered testing strategy (simulation → hardware → environment) and testing toolchain, firmware reliability can be significantly improved, mass production risks reduced, efficiency improved, and the reliability of the final product optimized.

[0225] In the above network card stability testing method, the network card controller is configured to have both a normal installation version of the network firmware and an abnormal image version of the network firmware burned into it. When running the normal installation version of the network firmware and the abnormal image version of the network firmware, the network card stability test is performed. The abnormal image version of the network firmware can be configured according to actual needs. It can comprehensively acquire test data so that subsequent performance test results can be compared and analyzed based on the test data of different versions to find network card defects and achieve comprehensive network card stability testing.

[0226] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0227] In one embodiment, such as Figure 7 As shown, a network card stability testing device 10 is provided, including: a normal installed version network firmware testing module 1, a version switching management module 2, and an abnormal image version network firmware testing module 3.

[0228] The normal installation version network firmware test module 1 is used to perform service performance tests on the network card when the normal installation version network firmware is running in the network card, and to monitor the network performance data stream value of the network card; and to determine the service performance test result of the network card based on the network performance data stream value.

[0229] Version switching management module 2 is used to respond to the normal installed version of network firmware to complete the service performance test, set the normal installed version of network firmware to invalid, and restart the network card to run the abnormal image version of network firmware.

[0230] The abnormal image version network firmware test module 3 is used to perform storage network flow tests on the network card in response to the abnormal image version network firmware running in the network card, and to monitor the bandwidth value of the network card; and to determine the storage read and write performance test results of the network card based on the bandwidth value.

[0231] In this embodiment, as Figure 7 As shown, the network card stability testing device 10 also includes a version storage management module 4, which is used for:

[0232] Obtain the storage space of the controller in the network card to be tested, and divide the storage space into tool reserved space, image file space and application file space according to the storage address;

[0233] An abnormal image version of network firmware was burned into the image file space. The abnormal image version of network firmware includes functions such as flash memory burning, network port and communication interface. The abnormal image version of network firmware does not match the device type of the network card.

[0234] Burn the normal installation version of the network firmware into the application file space. The normal installation version of the network firmware is matched with the device type of the network card.

[0235] In this embodiment, the version storage management module 4 is used for:

[0236] Determine whether the network firmware of the normal installation version and the network firmware of the abnormal image version exist independently of each other;

[0237] In response to the fact that the normal installation version network firmware and the abnormal image version network firmware do not exist independently, the normal installation version network firmware and the abnormal image version network firmware are merged to create a first programming data file; when upgrading the normal installation version network firmware or the abnormal image version network firmware, the corresponding network firmware in the first programming data file is upgraded.

[0238] Since the normal installation version network firmware and the abnormal image version network firmware exist independently, the normal installation version network firmware is made into a second programming data file; when the normal installation version network firmware is upgraded, the second programming data file is upgraded; when the abnormal image version network firmware is upgraded, the abnormal image version network firmware in the image file space is upgraded.

[0239] In this embodiment, the version storage management module 4 is used for:

[0240] When upgrading the network firmware in response to the normal installation version, perform an in-band update on the abnormal image version network firmware according to the update content of the normal installation version network firmware, obtain the manager associated with the normal installation version network firmware, and perform an out-of-band update on the manager.

[0241] Responding to the network card restarting after burning an abnormal image version of network firmware into the image file space or upgrading an abnormal image version of network firmware;

[0242] When upgrading network firmware in response to an abnormal image version, perform an in-band update on the normal installed version of the network firmware based on the update content of the abnormal image version of the network firmware, obtain the manager associated with the abnormal image version of the network firmware, and perform an out-of-band update on the manager.

[0243] In this embodiment, the network firmware, including both the normal installation version and the abnormal image version, is burned into the controller of the network card under test.

[0244] In response to the network card's first power-on, control the network card to enable the normally installed version of network firmware;

[0245] In response to switching the normal installed version of the network firmware to the abnormal image version of the network firmware, the version switch is triggered by the remote system update command via email. The normal installed version of the network firmware is disabled to shut down the normal installed version of the network firmware. The network card is switched to the abnormal image version of the network firmware. After the function switch, the network card is restarted and the solid-state drive device is rescanned.

[0246] In response to a power-on after the network card is powered off, control the network card to enable the normal installed version of the network firmware.

[0247] In this embodiment, in response to an abnormal image version of network firmware running in the network interface card (NIC), a storage network traffic test is performed on the NIC, and the bandwidth value of the NIC is monitored, including:

[0248] The types of storage and network flow tests that can be performed on a network card include storage flow test and network flow test.

[0249] When testing the storage read / write performance, throughput limits, or latency of the network interface card, a storage flow test is performed.

[0250] When testing the network interface card's bandwidth capacity, packet loss rate, latency jitter, or protocol processing capabilities, network flow testing is performed.

[0251] The storage streaming test includes:

[0252] A storage application, a first physical network port function module, and a second physical network port function module are set in the controller of the network card. The first physical network port function module and the second physical network port function module are connected through the storage application.

[0253] A first address table and a second address table are configured in the network card. The first address table and the second address table are connected to the test server through a switch.

[0254] The host machine is configured to include a semi-virtualized block device driver (virtio-blk) and a semi-virtualized network communication driver (virtio-net). The first address table is connected to the second physical network port function module, the first physical network port function module is connected to the semi-virtualized block device driver (virtio-blk), and the semi-virtualized network communication driver (virtio-net) is connected to the second address table.

[0255] After the test server is connected to the network card via a switch, the network card sends a one-way data stream to the semi-virtualized block device driver (virtio-blk). The host sends data back to the network card via the opposite link. The test server monitors the data stream and bandwidth and determines whether it exceeds the preset bandwidth value.

[0256] The test server connects to the switch and then to the semi-virtualized network communication driver (virtio-net) via the second address table. The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value.

[0257] In this embodiment, the network flow attack test includes:

[0258] A first address table and a second address table are configured in the network card. The first address table and the second address table are connected to the test server through a switch.

[0259] A third physical network port function module is set up in the network card controller. The host machine is configured to include a first network card function module, a second network card function module, and a third network card function module. The first network card function module is connected to the second address table, the second network card function module is connected to the first address table, and the third network card function module is connected to the third physical network port function module.

[0260] The control traffic is routed from the second network interface card (NIC) functional module to the first address table, then through the switch to the test server and back to the second NIC functional module.

[0261] The control traffic flows from the first network interface card (NIC) functional module to the second address table, then through the switch to the test server and back to the first NIC functional module;

[0262] Control the flow between the third network card function module and the third physical network port function module;

[0263] The test server monitors network performance data streams and determines whether they exceed the preset bandwidth value.

[0264] In this embodiment, when performing storage network flow testing on the network card, the following steps are also included:

[0265] Determine if the network card has undergone storage network flow testing. If so, stop the storage input / output performance test and execute the disk suspending script to delete the disk. Otherwise, perform the storage network flow testing and skip executing the disk suspending script.

[0266] In this embodiment, when performing storage network flow testing on the network card, the following steps are also included:

[0267] Set the maximum transmission rate threshold for the first, second, and third network interface card (NIC) modules in the host machine. When the transmission rate of any of the first, second, or third NIC modules exceeds the maximum transmission rate threshold, a speed reduction process will be implemented.

[0268] In this embodiment, as Figure 7 As shown, the network card stability testing device 10 also includes a test result recording module 5, which is used for:

[0269] Obtain test data for normal installed network firmware and various abnormal image versions of network firmware, and obtain the corresponding links for the test data. Classify and statistically analyze the test data according to the links.

[0270] By comparing test data of normal installed network firmware versions and various abnormal image versions of network firmware belonging to the same link, the defective functions of the network card are identified, and the corresponding code is adjusted accordingly.

[0271] In response to network card service performance failures or storage read / write performance failures, the system records network card test data and issues warning messages.

[0272] In the aforementioned network card stability testing device, the network card controller is equipped with both a normal installation version of the network firmware and an abnormal image version of the network firmware. When running the normal installation version of the network firmware and the abnormal image version of the network firmware, the network card stability test is performed. The abnormal image version of the network firmware can be configured according to actual needs. It can comprehensively acquire test data so that subsequent performance test results can be compared and analyzed based on the test data of different versions to find network card defects and achieve comprehensive network card stability testing.

[0273] For a description of the features in the embodiment corresponding to the network card stability testing device, please refer to the relevant description of the embodiment corresponding to the network card stability testing method, which will not be repeated here.

[0274] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the network card stability testing method embodiments described above.

[0275] In one embodiment, the electronic device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown, this electronic device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database stores network interface card (NIC) stability test data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a NIC stability testing method.

[0276] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described network interface card stability testing method embodiments when running.

[0277] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0278] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described network interface card stability testing method embodiments.

[0279] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described network interface card stability testing method embodiments.

[0280] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0281] The foregoing has provided a detailed description of the network interface card (NIC) stability testing method, electronic device, storage medium, and program product provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A method for testing the stability of a network interface card (NIC), characterized in that, The network interface card (NIC) controller has a normally installed version of network firmware and an abnormal image version of network firmware burned into it. The abnormal image version of network firmware is a service version of network firmware that does not match the attributes of the NIC. The method includes: When the network firmware of the normal installation version is running in the network card, the network card is subjected to service performance testing, and the network performance data stream value of the network card is monitored; The service performance test results of the network card are determined based on the network performance data stream values. In response to the normal installed version of the network firmware completing the service performance test, the normal installed version of the network firmware is set to invalid, and the network card is restarted to run the abnormal image version of the network firmware. When the abnormal image version of network firmware is running in the network card, a storage network flow test is performed on the network card, and the bandwidth value of the network card is monitored. The storage read / write performance test results of the network card are determined based on the bandwidth value; By comparing test data of normal installed network firmware versions and various abnormal image versions of network firmware belonging to the same link, the defective functions of the network card are identified, and the corresponding code is adjusted accordingly. Determine whether the normal installation version of the network firmware and the abnormal image version of the network firmware exist independently of each other; In response to the fact that the normal installation version network firmware and the abnormal image version network firmware do not exist independently, the normal installation version network firmware and the abnormal image version network firmware are merged to create a first programming data file; when the normal installation version network firmware or the abnormal image version network firmware is upgraded, the corresponding network firmware in the first programming data file is upgraded. In response to the fact that the normal installation version network firmware and the abnormal image version network firmware exist independently, the normal installation version network firmware is created as a second programming data file; when the normal installation version network firmware is upgraded, the second programming data file is upgraded; when the abnormal image version network firmware is upgraded, the abnormal image version network firmware in the image file space is upgraded.

2. The network card stability testing method according to claim 1, characterized in that, The method further includes: Obtain the storage space of the controller in the network card, and divide the storage space into tool reserved space, image file space and application file space according to the storage address; An abnormal image version of network firmware is burned into the image file space. The abnormal image version of network firmware includes functions such as flash memory burning, network port, and communication interface. The abnormal image version of network firmware does not match the device type of the network card. The normal installation version of the network firmware is burned into the application file space. The normal installation version of the network firmware is matched with the device type of the network card.

3. The network card stability testing method according to claim 1, characterized in that, The method further includes: When the normal installation version network firmware is upgraded, the abnormal image version network firmware is updated in-band according to the update content of the normal installation version network firmware, the manager associated with the normal installation version network firmware is obtained, and the manager is updated out-of-band. The network card is restarted in response to either burning an abnormal image version of the network firmware into the image file space or upgrading the abnormal image version of the network firmware.

4. The network card stability testing method according to claim 1, characterized in that, The method further includes: When the abnormal image version network firmware is upgraded, the normal installed version network firmware is updated in-band according to the update content of the abnormal image version network firmware, the manager associated with the abnormal image version network firmware is obtained, and the manager is updated out-of-band.

5. The network card stability testing method according to claim 2, characterized in that, The step of responding to the normal installation version of the network firmware completing the service performance test, setting the normal installation version of the network firmware to invalid, and restarting the network card to run the abnormal image version of the network firmware includes: When the network card is powered on, control the network card to enable the normally installed version of the network firmware; When the normal installed version of the network firmware completes the service performance test, a version switch is triggered via a remote system update command via email. The normal installed version of the network firmware is disabled to shut down the normal installed version of the network firmware. The network card switches the normal installed version of the network firmware to the abnormal image version of the network firmware. After the function switch, the network card is restarted to rescan the solid-state drive device to run the abnormal image version of the network firmware.

6. The network card stability testing method according to claim 1, characterized in that, When the abnormal image version of network firmware is running in the network interface card (NIC), the process of performing a storage network traffic test on the NIC and monitoring the bandwidth value of the NIC includes: The types of storage and network flow tests performed on the network card include storage flow test and network flow test; In response to testing the storage read / write performance, throughput limit, or latency of the network interface card, a storage flow test is performed; In response to testing the bandwidth capacity, packet loss rate, latency jitter, or protocol processing capability of the network interface card, a network flow test is performed.

7. The network card stability testing method according to claim 6, characterized in that, When conducting storage streaming tests, the following are included: The controller in the network card is equipped with a storage application, a first physical network port function module and a second physical network port function module, and the first physical network port function module and the second physical network port function module are connected through the storage application. A first address table and a second address table are configured in the network card, and the first address table and the second address table are connected to the test server through a switch; The host machine is configured to include a semi-virtualized block device driver and a semi-virtualized network communication driver. The first address table is connected to the second physical network port function module, the first physical network port function module is connected to the semi-virtualized block device driver, and the semi-virtualized network communication driver is connected to the second address table. After the test server is connected to the network card through the switch, the network card sends a one-way data stream to the semi-virtualized block device driver. The host machine sends data back to the network card through the opposite link. The test server monitors the data stream and bandwidth and determines whether it is greater than the preset bandwidth value. If it is, it records that the network card's storage read and write performance is qualified; otherwise, it records that the network card's storage read and write performance is unqualified. The test server is connected to the switch and connected to the semi-virtualized network communication driver through the second address table. The test server monitors the network performance data stream and determines whether it is greater than the preset bandwidth value. If it is, it records that the network card's storage read and write performance is qualified; otherwise, it records that the network card's storage read and write performance is unqualified.

8. The network card stability testing method according to claim 6, characterized in that, When conducting network flow testing, the following should be included: A first address table and a second address table are configured in the network card, and the first address table and the second address table are connected to the test server through a switch; A third physical network port function module is set in the controller of the network card. The host machine is set to include a first network card function module, a second network card function module and a third network card function module. The first network card function module is connected to the second address table, the second network card function module is connected to the first address table, and the third network card function module is connected to the third physical network port function module. The control traffic is directed from the second network interface card (NIC) functional module to the first address table, then through the switch to the test server and back to the second NIC functional module. The control traffic flows from the first network interface card (NIC) functional module to the second address table, then through the switch to the test server and back to the first NIC functional module; Control the flow between the third network card function module and the third physical network port function module; The test server monitors the network performance data stream and determines whether it exceeds the preset bandwidth value. If it does, the network card's network transmission performance is recorded as qualified; otherwise, the network card's network transmission performance is recorded as unqualified.

9. The network card stability testing method according to claim 6, characterized in that, The storage network flow test performed on the network card also includes: Determine whether the network card has undergone storage network flow testing. If so, stop the storage input / output performance test and execute the disk hanging script to delete the disk. Otherwise, perform the storage network flow test and skip executing the disk hanging script.

10. The network card stability testing method according to claim 8, characterized in that, The storage network flow test performed on the network card also includes: Set the maximum transmission rate threshold for the first, second, and third network interface card (NIC) functional modules in the host machine. When the transmission rate of any one of the first, second, or third NIC functional modules exceeds the maximum transmission rate threshold, a speed reduction process is performed.

11. The network card stability testing method according to claim 1, characterized in that, The method further includes: Obtain test data for normal installed network firmware and various abnormal image versions of network firmware, and obtain the corresponding links for the test data. Classify and statistically analyze the test data based on the links.

12. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the network interface card stability testing method as described in any one of claims 1 to 11 when executing the computer program.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the network card stability testing method as described in any one of claims 1 to 11.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the network card stability testing method as described in any one of claims 1 to 11.

Images