CN113114578A - Traffic congestion isolation method, device and system - Google Patents
Traffic congestion isolation method, device and system Download PDFInfo
- Publication number
- CN113114578A CN113114578A CN202110336539.4A CN202110336539A CN113114578A CN 113114578 A CN113114578 A CN 113114578A CN 202110336539 A CN202110336539 A CN 202110336539A CN 113114578 A CN113114578 A CN 113114578A
- Authority
- CN
- China
- Prior art keywords
- congestion
- service
- message
- service flow
- flow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/31—Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits
Abstract
The embodiment of the application discloses a method, a device and a system for isolating traffic congestion. In this application, after receiving a congestion isolation configuration issued by a controller, a switch or a server (referring to a source end of a congestion traffic flow) may isolate the congestion traffic flow from a normal traffic flow without congestion according to the congestion isolation configuration, where the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP, and the reverse congestion notification message CNP is triggered when another server receives a traffic message carrying a congestion flag. The scheme provided by the application isolates the congested service flow from the normal service flow without congestion, so that the transmission of the normal service flow without congestion can be prevented from being influenced when the congestion in the congested service flow is further eliminated.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a method, an apparatus, and a system for traffic congestion isolation.
Background
In order to solve the problem of server-side data processing delay during service streaming in a network, some data center networks have started to use an ROCE (RDMA over switched Ethernet, RDMA over Ethernet technology) technology at present. By using the RDMA (Remote Direct Memory Access) technology, a high forwarding bandwidth can be provided without loss and packet loss in the transmission process of the service message of the service stream, but the RDMA technology is sensitive to the delay or packet loss problem of the service message of the service stream, and particularly when the service stream transmitted in the rock network is congested and causes packet loss, a large area of retransmission of the service message of the service stream is caused, which causes a serious decrease in the transmission rate of the service stream in the whole rock network.
In the related art, in order to relieve congestion of a service flow in an rock network to avoid packet loss, the congestion of the congested service flow may be relieved by reducing a packet forwarding rate of a packet forwarding queue for storing a service packet of the congested service flow on a switch that forwards the congested service flow. However, when the device in the ROCE network forwards all the service flows, the service messages of all the service flows are stored in the same message forwarding queue for forwarding, that is, when the rate of forwarding the service messages by the message forwarding queue is reduced, normal service flows which are not congested and exist in the message forwarding queue are affected, so that the transmission rate of the normal service flows which are not congested in the ROCE network is also reduced.
Disclosure of Invention
The application discloses a method, a device and a system for isolating traffic congestion, which are used for isolating congested traffic flow from normal traffic flow without congestion and avoiding influencing the transmission of the normal traffic flow without congestion.
According to a first aspect of the embodiments of the present application, there is provided a traffic congestion isolation method, which is applied to a switch, and includes:
when receiving a reverse Congestion Notification Packet (CNP) (congestion Notification packet), sending the CNP to a controller, wherein the CNP is triggered by a server when receiving a service packet carrying a congestion mark; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and receiving congestion isolation configuration sent by the controller, and isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration.
According to a second aspect of the embodiments of the present application, there is provided a traffic congestion isolation method, applied to a first server, including:
receiving congestion isolation configuration sent by a controller; the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP message; the CNP message is triggered by a second server when receiving a service message carrying a congestion mark, and the first server is a source end of the service message; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration.
According to a third aspect of the embodiments of the present application, there is provided a traffic congestion isolation apparatus, which is applied to a switch, and includes:
a CNP message uploading unit, configured to, when a reverse congestion notification message CNP message is received, upload the CNP message to a controller, where the CNP message is triggered by a server when receiving a service message carrying a congestion flag; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and the congestion service flow isolation unit is used for receiving congestion isolation configuration sent by the controller and isolating the congestion service flow from normal service flows which are not congested according to the congestion isolation configuration.
According to a fourth aspect of the embodiments of the present application, there is provided a traffic congestion isolation apparatus, applied to a first server, including:
a congestion isolation configuration receiving unit, configured to receive a congestion isolation configuration issued by the controller; the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP message; the CNP message is triggered by a second server when receiving a service message carrying a congestion mark, and the first server is a source end of the service message; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and the congestion service flow isolation unit is used for isolating the congestion service flow from the normal service flow without congestion according to the congestion isolation configuration.
According to a fifth aspect of embodiments of the present application, there is provided a traffic congestion isolation system, the system comprising: the system comprises a switch, a controller and a server;
the switch receives a reverse congestion notification message (CNP) message, and sends the CNP message to a controller, wherein the CNP message is triggered by a server when receiving a service message carrying a congestion mark; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs;
when the controller receives a CNP message sent by the switch, the controller sends congestion isolation configuration to the switch, wherein the congestion isolation configuration is used for isolating the congested service flow from a normal service flow without congestion;
when the switch receives the congestion isolation configuration sent by the controller, the switch isolates the congested service flow from the normal service flow without congestion according to the congestion isolation configuration;
alternatively, the first and second electrodes may be,
when the controller receives a reverse congestion notification message (CNP), a congestion isolation configuration is issued to a server, wherein the congestion isolation configuration is used for isolating the congested service flow from a normal service flow without congestion; the CNP message is triggered by another server when receiving a service message carrying a congestion mark, the controller issues a server to which congestion isolation is configured as a source end of the service message, and the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs;
when the server receives the congestion isolation configuration sent by the controller, the existing priority value in the service message to be forwarded, which belongs to the congestion service flow, is modified into the reset priority value and the reset priority value is forwarded, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
as can be seen from the foregoing technical solutions, in the solutions provided in the present application, after receiving a congestion isolation configuration issued by a controller, a switch or a server (referring to a source end of a congested service flow) may isolate the congested service flow from a normal service flow without congestion according to the congestion isolation configuration, where the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP, and the reverse congestion notification message CNP is triggered when another server (such as a destination end of the congested service flow) receives a service message with a congestion flag. The scheme provided by the application isolates the congested service flow from the normal service flow without congestion, so that the transmission of the normal service flow without congestion can be prevented from being influenced when the congestion in the congested service flow is further eliminated.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.
Fig. 1 is a network architecture diagram of an rock network according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a method applied to traffic congestion isolation of a switch according to an embodiment of the present application;
fig. 3 is a flowchart of a method for traffic congestion isolation applied to a controller according to an embodiment of the present application;
fig. 4 is a schematic diagram of a networking architecture of an rock network according to an embodiment of the present application;
FIG. 5 is a schematic flow chart diagram of an embodiment for implementing the method shown in FIG. 2 according to the present disclosure;
fig. 6 is a schematic diagram of a networking architecture of another rock network according to an embodiment of the present application;
FIG. 7 is a schematic flow chart diagram of an embodiment for implementing the method shown in FIG. 3 according to an embodiment of the present application;
fig. 8 is a schematic diagram of an apparatus for implementing traffic congestion isolation applied to a switch according to an embodiment of the present application;
fig. 9 is a schematic diagram of an apparatus for implementing traffic congestion isolation applied to a controller according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions provided in the embodiments of the present application, the following description is made first on the related technologies involved in the embodiments of the present application:
as described in the background art, when a service flow transmitted in an ROCE network is congested and causes packet loss, a large-area retransmission of a service packet of the service flow may be caused, which may cause a serious decrease in a transmission rate of the service flow in the entire ROCE network. Therefore, in the related art, various technologies are provided to relieve Congestion caused by a traffic Flow, such as an ECN (Explicit Congestion Notification) technology based on a traffic Flow, a PFC (Priority-based Flow Control) technology based on a port and a queue, and the like.
It should be noted that, when relieving the congestion of the traffic flow, the ECN technique is implemented by notifying the source server that sends the congested traffic flow to reduce the rate of sending the traffic packet of the congested traffic flow, which has a small impact on the transmission process of the congested traffic flow, but the congestion solving is not strong enough, and a situation that the congestion cannot be solved, or even the congestion is more and more serious may occur.
The PFC technology is to notify the upper level device to reduce the rate of forwarding the service packet of the congested service flow when it is detected that the service flow forwarded on the device is congested, or even notify the upper level device to suspend forwarding the service packet of the congested service flow, at this time, the upper level device may cache the service packet of the congested service flow, and the congestion may occur in the upper level device due to the increase of the cache, and the upper level device may continue to notify the upper level device of itself to perform the above operations, so that the upper level notification is performed until the source server that sends the congested service flow is notified, which can ensure that the congestion is solved, and packet loss is avoided, but the impact on the transmission process of the congested service flow is large.
Therefore, in practical application, a scheme of combining ECN + PFC is adopted to ensure that service messages of service flows in the rock network are lossless and do not lose packets in a transmission process.
However, the PFC technique described above is implemented based on ports and queues, and the reduction of the rate of forwarding the service packet of the congested service flow on the device using the PFC is implemented by reducing the rate of sending the service flow to the device by the previous device, specifically, by reducing the packet forwarding rate of the packet forwarding queue storing the service packet of the congested service flow in the port that forwards the congested service flow, so as to implement the reduction of the rate of sending the service flow to the device by the previous device. However, in the ROCE network, the service messages of all the service flows are stored in the same message forwarding queue for forwarding, so when the message forwarding rate of the message forwarding queue is reduced, other uncongested normal service flows using the same message forwarding queue as the congested service flow will be affected, which causes the transmission rate of the uncongested normal service flows in the ROCE network to be reduced, even the normal service flows are cut off.
The following illustrates the influence of the rock networking shown in fig. 1 on the normal traffic flow when the PFC function is triggered in the related art:
referring to fig. 1, the DUT devices in fig. 1 are switches, servers 1 and 2 are source servers, servers 3 and 4 are destination servers, and all devices in fig. 1 have PFC and ECN functionality enabled. In the networking shown in fig. 1, all traffic is RDMA technology based traffic and the switch DUT1 forwards all traffic using the same queue. Where traffic flow 1 is sent from Server1, through Port1 and Port3 of DUT1 to Server 3; traffic flow 2 is sent from Server2 through Port2 and Port3 of DUT1 to Server 3; traffic stream 3 is sent from Server2 through Port2 and Port4 of DUT1 to Server 4.
Since traffic flow 1 and traffic flow 2 are input from different ports on the DUT, but output at the same output Port3, congestion is most likely to occur at Port 3. When traffic 1 and 2 are congested at Port3 and trigger the PFC function, the DUT will generate PFC backpressure frames and send upstream servers 1 and 2 from ports 1 and 2 to throttle the rate at which servers 1 and 2 send traffic to DUT 1. It can be seen that the normally forwarded traffic 3 is not actually congested on the forwarding path, but is still forced to slow down due to the reception of the PFC backpressure frame by the Server 2.
In view of the above, the present application provides the following traffic congestion isolation method, apparatus and system to solve the problem caused by traffic congestion. The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
An embodiment of the method provided by the present application is described below with reference to fig. 2:
referring to fig. 2, fig. 2 is a flowchart of a method for traffic congestion isolation applied to a switch according to an embodiment of the present application. As an example, the method shown in fig. 2 may be applied to the rock network architecture shown in fig. 4 or fig. 6.
As shown in fig. 2, the process may include the following steps:
It should be noted that, in this embodiment of the present application, at least two queues exist in a switch, where one queue is a packet forwarding queue used for storing service packets of all service flows that do not have congestion initially, and the other queue is a congestion reservation queue used for storing service packets of congested service flows when congested service flows occur, and at initial time, no service packet of any service flow may be stored in the congestion reservation queue, and the priority of the congestion reservation queue is lower than that of the packet forwarding queue.
As an embodiment, when the switch detects that the forwarded service flow is congested in the device, it determines that the service flow is a congested service flow, and modifies an uncongested flag, which is carried in a service packet and used for indicating that the congested service flow is not congested, of the service packet of the congested service flow stored in a packet forwarding queue, so as to send the service packet carrying the congested flag to a server, where the server is a destination server of the service packet.
In a specific implementation, the congestion marking can be implemented by configuring all devices in the rock network and starting the ECN function. After the ECN function is turned on, packets sent by a source end server (i.e., a source end that sends traffic packets of a traffic flow) in the rock network all carry a flag of ECN01 or ECN10, where the flag may indicate that the traffic flow is not congested, and the ECN function may be used when the traffic flow is forwarded. When the switch detects that the congestion service flow occurs, the switch modifies the ECN mark carried by the service message of the congestion service flow to be forwarded, which is stored in the message forwarding queue, into ECN11, so that the destination server can judge that the congestion service flow to which the service message belongs is congested according to the received ECN field of the service message of the congestion service flow.
Optionally, the switch detects whether the forwarded service flow is congested in the device, and may be implemented by detecting whether a cache occupancy at an ingress port for receiving the service flow on the switch exceeds a preset first water line value. The first water line value may be set according to a cache scheme of the ingress port on the switch, for example, when the cache of the ingress port on the switch is a fixed cache, a static value may be set as the first water line value (for example, the first water line value is set as 2000 cache units), when the cache of the ingress port on the switch is a shared cache, the first water line value may be set as a dynamic value (for example, the first water line value is set as 70% of the cache allocated to the ingress port), and the specific setting may be according to a service condition, and a detailed process of the setting may refer to related technologies, which is not described herein again.
In the embodiment of the application, when receiving a service message carrying a congestion mark, the server generates a CNP message by a trigger server and returns the CNP message to the switch, and when receiving a reverse congestion notification message CNP message, the switch sends the CNP message to the controller. Optionally, the switch determines the CNP packet from the received packet, and may determine that the received packet is the CNP packet by matching an OPCODE field of each packet received by a port receiving the CNP packet, where the OPCODE field matched to the packet is 129.
Further, before the implementation of the embodiment of the present application, an ERSPAN (Encapsulated Remote Switch Port Analyzer, a three-layer Remote flow mirroring technology) mirror configuration may be sent to the Switch by the controller, so as to indicate that the Switch determines that the received message is a CNP message, mirror the CNP message to the controller, and trigger the controller to send a congestion isolation configuration.
It should be noted that the congestion isolation configuration generated by the controller in this step 201 may include the following: matching items and actions.
As an embodiment, the matching item may be a service flow identifier of a congested service flow, and the action is to store the service flow identifier into a congestion reservation queue, where the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows where congestion does not occur are stored into the message forwarding queue.
For example, in the embodiment of the present application, the service flow identifier carried by the congestion message may be implemented by using a QPAIR field in the message, where the QPAIR is a field in a ROCEV2 message used in the ROCE network, and may be understood as a character string to identify a service flow.
Based on the congestion isolation configuration in the above embodiment, when the switch receives the service packet and detects that the identifier of the service flow to which the received service packet belongs matches the identifier of the service flow in the matching entry, the received service packet is stored in the congestion reservation queue.
As another example, the matching items of the congestion isolation configuration generated by the controller in this step 201 may be the traffic flow identifier and the forwarding rate threshold,
when the matching item comprises the service flow identification and the forwarding rate threshold value of the congestion service flow, when the switch receives a service message, the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item, and the forwarding rate of the service flow to which the service message matched with the service flow identification in the matching item belongs is detected to be greater than or equal to the forwarding rate threshold value, the received service message is stored in the congestion reservation queue.
For the above two congestion isolation configurations, since the controller does not continuously receive the CNP packet carrying the service flow identifier of the congested service flow when the congestion of the congested service flow is not relieved, in order to avoid that the controller continuously issues the congestion isolation configuration, as an embodiment, a delay time may be set, and after issuing the congestion isolation configuration, even if the controller receives the CNP packet carrying the service flow identifier of the congested service flow, the congestion isolation configuration for the congested service flow is not issued again.
Further, after the controller issues the congestion isolation configuration, the controller does not receive the CNP packet carrying the service flow identifier of the congested service flow within the specified time, and may issue a congestion isolation configuration release command to the switch, so that the switch stores the service packet of the congestion-relieved congested service flow by using the packet forwarding queue after the congestion of the congested service flow is released, so as to further ensure that the congestion reservation queue does not store the service packet of the uncongested service flow, thereby implementing the isolation between the congested service flow and the normal service flow without congestion.
As another embodiment, in this embodiment, the controller may also set an aging time when generating the congestion isolation configuration for the congested traffic flow, and when issuing the congestion isolation configuration, issue the aging time of the congestion isolation configuration to the switch. In the aging time, even if the controller receives the CNP packet carrying the service flow identifier of the congested service flow, the congestion isolation configuration for the congested service flow is not issued.
Further, the congestion isolation configuration will be automatically released from the switch when the time at which the congestion isolation configuration is received at the switch equals the aging time. For example, when the aging time is N seconds, N is greater than 0, and when the time for receiving the congestion isolation configuration at the switch reaches N seconds, the switch deletes the congestion isolation configuration reaching the aging time from the local device. Meanwhile, when the controller detects that the issued congestion isolation configuration for the congested service flow reaches the aging time, if a CNP message carrying the service flow identifier of the congested service flow is received, the controller will continue to issue the congestion isolation configuration for the congested service flow according to the CNP message.
Thus, the flow shown in fig. 2 is completed.
It should be noted that, in this embodiment of the present application, after the switch stores the received service packet of the congested service flow in the congestion reservation queue for forwarding, if the cache occupancy at the port of the switch that receives the congested flow continues to increase and exceeds a preset second water line value (the setting of the second water line value may refer to the first water line value, and the second water line value is higher than the first water line value), the switch may be triggered to reduce the rate of sending the service packet through the congestion flow queue, so as to prevent packet loss caused by congestion, and specifically, the switch may be implemented by setting a PFC function. At this time, since the congestion reserved queue isolates the congested traffic flow from the normal traffic flow without congestion, reducing the rate at which the congestion traffic queue sends the traffic packet through the congestion traffic queue does not affect the normal traffic flow without congestion.
As can be seen from the process shown in fig. 2, in this embodiment, after receiving a congestion isolation configuration issued by the controller, the switch may isolate the congested service flow from a normal service flow without congestion according to the congestion isolation configuration, where the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP, and the reverse congestion notification message CNP is triggered when another server (e.g., a destination of the congested service flow) receives a service message with a congestion flag. The scheme provided by the application isolates the congested service flow from the normal service flow without congestion, so that the transmission of the normal service flow without congestion can be prevented from being influenced when the congestion in the congested service flow is further eliminated.
Another method embodiment provided by the present application is described below with reference to fig. 3:
referring to fig. 3, fig. 3 is a flowchart of a method for traffic congestion isolation applied to a server according to an embodiment of the present application. As an example, the method shown in fig. 3 may be applied to the rock network architecture shown in fig. 6.
As shown in fig. 3, the process may include the following steps:
It should be noted that, in this embodiment, a server that generates a CNP packet is different from a server applied in this embodiment, where the server that generates the CNP packet is a destination server of a service packet of a congested service flow, and the server applied in this embodiment is a source server of the service packet of the congested service flow.
In this embodiment, because the controller and the server are connected, the CNP message received by the controller may be a CNP message that is sent by the switch to the controller using a configured mirror function (e.g., an ERSPAN function) in the rock network, or a CNP message that is sent by the destination server directly to the controller.
As an embodiment, the congestion isolation configuration issued by the controller in this step 301 may include the following:
resetting the priority value set for the congestion traffic flow, wherein the reset priority value is lower than the priority value set before the congestion traffic flow; the reset priority value is matched with a congestion reservation queue on a switch connected with the first server, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows without congestion are stored in the message forwarding queue.
Based on the congestion isolation configuration, the source end server of the congested service flow can modify the existing priority value in the service packet into the reset priority value and forward the modified priority value aiming at the service packet to be forwarded in the server and belonging to the congested service flow, so that the switch stores the service packet to the congestion reservation queue according to the reset priority value carried by the service packet when receiving the service packet.
For example, the priority value carried in the service message in this embodiment is a priority information field in the IP message: a DSCP (Differentiated Services Code Point) field. In the embodiment of the application, when the message forwarding queue and the congestion reservation queue on the switch are configured, DSCP values corresponding to the message forwarding queue and the congestion reservation queue are configured at the same time. When the switch receives the service message, the switch searches the queue corresponding to the DSCP value according to the DSCP value carried in the service message, and stores the received service message to the queue corresponding to the DSCP value for forwarding.
It should be noted that, in this embodiment, the generation process and the forwarding process of the CNP packet and the service packet carrying the congestion flag, and other contents may refer to the description in the method embodiment shown in fig. 2, and are not described in detail in this application.
The flow shown in fig. 3 is completed.
As can be seen from the flow shown in fig. 3, in this embodiment, after receiving a congestion isolation configuration issued by a controller, a server (i.e., a source end of a congested service flow) may isolate the congested service flow from a normal service flow without congestion according to the congestion isolation configuration, where the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP, and the reverse congestion notification message CNP is triggered when another server (e.g., a destination end of a congested service flow) receives a service message with a congestion flag. The scheme provided by the application isolates the congested service flow from the normal service flow without congestion, so that the transmission of the normal service flow without congestion can be prevented from being influenced when the congestion in the congested service flow is further eliminated.
The method provided by the present application is described below by two examples:
example 1:
this embodiment 1 is applied to the rock networking architecture shown in fig. 4, where in fig. 4, the DUT device is a switch, the Server is a Server, and the Controller is a Controller, where there is a connection between the switch and the Controller, and there is a connection between the switch and the Server. All the devices are configured with an ECN function and a PFC function, each switch is configured with an ERSPAN mirror function and two different queues, wherein one queue is a message forwarding queue for storing service messages of all service flows which are not congested initially, the message forwarding queue is stored for forwarding when the switch receives the service messages of a service flow 1, a service flow 2 and a service flow 3 initially, the other queue is a congestion reservation queue for storing the service messages of the congested service flows when the congested service flows occur, the congestion reservation queue can not store any service messages of the service flows initially, and the priority of the congestion reservation queue is lower than that of the message forwarding queue.
This embodiment 1 is described below by a flowchart shown in fig. 5:
Taking traffic flow 1 and traffic flow 2 forwarded by DUT3 as an example, when detecting that the buffer occupancy of Port4 Port and Port5 Port on DUT3 reaches the first water line value set for triggering the ECN function, respectively, it indicates that Port6 Port has been congested, and at this time, traffic flow 1 and traffic flow 2 forwarded by DUT3 are congested traffic flows. After the ECN function is triggered, the DUT3 modifies the ECN field carried in the traffic packets of the traffic flow 1 and the traffic flow 2 to be forwarded to the ECN11 before forwarding the traffic packets of the traffic flow 1 and the traffic flow 2 to be forwarded by the device, and sends the modified traffic packet carrying the congestion flag ECN11 to the Server 3.
In this embodiment 1, after receiving the service packet carrying the ECN11 field, the Server3 (i.e., the second Server) triggers the Server3 to generate a CNP packet. When the Server3 generates the CNP message, the decapsulation congestion message obtains a QPAIR value carried in the congestion message (the QPAIR value is a service flow identifier), and carries the QPAIR value in the CNP message. Further, after generating the CNP message, the Server3 returns the CNP message to the DUT 3.
Optionally, when the DUT3 receives the message at Port6, the received message is matched with the OPCODE field of the message, and when the received message is matched with the OPCODE field of 129, the message is determined to be a CNP message, and the DUT3 is triggered to copy the received CNP message using the configured ERSPAN mirror image function, and send the copied CNP message to the Controller.
In step 504, the controller issues congestion isolation configuration for isolating the congested service flow from normal service flows that are not congested to all switches connected to the controller according to the service flow identifier of the congested service flow carried in the received CNP message.
In this embodiment 1, after receiving the CNP message and identifying that the CNP message is used to notify that congestion occurs in traffic flow 1 and traffic flow 2 according to a QPAIR field carried in the CNP message, the Controller issues congestion isolation configuration to the DUT1, the DUT2, and the DUT3 for the traffic flow 1 and the traffic flow 2.
And 505, the switch receives the congestion isolation configuration issued by the controller, and stores the received service message to the congestion reservation queue when receiving the service message matched with the matching item in the congestion isolation configuration.
After receiving the congestion isolation configuration, if the congestion isolation configuration is the congestion isolation configuration of the traffic flow identifier in the embodiment of the method shown in fig. 2, after receiving the congestion isolation configuration, if the QPAIR value carried in the traffic message matches with the traffic flow identifier of the traffic flow 1 or the traffic flow 2, the DUT1, the DUT2, and the DUT3 store the traffic message in their respective congestion reservation queues for forwarding.
Or, if the matching items of the congestion isolation configuration received by the DUT1, DUT2, and DUT3 are the traffic flow identifier and the forwarding rate threshold of the congested traffic flow, when receiving a traffic packet, if the QPAIR value carried by the traffic packet matches the traffic flow identifier of the traffic flow 1 or traffic flow 2, and the forwarding rate of the traffic flow to which the traffic packet belongs exceeds the forwarding rate threshold, storing the traffic packet in the respective congestion reservation queue for forwarding.
In this embodiment 1, the traffic flow 1 and the traffic flow 2 with the congested traffic flow are finally forwarded through the congestion reservation queue, so that when it is detected that the buffer occupancy of the Port4 Port and/or the Port5 Port on the DUT3 reaches the second water line value that is set for each of them and triggers the PFC function, the congestion generated by the traffic flow 1 and the traffic flow 2 is relieved through the PFC function, and the transmission of the traffic flow 3 is not affected.
Example 2:
the embodiment 2 is applied to the rock networking architecture shown in fig. 6, the controller and the server of the networking architecture shown in fig. 6 are connected, and other configurations of the devices are the same as those of the embodiment 1.
The present embodiment 2 is described below by a flowchart shown in fig. 7:
In this embodiment 2, similarly taking congestion of the traffic flow 1 and the traffic flow 2 forwarded by the DUT3 as an example, in this embodiment 2, the steps before the Server3 (i.e., the second Controller) generates the CNP message may be consistent with those in embodiment 1, but after the Server3 generates the CNP message, the CNP message may be returned to the DUT3, so that the DUT3 sends the CNP message to the Controller, or the CNP message may be directly sent to the CNP message through the connection between the Controller and the Server 3.
In this embodiment, after receiving the CNP packet, the Controller identifies the service flows with congestion as service flow 1 and service flow 2 according to the QPAIR field carried in the CNP packet, and further finds that the source end Server of the service flow 1 is Server1 and the source end Server of the service flow 1 is Server2 according to the QPAIR value carried in the CNP packet.
Optionally, the existing priority value in the service packet is modified to the reset priority value, which may be that a DSCP value (i.e., a priority value) corresponding to an existing packet forwarding queue in the service packet is modified to a DSCP value corresponding to a congestion reservation queue.
In this embodiment 2, by directly modifying the modified priority value in the service packet of the congested service flow at the source end server of the congested service flow, when the switch receives the service packet, the service packet is stored in the congestion reservation queue according to the reset priority value carried in the service packet, and finally, the service packets of the congested service flow 1 and the congested service flow 2 can be forwarded on the switch through the congestion reservation queue, so that when it is detected that the buffer occupancy of the Port4 Port and the Port5 Port on the DUT3 reaches the second water line value of the set PFC-triggered function, the transmission of the service flow 3 is not affected when the congestion generated by the service flow 1 and the service flow 2 is relieved through the PFC function.
The method provided by the embodiment of the application is described above. The following describes the apparatus provided in the embodiments of the present application:
referring to fig. 8, fig. 8 is a schematic diagram of an apparatus for implementing traffic congestion isolation according to an embodiment of the present application, where the embodiment of the apparatus is applied to a switch. The device includes:
a CNP message uploading unit 801, configured to, when receiving a reverse congestion notification message, a CNP message, send the CNP message to a controller, where the CNP message is triggered by a server when receiving a service message carrying a congestion flag; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion.
A congestion traffic flow isolation unit 802, configured to receive a congestion isolation configuration sent by the controller, and isolate the congestion traffic flow from a normal traffic flow without congestion according to the congestion isolation configuration.
Optionally, the congestion isolation configuration includes: matching items and actions; the matching item is the service flow identification or the service flow identification and a forwarding rate threshold value; the action is stored to a congestion reservation queue, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows which are not congested are stored to the message forwarding queue.
The congestion traffic flow isolation unit 802, according to the congestion isolation configuration, isolating the congested traffic flow from the normal traffic flow without congestion includes:
and when the matching item only comprises the service flow identification, if a service message is received, storing the received service message to the congestion reservation queue when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item.
And when the matching item comprises the service flow identification and the forwarding rate threshold value, if a service message is received, when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item, and the forwarding rate of the service flow to which the service message matched with the service flow identification in the matching item belongs is detected to be greater than or equal to the forwarding rate threshold value, storing the received service message to the congestion reservation queue.
Optionally, the CNP message uploading unit 801 is further configured to receive a mirror configuration sent by the controller, where the mirror configuration is used to indicate that a CNP message is mirrored to the controller.
The CNP message uploading unit 801 uploading the CNP message to a controller includes:
and mirroring the received CNP message according to the mirror image configuration, and sending the CNP message obtained after mirroring to a controller.
Thus, the structure of the embodiment of the apparatus shown in FIG. 8 is completed.
Referring to fig. 9, fig. 8 is a schematic diagram of another apparatus for implementing traffic congestion isolation according to an embodiment of the present application, where the embodiment of the apparatus is applied to a server:
a congestion isolation configuration receiving unit 901, configured to receive a congestion isolation configuration sent by a controller; the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP message; the CNP message is triggered by a second server when receiving a service message carrying a congestion mark, and the first server is a source end of the service message; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion.
The congestion traffic flow isolation unit 902 isolates the congestion traffic flow from a normal traffic flow without congestion according to the congestion isolation configuration.
Optionally, the congestion isolation configuration includes:
resetting the priority value set for the congestion traffic flow, wherein the reset priority value is lower than the priority value set before the congestion traffic flow; the reset priority value is matched with a congestion reservation queue on a switch connected with the first server, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows without congestion are stored in the message forwarding queue.
The congestion traffic flow isolation unit 902, according to the congestion isolation configuration, isolating the congestion traffic flow from the normal traffic flow without congestion includes:
and aiming at the service message to be forwarded, which belongs to the congestion service flow, modifying the existing priority value in the service message into the reset priority value and forwarding the service message, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
Thus, the structure of the embodiment of the apparatus shown in FIG. 9 is completed.
The method and the device provided by the embodiment of the application are described above. The following describes a system provided in an embodiment of the present application:
the traffic congestion isolation system provided by the application comprises: the switch, the controller and the server are connected, and the switch and the server are connected, so that the congestion service flow and the normal service flow without congestion can be isolated, and the normal service flow without congestion is prevented from being influenced when the congestion of the congestion service flow is solved.
The switch receives a reverse congestion notification message (CNP) message, and sends the CNP message to a controller, wherein the CNP message is triggered by a server when receiving a service message carrying a congestion mark; and the CNP message carries the service flow identification of the congestion service flow to which the service message belongs.
And when receiving the CNP message sent by the switch, the controller sends congestion isolation configuration to the switch, wherein the congestion isolation configuration is used for isolating the congested service flow from the normal service flow without congestion.
And when the switch receives the congestion isolation configuration sent by the controller, isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration.
Or, if a connection also exists between the controller and the server in the traffic congestion isolation system provided by the present application, when receiving a reverse congestion notification message CNP, the controller issues a congestion isolation configuration to the server, where the congestion isolation configuration is used to isolate the congested traffic flow from a normal traffic flow that is not congested; the CNP message is triggered by another server when receiving a service message carrying a congestion mark, the controller issues a server to which congestion isolation configuration is allocated as a source end of the service message, and the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs.
When the server receives the congestion isolation configuration sent by the controller, the existing priority value in the service message to be forwarded, which belongs to the congestion service flow, is modified into the reset priority value and the reset priority value is forwarded, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
The above examples are merely for convenience of understanding, and the embodiments of the present application are not particularly limited.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A traffic congestion isolation method is applied to a switch and comprises the following steps:
when receiving a reverse congestion notification message (CNP), sending the CNP to a controller, wherein the CNP is triggered by a server when receiving a service message carrying a congestion mark; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and receiving congestion isolation configuration sent by the controller, and isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration.
2. The method of claim 1, wherein the congestion isolation configuration comprises: matching items and actions; the matching item is the service flow identification or the service flow identification and a forwarding rate threshold value; the action is stored to a congestion reservation queue, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows which are not congested are stored to the message forwarding queue;
the step of isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration comprises:
when the matching item only comprises the service flow identification, if a service message is received, storing the received service message to the congestion reservation queue when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item;
and when the matching item comprises the service flow identification and the forwarding rate threshold value, if a service message is received, when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item, and the forwarding rate of the service flow to which the service message matched with the service flow identification in the matching item belongs is detected to be greater than or equal to the forwarding rate threshold value, storing the received service message to the congestion reservation queue.
3. The method of claim 1, wherein prior to performing the method, further comprising:
receiving mirror image configuration sent by the controller, wherein the mirror image configuration is used for indicating that a CNP message is mirrored to the controller;
the uploading the CNP message to a controller comprises:
and mirroring the received CNP message according to the mirror image configuration, and sending the CNP message obtained after mirroring to a controller.
4. A traffic congestion isolation method applied to a first server comprises the following steps:
receiving congestion isolation configuration sent by a controller; the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP message; the CNP message is triggered by a second server when receiving a service message carrying a congestion mark, and the first server is a source end of the service message; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration.
5. The method of claim 4, wherein the congestion isolation configuration comprises:
resetting the priority value set for the congestion traffic flow, wherein the reset priority value is lower than the priority value set before the congestion traffic flow; the reset priority value is matched with a congestion reservation queue on a switch connected with the first server, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows without congestion are stored in the message forwarding queue;
the step of isolating the congested service flow from the normal service flow without congestion according to the congestion isolation configuration comprises:
and aiming at the service message to be forwarded, which belongs to the congestion service flow, modifying the existing priority value in the service message into the reset priority value and forwarding the service message, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
6. A traffic congestion isolation device, applied to a switch, comprises:
a CNP message uploading unit, configured to, when a reverse congestion notification message CNP message is received, upload the CNP message to a controller, where the CNP message is triggered by a server when receiving a service message carrying a congestion flag; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and the congestion service flow isolation unit is used for receiving congestion isolation configuration sent by the controller and isolating the congestion service flow from normal service flows which are not congested according to the congestion isolation configuration.
7. The apparatus of claim 6, wherein the congestion isolation configuration comprises: matching items and actions; the matching item is the service flow identification or the service flow identification and a forwarding rate threshold value; the action is stored to a congestion reservation queue, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows which are not congested are stored to the message forwarding queue;
the congestion traffic flow isolation unit isolating the congestion traffic flow from the normal traffic flow without congestion according to the congestion isolation configuration comprises:
when the matching item only comprises the service flow identification, if a service message is received, storing the received service message to the congestion reservation queue when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item;
and when the matching item comprises the service flow identification and the forwarding rate threshold value, if a service message is received, when the identification of the service flow to which the received service message belongs is matched with the service flow identification in the matching item, and the forwarding rate of the service flow to which the service message matched with the service flow identification in the matching item belongs is detected to be greater than or equal to the forwarding rate threshold value, storing the received service message to the congestion reservation queue.
8. A traffic congestion isolation apparatus applied to a first server, comprising:
a congestion isolation configuration receiving unit, configured to receive a congestion isolation configuration issued by the controller; the congestion isolation configuration is issued when the controller receives a reverse congestion notification message CNP message; the CNP message is triggered by a second server when receiving a service message carrying a congestion mark, and the first server is a source end of the service message; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs, so that the controller issues congestion isolation configuration, wherein the congestion isolation configuration is used for isolating the congestion service flow from a normal service flow without congestion;
and the congestion service flow isolation unit is used for isolating the congestion service flow from the normal service flow without congestion according to the congestion isolation configuration.
9. The apparatus of claim 8, wherein the congestion isolation configuration comprises:
resetting the priority value set for the congestion traffic flow, wherein the reset priority value is lower than the priority value set before the congestion traffic flow; the reset priority value is matched with a congestion reservation queue on a switch connected with the first server, the congestion reservation queue is different from a set message forwarding queue, and initially, service messages of all service flows without congestion are stored in the message forwarding queue;
the congestion traffic flow isolation unit isolating the congestion traffic flow from the normal traffic flow without congestion according to the congestion isolation configuration comprises:
and aiming at the service message to be forwarded, which belongs to the congestion service flow, modifying the existing priority value in the service message into the reset priority value and forwarding the service message, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
10. A traffic congestion isolation system, the system comprising: the system comprises a switch, a controller and a server;
the switch receives a reverse congestion notification message (CNP) message, and sends the CNP message to a controller, wherein the CNP message is triggered by a server when receiving a service message carrying a congestion mark; the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs;
when the controller receives a CNP message sent by the switch, the controller sends congestion isolation configuration to the switch, wherein the congestion isolation configuration is used for isolating the congested service flow from a normal service flow without congestion;
when the switch receives the congestion isolation configuration sent by the controller, the switch isolates the congested service flow from the normal service flow without congestion according to the congestion isolation configuration;
alternatively, the first and second electrodes may be,
when the controller receives a reverse congestion notification message (CNP), a congestion isolation configuration is issued to a server, wherein the congestion isolation configuration is used for isolating the congested service flow from a normal service flow without congestion; the CNP message is triggered by another server when receiving a service message carrying a congestion mark, the controller issues a server to which congestion isolation is configured as a source end of the service message, and the CNP message carries a service flow identifier of a congestion service flow to which the service message belongs;
when the server receives the congestion isolation configuration sent by the controller, the existing priority value in the service message to be forwarded, which belongs to the congestion service flow, is modified into the reset priority value and the reset priority value is forwarded, so that the switch stores the service message to the congestion reservation queue according to the reset priority value carried by the service message when receiving the service message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110336539.4A CN113114578B (en) | 2021-03-29 | 2021-03-29 | Traffic congestion isolation method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110336539.4A CN113114578B (en) | 2021-03-29 | 2021-03-29 | Traffic congestion isolation method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113114578A true CN113114578A (en) | 2021-07-13 |
| CN113114578B CN113114578B (en) | 2022-11-25 |
Family
ID=76712587
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110336539.4A Active CN113114578B (en) | 2021-03-29 | 2021-03-29 | Traffic congestion isolation method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113114578B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174477A (en) * | 2022-06-29 | 2022-10-11 | 无锡芯光互连技术研究院有限公司 | Congestion control method and system based on priority flow control |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150334024A1 (en) * | 2012-04-20 | 2015-11-19 | Jeffrey Clifford Mogul | Controlling Data Rates of Data Flows Based on Information Indicating Congestion |
| CN108449279A (en) * | 2016-12-13 | 2018-08-24 | 中国移动通信有限公司研究院 | Jamming control method and device |
| US20200021532A1 (en) * | 2018-07-10 | 2020-01-16 | Cisco Technology, Inc. | Automatic rate limiting based on explicit network congestion notification in smart network interface card |
| CN111490943A (en) * | 2019-01-29 | 2020-08-04 | 中兴通讯股份有限公司 | Congestion control method, terminal and readable storage medium |
| US20200287833A1 (en) * | 2019-03-08 | 2020-09-10 | Hewlett Packard Enterprise Development Lp | Cost effective congestion isolation for lossless ethernet |
| CN111683017A (en) * | 2020-05-26 | 2020-09-18 | 中国人民解放军国防科技大学 | Multi-level congestion control method, device, system and medium in high-speed interconnection network |
-
2021
- 2021-03-29 CN CN202110336539.4A patent/CN113114578B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150334024A1 (en) * | 2012-04-20 | 2015-11-19 | Jeffrey Clifford Mogul | Controlling Data Rates of Data Flows Based on Information Indicating Congestion |
| CN108449279A (en) * | 2016-12-13 | 2018-08-24 | 中国移动通信有限公司研究院 | Jamming control method and device |
| US20200021532A1 (en) * | 2018-07-10 | 2020-01-16 | Cisco Technology, Inc. | Automatic rate limiting based on explicit network congestion notification in smart network interface card |
| CN111490943A (en) * | 2019-01-29 | 2020-08-04 | 中兴通讯股份有限公司 | Congestion control method, terminal and readable storage medium |
| US20200287833A1 (en) * | 2019-03-08 | 2020-09-10 | Hewlett Packard Enterprise Development Lp | Cost effective congestion isolation for lossless ethernet |
| CN111683017A (en) * | 2020-05-26 | 2020-09-18 | 中国人民解放军国防科技大学 | Multi-level congestion control method, device, system and medium in high-speed interconnection network |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174477A (en) * | 2022-06-29 | 2022-10-11 | 无锡芯光互连技术研究院有限公司 | Congestion control method and system based on priority flow control |
| CN115174477B (en) * | 2022-06-29 | 2024-04-05 | 无锡芯光互连技术研究院有限公司 | Congestion control method and system based on priority flow control |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113114578B (en) | 2022-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11646967B2 (en) | Packet control method and network apparatus | |
| US11032205B2 (en) | Flow control method and switching device | |
| CN108989235B (en) | Message forwarding control method and device | |
| CN111788803B (en) | Flow management in a network | |
| US10965604B2 (en) | Deadlock avoidance in leaf-spine networks | |
| US20060203730A1 (en) | Method and system for reducing end station latency in response to network congestion | |
| WO2021244240A1 (en) | Network congestion control method and apparatus, device, system, and storage medium | |
| US10110482B2 (en) | Technique for network service availability | |
| US11005770B2 (en) | Listing congestion notification packet generation by switch | |
| US20150215224A1 (en) | Positive feedback ethernet link flow control for promoting lossless ethernet | |
| WO2013082819A1 (en) | Layer 2 network loop processing method, apparatus and network device | |
| WO2022105932A1 (en) | Pfc pause packet and processing method therefor | |
| CN107547442B (en) | Data transmission buffer queue distribution method and device | |
| WO2021083160A1 (en) | Data transmission method and apparatus | |
| US10728156B2 (en) | Scalable, low latency, deep buffered switch architecture | |
| WO2013104178A1 (en) | Ethernet flow control device and method based on microwave transmission | |
| CN113114578B (en) | Traffic congestion isolation method, device and system | |
| JP2008118281A (en) | Communication device | |
| US10749803B1 (en) | Enhanced congestion avoidance in network devices | |
| CN108243117B (en) | Flow monitoring method and device and electronic equipment | |
| CN107231316B (en) | Message transmission method and device | |
| US7009989B2 (en) | Forwarding ordered data packets with less delay | |
| CN110336759B (en) | RDMA (remote direct memory Access) -based protocol message forwarding method and device | |
| CN112437017A (en) | Data flow control system, method, device, equipment and medium | |
| JPH10285168A (en) | Path change-over system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |