A RoCE v2 Network Environment Traffic Control Method, System, and Storage Medium

Abstract

The present invention relates to a method, a system and a storage medium for traffic control in a RoCE v2 network environment. When congestion occurs, the present invention performs the operation of packing and sending RoCE v2 traffic data packets of the same type in sequence according to the preset RoCE v2 traffic data packet type order until the congestion is alleviated or all types of RoCE v2 traffic data packets are respectively packed and sent. The type order is as follows: log or information providing type, refreshed data type, and operation data type. After the congestion is alleviated, the RoCE v2 traffic data is unpacked and sent in sequence according to the order of operation data type, refreshed data type, and log or information providing type to resume normal sending. When congestion reaches packet loss, the RoCE v2 traffic data packets of the log or information providing type are preferentially lost. The present application alleviates congestion and reduces the packet loss of important refreshed data type and operation data type RoCE v2 traffic data packets without restricting the traffic injection of the data source.

Description

Technical Field

[0001] The present invention relates to the field of RoCE network traffic control, and particularly to a traffic control method, system, and storage medium for a RoCE v2 network environment. Background Art

[0002] In the era of data supremacy, people have more stringent requirements for the network. However, traditional TCP / IP Ethernet connections consume a large amount of CPU resources and require additional data processing, and can no longer meet the current network requirements for faster, more efficient, and scalable. In this case, RoCE (RDMA over Converged Ethernet) emerged as the times require. RDMA (Remote Direct Memory Access) can directly access the memory of another host or server from the memory of one host or server. It releases the CPU to perform its due work, improving both bandwidth and reducing latency, jitter, and CPU consumption.

[0003] In a network switch, network congestion occurs when the incoming traffic bandwidth is greater than the outgoing traffic bandwidth. A typical example is that multiple senders simultaneously send network data to the same destination. The switch's cache can handle temporary congestion, but when the congestion lasts too long, the switch's cache will become overloaded. When the switch cache is overloaded, the next newly received packet will be discarded. Packet loss reduces application performance because the complexity of retransmission and transport protocols brings latency. Lossless networks implement a flow control mechanism that can pause the incoming traffic before the cache overflows, preventing packet loss. However, the means of pausing the incoming traffic by the flow control itself will cause waste of the incoming bandwidth, forming a problem of congestion propagation. To avoid the congestion propagation caused by flow control, currently, some congestion control means are proposed. The core idea is that when congestion is detected, the congestion is reported to all source ports of the congested port, and the source ports limit the injection of traffic by reducing the speed. The speed reduction is uncertain, that is, it may start to reduce the speed, but the cache of the congested port has been released and there is no need to reduce the speed anymore, but the speed reduction action is still continuing, reducing the transmission efficiency. There is also over-speed reduction, resulting in a sudden drop in bandwidth, so that it is lower than the bottom line, and its performance will be pulled down. At the same time, the fluctuations in speed reduction recovery will also make the RoCE network stability relatively poor. Summary of the Invention

[0004] To solve the above technical problems or at least partially solve the above technical problems, the present invention provides a traffic control method, system, and storage medium for a RoCE v2 network environment.

[0005] In a first aspect, the present invention provides a traffic control method for a RoCE v2 network environment, including:

[0006] When congestion occurs, perform the operation of packing and sending the RoCE v2 traffic data packets of the same type in sequence according to the preset RoCE v2 traffic data packet type order until the congestion is relieved or all types of RoCE v2 traffic data packets have been packed and sent respectively. The type order is as follows: log or information providing class, refreshed data class, and operation data class;

[0007] After the congestion is relieved, unpack and send the RoCE v2 traffic data in the order of operation data class, refreshed data class, and log or information providing class in sequence to resume normal sending;

[0008] When congestion reaches packet loss, preferentially drop the RoCE v2 traffic data packets of the log or information providing class.

[0009] Furthermore, the source Ethernet network card port adds corresponding identification marks in the UDP header of the RoCE v2 traffic data packets according to the type of the RoCE v2 traffic data packets; add a first identification mark in the UDP header of the RoCE v2 traffic data packets of the operation data class, add a second identification mark in the UDP header of the RoCE v2 traffic data packets of the refreshed data class, and add a third identification mark in the UDP header of the RoCE v2 traffic data packets of the log or information providing class; identify the type of the RoCE v2 traffic data packets based on the identification marks.

[0010] Furthermore, when the RoCE v2 traffic data packets are transmitted to the destination Ethernet network card port buffer, the destination Ethernet network card port rereads and disassembles the identification marks added in the RoCE v2 traffic data packets.

[0011] Furthermore, when congestion occurs, the operation of packing and sending the RoCE v2 traffic data packets of the same type in sequence according to the preset RoCE v2 traffic data packet type order includes:

[0012] When congestion occurs, first pack and send the RoCE v2 traffic data packets of the log or information providing class, and send the RoCE v2 traffic data packets of the operation data class and the refreshed data class as normal;

[0013] If, after packing and sending the RoCE v2 traffic data packets of the log or information providing class, the congestion continues to reach the set duration and the cache continues to be full with a risk of packet loss, pack and send the RoCE v2 traffic data packets of the log or information providing class and the refreshed data class respectively, and send the RoCE v2 traffic data packets of the operation data class as normal;

[0014] If, after separately packaging and sending the log or information providing class and the data refreshing class, the congestion persists for a set duration and the cache continues to be full with a risk of packet loss, the RoCEv2 traffic data packets of the log or information providing class, the data refreshing class, and the operation data class are separately packaged and sent.

[0015] Furthermore, when configuring different packaging amounts for different stages from low to high, when the same type of RoCE v2 traffic data packets are separately packaged and sent, if the congestion is not alleviated, the amount of the same type of RoCE v2 traffic data packets is gradually increased in ascending order according to the packaging amount for packaging and sending. When the congestion is alleviated, the amount of the same type of RoCE v2 traffic data packets is gradually decreased in descending order according to the packaging amount.

[0016] Furthermore, the step increment between adjacent values of the packaging amount is the product of the IO bandwidth and a preset coefficient. The preset coefficient for a type of RoCE v2 traffic data packet is the product of the proportion of this type of RoCE v2 traffic data packet in the total data and the preset step increment ratio.

[0017] Furthermore, when the amount of the same type of RoCE v2 traffic data packets selected for packaging and sending or for canceling packaging and sending is less than the step increment, the remaining amount is used to select RoCE v2 traffic data packets for packaging and sending or for canceling packaging and sending.

[0018] Furthermore, when congestion causes packet loss of the RoCE v2 traffic data packets of the data refreshing class or the operation data class, it triggers the receiving end to generate corresponding logs, and corresponding operations or data refreshing are performed based on the logs to make up for it.

[0019] In a second aspect, an embodiment of the present invention provides a system for implementing a RoCE v2 network environment traffic control method, including: a transmitting end, a transmitting end network card, a switch, a receiving end network card, and a receiving end. The switch is connected to the transmitting end network card and the receiving end network card. At least one storage unit and one processing unit are respectively configured for the transmitting end, the transmitting end network card, the switch, the receiving end network card, and the receiving end. The storage unit stores computer programs and data. When the computer program is executed by the processing unit, the RoCE v2 network environment traffic control method described above is implemented.

[0020] In a third aspect, an embodiment of the present invention provides a storage medium for implementing a RoCE v2 network environment traffic control method. The storage medium stores a computer program, and when the computer program is executed by at least one processor, the RoCE v2 network environment traffic control method is implemented.

[0021] The above technical solutions provided by the embodiments of the present invention have the following advantages compared with the prior art:

[0022] When congestion occurs in the present invention, RoCE v2 traffic data packets of the same type are respectively packed and sent in accordance with the preset RoCE v2 traffic data packet type sequence until the congestion is alleviated or all types of RoCE v2 traffic data packets are respectively packed and sent. The type sequence is as follows: log or information providing type, refreshed data type, and operation data type. After the congestion is alleviated, the RoCE v2 traffic data is unpacked and sent in the order of operation data type, refreshed data type, and log or information providing type to resume normal sending. When congestion occurs, the sending of important operation data type and refreshed data type is preferentially ensured, and the congestion is alleviated by sending the log or information providing type after packing. Once the sending of the log or information providing type after packing fails to alleviate the congestion, the sending of the operation data type is ensured by sending the refreshed data type after packing to reduce the congestion. When all types of RoCE v2 traffic data packets are packed and sent but the congestion still causes packet loss, the RoCE v2 traffic data packets of the log or information providing type are preferentially lost to reduce the packet loss of the RoCE v2 traffic data packets of the refreshed data type and operation data type. Without restricting the data source traffic injection, the present application alleviates the congestion and reduces the packet loss of important RoCE v2 traffic data packets of the refreshed data type and operation data type. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present invention and used together with the specification to explain the principles of the present invention.

[0024] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0025] Figure 1 It is a flowchart of a RoCE v2 network environment traffic control method provided by an embodiment of the present invention;

[0026] Figure 2 It is a detailed flowchart of the RoCE v2 network environment traffic control method provided by an embodiment of the present invention;

[0027] Figure 3 It is a flowchart of packing and sending RoCE v2 traffic data packets of the log or information providing type in stages according to the packing amount and congestion situation of RoCE v2 traffic data packets of the log or information providing type provided by an embodiment of the present invention;

[0028] Figure 4A flowchart for sending out RoCE v2 traffic data packets of the log or information providing class after packing them in stages according to the sub - category order and congestion situation of the log or information providing class provided by the embodiments of the present invention;

[0029] Figure 5 A flowchart for sending out RoCE v2 traffic data packets of the refreshed data class after packing them in stages according to the packing quantity and congestion situation of the RoCE v2 traffic data packets of the refreshed data class provided by the embodiments of the present invention;

[0030] Figure 6 A flowchart for sending out RoCE v2 traffic data packets of the refreshed data class after packing them in stages according to the sub - category order and congestion situation of the refreshed data class provided by the embodiments of the present invention;

[0031] Figure 7 A flowchart for sending out RoCE v2 traffic data packets of the operation data class after packing them in stages according to the packing quantity and congestion situation of the RoCE v2 traffic data packets of the operation data class provided by the embodiments of the present invention;

[0032] Figure 8 A flowchart for sending out RoCE v2 traffic data packets of the operation data class after packing them in stages according to the sub - category order and congestion situation of the operation data class provided by the embodiments of the present invention;

[0033] Figure 9 A schematic diagram of a system for implementing a RoCE v2 network environment traffic control method provided by the embodiments of the present invention. Detailed implementation manners

[0034] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0035] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non - exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not explicitly listed, or further includes elements inherent to such a process, method, article or device. Without further limitations, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

[0036] Example 1

[0037] Refer to Figure 1 As shown, the present invention provides a method for controlling the traffic of a RoCE v2 network environment, including:

[0038] The source Ethernet card port adds corresponding identification marks in the UDP header of the RoCE v2 traffic data packet according to the type of the RoCE v2 traffic data packet. Among them, the source Ethernet card is the Ethernet card at the data sending end and supports the RoCE v2 specification. The RoCE v2 specification is developed on the basis of RoCE, and its data packet format includes Eth L2 Header, Ethertype, IP Header, protocol number, UDP Header, port number, IB BTH+, IB Payload, ICRC, and FCS.

[0039] The source Ethernet card port adds a first identification mark in the UDP header (UDP Header) of the RoCE v2 traffic data packet of the operation data type, adds a second identification mark in the UDP header of the RoCE v2 traffic data packet of the refresh data type, and adds a third identification mark in the UDP header of the RoCE v2 traffic data packet of the log or information providing type; the type of the RoCE v2 traffic data packet is identified based on the identification mark. If the number of bits occupied by the identification mark is k, then 2^k needs to be greater than the number of types of RoCE v2 traffic data packets. This application does not limit the RoCE v2 traffic data packets of the data operation type, the refresh data type, and the log or information providing type as the most refined types. In the specific application process, the three types of RoCE v2 traffic data packets can be further classified according to the data priorities of the data operation type, the refresh data type, and the log or information providing type. The factors affecting the priority include but are not limited to: the packet delay requirement and the importance of the packet; the higher the delay requirement (the shorter the sending time requirement), the higher the priority and the later the sorting, and the higher the importance of the packet, the higher the priority and the later the sorting. Accordingly, the identification mark is configured into two parts. The first part represents the three major types of the data operation type, the refresh data type, and the log or information providing type, and the second part represents the further refined small types in the three major types.

[0040] When congestion occurs, the RoCE v2 traffic data packets of the same type are respectively packed and sent in the order of the preset RoCE v2 traffic data packet types until the congestion is alleviated or all types of RoCE v2 traffic data packets are respectively packed and sent. Among them, the type order is as follows: log or information providing class, refreshed data class, and operation data class. When the three major categories are further subdivided into several small categories, the type order obtained by further defining the order of the sub-categories in each major category is as follows: log or information providing class_sub-category 1, log or information providing class_sub-category 2..., refreshed data class_sub-category 1, refreshed data class_sub-category 2..., and operation data class_sub-category 1, operation data class_sub-category 2...

[0041] After the congestion is alleviated, the RoCE v2 traffic data is unpacked and sent in the reverse order of the preset RoCE v2 traffic data packet type order, that is, in the order of operation data class, refreshed data class, and log or information providing class, to resume normal sending.

[0042] In the specific implementation process, refer to Figure 2 As shown, during the normal sending process of RoCE v2 traffic data packets, the type of RoCE v2 traffic data packets is identified through the identification mark in the UDP header, and whether congestion occurs is detected. When congestion occurs, a congestion notification will be generated. After receiving the congestion notification, first, the RoCE v2 traffic data packets identified as the log or information providing class through the identification mark in the UDP header are packed and sent, and the RoCE v2 traffic data packets of the operation data class and the refreshed data class are sent as normal.

[0043] As a preferred implementation manner, refer to Figure 3As shown, for RoCE v2 traffic data packets of the log or information providing type, different levels of packetization amounts are configured from low to high. When performing the operation of packetizing and sending the RoCE v2 traffic data packets of the log or information providing type, first select a part from all the RoCE v2 traffic data packets of the log or information providing type according to the lowest value in the packetization amount for packetization. If the congestion is not alleviated, gradually increase the amount of RoCE v2 traffic data packets of the log or information providing type selected in ascending order according to the packetization amount, perform packetization and then send. If the congestion is alleviated, gradually decrease the amount of RoCE v2 traffic data packets of the log or information providing type selected in descending order according to the packetization amount, and send after de-packetization. The step increment between adjacent values of the packetization amount of the RoCE v2 traffic data packets of the log or information providing type is the product of the IO bandwidth and the preset coefficient for the RoCE v2 traffic data packets of the log or information providing type. The preset coefficient for the RoCE v2 traffic data packets of the log or information providing type is the product of the proportion of the RoCE v2 traffic data packets of the log or information providing type in the total data and the preset step increment ratio. When the amount of RoCE v2 traffic data packets of the log or information providing type selected for packetization or de-packetization is less than the step increment, select the RoCE v2 traffic data packets according to the remaining amount for packetization or de-packetization and then send.

[0044] As a preferred implementation, refer to Figure 4 As shown, if the log or information providing type is further subdivided, preset the order of the sub-categories of the log or information providing type. First select the sub-category that appears first in the order of the sub-categories of the log or information providing type (log or information providing type_sub-category 1) for packetization and then send. If the congestion is not alleviated, gradually increase the selection of sub-categories (such as the second increase in selecting log or information providing type_sub-category 2) for packetization and then send in accordance with the order of the sub-categories of the log or information providing type; if the congestion is alleviated, gradually decrease the selection of the corresponding sub-categories for de-packetization and send in descending order according to the order of the sub-categories of the log or information providing type.

[0045] If, after packetizing and sending the RoCE v2 traffic data packets of the log or information providing type, the congestion persists for a set duration and the cache continues to be full with a risk of packet loss, packetize and send the RoCE v2 traffic data packets of the log or information providing type and the refresh data type separately, and send the RoCE v2 traffic data packets of the operation data type conventionally.

[0046] As a preferred implementation, refer to Figure 5As shown, for RoCE v2 traffic data packets of the refresh data type, different levels of packetization amounts are configured from low to high. When performing the operation of packetizing and then transmitting the RoCE v2 traffic data packets of the refresh data type, first, a part is selected from all the RoCE v2 traffic data packets of the refresh data type according to the lowest value in the packetization amount for packetization. If the congestion is not alleviated, the amount of RoCE v2 traffic data packets of the refresh data type selected is gradually increased in ascending order according to the packetization amount for packetization and then transmitted after packetization. If the congestion is alleviated, the amount of RoCE v2 traffic data packets of the refresh data type selected is gradually decreased in descending order according to the packetization amount. The step increment between adjacent values of the packetization amount of the RoCE v2 traffic data packets of the refresh data type is the product of the IO bandwidth and a preset coefficient for the RoCE v2 traffic data packets of the refresh data type. The preset coefficient for the RoCE v2 traffic data packets of the refresh data type is the product of the proportion of the RoCE v2 traffic data packets of the refresh data type in the total data and a preset step increment ratio. When the amount of RoCE v2 traffic data packets of the refresh data type selected for or after de-packetization and transmission is less than the step increment, the remaining amount is used to select RoCE v2 traffic data packets for or after de-packetization and transmission.

[0047] As a preferred implementation, refer to Figure 6 As shown, if the RoCE v2 traffic data packets of the refresh data type are further subdivided, the order of the sub-categories of the preset refresh data type is set. First, the sub-category that appears first in the order of the sub-categories of the refresh data type (refresh data - sub-category 1) is selected for packetization and then transmitted. If the congestion is not alleviated, the sub-categories selected are gradually increased in order according to the order of the sub-categories of the refresh data type (such as the second time, refresh data - sub-category 2 is added for selection) for packetization and then transmitted. If the congestion is alleviated, the corresponding sub-categories selected are gradually decreased in descending order according to the order of the sub-categories of the refresh data type for de-packetization and then transmitted.

[0048] If, after packetizing and transmitting the log or information providing type and the refresh data type separately, the congestion persists for a set duration and there is a risk of packet loss due to the cache being continuously full, the RoCEv2 traffic data packets of the log or information providing type, the refresh data type, and the operation data type are all packetized and transmitted separately.

[0049] As a preferred implementation, refer to Figure 7As shown in the figure, for RoCE v2 traffic data packets of the operation data type, different levels of packetization amounts are configured from low to high. When performing the operation of packetizing and sending RoCE v2 traffic data packets of the operation data type, first select a part from all RoCE v2 traffic data packets of the operation data type according to the lowest value in the packetization amount for packetization. If the congestion is not alleviated, gradually increase the amount of RoCE v2 traffic data packets of the operation data type selected in ascending order according to the packetization amount, perform packetization and then send. If the congestion is alleviated, gradually decrease the amount of RoCE v2 traffic data packets of the operation data type selected in descending order according to the packetization amount. The step increment between adjacent values of the packetization amount of RoCE v2 traffic data packets of the operation data type is the product of the IO bandwidth and the preset coefficient for RoCE v2 traffic data packets of the operation data type. The preset coefficient for RoCE v2 traffic data packets of the operation data type is the product of the proportion of RoCE v2 traffic data packets of the operation data type in the total data and the preset step increment ratio. When the amount of RoCE v2 traffic data packets of the operation data type selected for or after unpacking and sending is less than the step increment, select the RoCE v2 traffic data packets according to the remaining amount for or after unpacking and sending.

[0050] As a preferred implementation, refer to Figure 8 As shown in the figure, if the RoCE v2 traffic data packets of the operation data type are further subdivided, the order of the subdivided subcategories of the preset operation data type is set. First, select the subcategory that appears first in the order of the subdivided subcategories of the operation data type (operation data type_subcategory 1) for packetization and then send. If the congestion is not alleviated, gradually increase the selection of subcategories in the order of the subdivided subcategories of the operation data type (such as the second increase in selecting operation data type_subcategory 2) for packetization and then send; if the congestion is alleviated, gradually decrease the selection of the corresponding subcategories in descending order in the order of the subdivided subcategories of the operation data type for unpacking and then sending.

[0051] When congestion reaches packet loss, preferentially perform packet loss on RoCE v2 traffic data packets of the log or information provision type. Packet loss includes but is not limited to packet loss generated by congestion of the source Ethernet network card at the sending end, packet loss generated by congestion of the forwarding switch, and packet loss generated by congestion of the destination Ethernet network card at the receiving end. Congestion causing packet loss of RoCE v2 traffic data packets of the refresh data type or operation data type triggers the receiving end to generate corresponding logs, and corresponding operations or data refreshes are performed based on the logs to make up for it.

[0052] As a preferred implementation, when the RoCE v2 traffic data packets are transmitted to the destination Ethernet network card port buffer, the destination Ethernet network card port rereads and disassembles the identification marks added in the RoCE v2 traffic data packets.

[0053] Embodiment 2

[0054] Refer to Figure 9As shown in the figure, an embodiment of the present invention provides a system for implementing a traffic control method in a RoCE v2 network environment, including: a transmitting end, a transmitting end network card, a switch, a receiving end network card, and a receiving end. The switch is connected to the transmitting end network card and the receiving end network card. The transmitting end, the transmitting end network card, the switch, the receiving end network card, and the receiving end are respectively configured with at least one storage unit and a processing unit. The storage unit stores a computer program and data. When the computer program is executed by the processing unit, the RoCE v2 network environment traffic control method is implemented.

[0055] Embodiment 3

[0056] An embodiment of the present invention provides a storage medium for implementing a traffic control method in a RoCE v2 network environment. The storage medium stores a computer program. When the computer program is executed by at least one processor, the RoCE v2 network environment traffic control method is implemented.

[0057] In several embodiments provided by the present invention, it should be understood that the disclosed modules and units can be implemented in other ways. For example, the structural embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the system or unit can be in an electrical, mechanical or other form.

[0058] The unit described as a separate component may or may not be physically separated. The component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0059] In addition, in each embodiment of the present invention, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0060] Although the present invention has been described in detail by referring to the accompanying drawings and in conjunction with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, those of ordinary skill in the art can make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions should all be within the scope of the present invention. / Any person skilled in the art within the technical scope disclosed by the present invention can easily conceive of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for traffic control in a RoCE v2 network environment, characterized in that, Including: The source Ethernet network card port adds corresponding identification marks in the UDP header of the RoCE v2 traffic data packet according to the type of the RoCE v2 traffic data packet; adds a first identification mark in the UDP header of the RoCE v2 traffic data packet of the operation data class, adds a second identification mark in the UDP header of the RoCE v2 traffic data packet of the refresh data class, and adds a third identification mark in the UDP header of the RoCE v2 traffic data packet of the log or information providing class; identifies the type of the RoCE v2 traffic data packet based on the identification mark. When congestion occurs, perform the operation of packing and sending the RoCE v2 traffic data packets of the same type in sequence according to the preset RoCE v2 traffic data packet type order until the congestion is relieved or all types of RoCE v2 traffic data packets are respectively packed and sent. The type order is as follows: log or information providing class, refresh data class, and operation data class. Among them, when congestion occurs, performing the operation of packing and sending the RoCE v2 traffic data packets of the same type in sequence according to the preset RoCE v2 traffic data packet type order includes: when congestion occurs, first pack and send the RoCE v2 traffic data packets of the log or information providing class, and send the RoCE v2 traffic data packets of the operation data class and the refresh data class normally; if after packing and sending the RoCE v2 traffic data packets of the log or information providing class, the congestion continues to reach the set duration and the cache continues to be full with a risk of packet loss, pack and send the RoCE v2 traffic data packets of the log or information providing class and the refresh data class respectively, and send the RoCE v2 traffic data packets of the operation data class normally; if after packing and sending the RoCE v2 traffic data packets of the log or information providing class and the refresh data class respectively, the congestion continues to reach the set duration and the cache continues to be full with a risk of packet loss, pack and send all the RoCE v2 traffic data packets of the log or information providing class, the refresh data class, and the operation data class respectively. After the congestion is relieved, unpack and send the RoCE v2 traffic data in sequence according to the order of operation data class, refresh data class, and log or information providing class, and resume normal sending. When congestion leads to packet loss, preferentially drop the RoCE v2 traffic data packets of the log or information providing class. When congestion causes the RoCE v2 traffic data packets of the refresh data class or the operation data class to be lost, trigger the receiving end to generate corresponding logs, and perform corresponding operations or data refreshing based on the logs to make up for it.

2. The method for traffic control in a RoCE v2 network environment according to claim 1, characterized in that, When the RoCE v2 traffic data packet is transmitted to the destination Ethernet network card port cache, the destination Ethernet network card port rereads and disassembles the identification mark added in the RoCE v2 traffic data packet.

3. The method for traffic control in a RoCE v2 network environment according to claim 1, characterized in that, Configure the packing amounts at different stages from low to high. When performing the operation of packing and sending the RoCE v2 traffic data packets of the same type, if the congestion is not relieved, select the amount of the RoCE v2 traffic data packets of the same type in ascending order step by step according to the packing amount, perform packing and sending. If the congestion is relieved, select the amount of the RoCE v2 traffic data packets of the same type in descending order step by step according to the packing amount.

4. The method for traffic control in a RoCE v2 network environment according to claim 3, characterized in that, The step increment between adjacent values of the packing quantity is the product of the IO bandwidth and a preset coefficient. For a certain type of RoCE v2 traffic data packet, the preset coefficient is the product of the proportion of this type of RoCE v2 traffic data packet in the total data and a preset step increment ratio.

5. The method for traffic control in a RoCE v2 network environment according to claim 4, characterized in that, When the number of the same type of RoCE v2 traffic data packets sent after packing or unpacking is less than the step increment, the remaining quantity is used to select RoCE v2 traffic data packets for packing or unpacking and then sending.

6. A system for implementing the method for traffic control in a RoCE v2 network environment, characterized in that, It includes: A transmitter, a transmitter network card, a switch, a receiver network card and a receiver. The switch is connected to the transmitter network card and the receiver network card. The transmitter, the transmitter network card, the switch, the receiver network card and the receiver are respectively configured with at least one storage unit and one processing unit. The storage unit stores computer programs and data. When the computer program is executed by the processing unit, it implements the RoCE v2 network environment traffic control method according to any one of claims 1-5.

7. A storage medium for implementing the method for traffic control in a RoCE v2 network environment, the storage medium stores a computer program, characterized in that, When the computer program is executed by at least one processor, it implements the RoCE v2 network environment traffic control method according to any one of claims 1-5.

Images