CONGESTION AVOIDANCE IN A NETWORK DEVICE

• US 20200136982A1
• Filed: 12/23/2019
• Published: 04/30/2020
• Est. Priority Date: 05/18/2016
• Status: Active Grant

• Current Assignee: Marvell Israel Limited (Marvell Technology Group Limited)
• Original Assignee: Marvell Israel Limited (Marvell Technology Group Limited)
• Inventors: MAYER-WOLF, Ilan, LEIB, Zvi Shmilovici, ARAD, Carmi
• Granted Patent: US 11,005,769 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/29 using a combination of thresholds
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames
• CPC Class Codes: H04L 49/9005 using dynamic buffer space allocation

Abstract

A packet processor of a network device determines an amount of free buffer space in a buffer memory currently available for buffering packets, and dynamically determines a value of a threshold for triggering a particular traffic management operation with respect to a packet, to dynamically adjust the value of the threshold based at least in part on a changing amount of free buffer space available for buffering packets in the buffer memory. The packet processor determines, based on a comparison between i) a current fill level of a particular transmit queue in which the packet is to be enqueued and ii) the dynamically adjusted value of the threshold, whether the particular traffic management operation is to be triggered with respect to the packet. When the particular traffic management operation is to be triggered, the packet processor performs the particular traffic management operation with respect to the packet.

Claims

1. A method for managing traffic flow to a network device, the method comprising:

receiving, at a packet processor of the network device, a packet received from a network;

determining, with the packet processor, a particular transmit queue, among a plurality of transmit queues in a buffer memory, in which the packet is to be enqueued for subsequent transmission from the network device;

determining, with the packet processor, an amount of free buffer space currently available for buffering packets in the buffer memory;

dynamically determining, with the packet processor based at least in part on the amount of free buffer space currently available for buffering packets in the buffer memory, a value of a threshold for triggering a particular traffic management operation with respect to the packet, to dynamically adjust the value of the threshold based at least in part on a changing amount of free buffer space available for buffering packets in the buffer memory;

determining, with the packet processor based on a comparison between i) a current fill level of the particular transmit queue in which the packet is to be enqueued and ii) the dynamically adjusted value of the threshold, whether the particular traffic management operation is to be triggered with respect to the packet; and

when it is determined that the particular traffic management operation is to be triggered, performing, with the packet processor, the particular traffic management operation with respect to the packet.

2. The method of claim 1, further comprising determining, with the packet processor, a flow to which the packet belongs, wherein dynamically determining the value of the threshold includes:

determining, based on the flow to which the packet belongs, one or more flow-specific parameters to be used for determining the value of the threshold, and

determining the value of the threshold further using the one or more flow-specific parameters.

3. The method of claim 2, wherein determining the one or more flow-specific parameters comprises retrieving the one or more flow-specific parameters from a memory.

4. The method of claim 2, wherein determining the one or more flow-specific parameters comprises determining one or both of (i) a guaranteed dynamic threshold for the flow to which the packet belongs and (ii) an allocation factor for allocation of free buffer space in the buffer memory to the flow to which the packet belongs.

5. The method of claim 2, wherein dynamically determining the value of the threshold comprises determining the value of the threshold based on (i) a guaranteed amount of buffer space allocated for the flow and (ii) a dynamically calculated amount of buffer space allocated to the flow, the dynamically calculated amount of buffer space being calculated based on a measure of the amount of free buffer space currently available for buffering packets in the buffer memory.

6. The method of claim 1, wherein determining the amount of free buffer space currently available for buffering packets in the buffer memory comprises determining the amount of free buffer space based on a mathematical difference between i) a preconfigured value of a total amount of buffer space in the buffer memory and ii) a value of a counter corresponding to an amount of total buffer space currently used by queues in the buffer memory.

7. The method of claim 1, wherein:

the buffer memory is configured to queue packets to be transmitted via ones of ports among a plurality of ports of the network device; and

determining the amount of free buffer space comprises determining the amount of free buffer space based on a mathematical difference between i) a preconfigured value of a total amount of buffer space in the buffer memory and ii) a value of a counter corresponding to an amount of a buffer space currently used by a subset of queues, among a set of queues in the buffer memory, the subset of queues corresponding to a particular port, among the plurality of ports, via which the packet is to transmitted.

8. The method of claim 1, further comprising determining, with the packet processor, a particular port, among a plurality of ports of the network device, via which the packet is to be transmitted from the network device, wherein dynamically determining the value of the threshold includes:

determining, based on the particular port via which the packet is to be transmitted, one or more port-specific parameters to be used for determining the value of the threshold; and

determining the value of the threshold further using the one or more port-specific parameters.

9. The method of claim 8, wherein determining the one or more port-specific parameters comprises retrieving the one or more port-specific parameters from a memory.

10. The method of claim 1, wherein dynamically determining the value of the threshold for triggering the particular traffic management operation with respect to the packet comprises dynamically determining the value of the threshold for triggering one of:

(i) a tail-drop operation to drop the packet,

(ii) an explicit congestion notification (ECN) operation to include ECN marking in a header of the packet,

(iii) transmission of a flow control message based on the packet, and

(iv) mirroring of the packet to an analyzer.

11. A network device, comprising:

a buffer memory configured to queue packets for subsequent transmission from the network device;

a packet processor coupled to the buffer memory, the packet processor configured to receive a packet from a network;

a threshold determination engine configured to;

determine a particular transmit queue, among a plurality of transmit queues in the buffer memory, in which the packet is to be enqueued for subsequent transmission from the network device,

determine an amount of free buffer space currently available for buffering packets in the buffer memory, and

dynamically determine, based at least in part on the amount of free buffer space currently available for buffering packets in the buffer memory, a value of a threshold for triggering a particular traffic management operation with respect to the packet, to dynamically adjust the value of the threshold based at least in part on a changing amount of free buffer space available for buffering packets in the buffer memory; and

a congestion avoidance trigger engine configured to;

determine, based on a comparison between i) a current fill level of the particular transmit queue in which the packet is to be enqueued and ii) the dynamically adjusted value of the threshold, whether the particular traffic management operation is to be triggered with respect to the packet, and

when it is determined that the particular traffic management operation is to be triggered, trigger the particular traffic management operation with respect to the packet.

12. The network device of claim 11, wherein:

the packet processor is further configured to determine a flow to which the packet belongs; and

the threshold determination engine is configured to;

determine, based on the flow to which the packet belongs, one or more flow-specific parameters to be used for determining the value of the threshold, and

determine the value of the threshold further using the one or more flow-specific parameters.

13. The network device of claim 12, wherein the threshold determination engine is configured to retrieve the one or more flow-specific parameters from a memory.

14. The network device of claim 12, wherein the threshold determination engine is configured to determine the one or more flow-specific parameters at least by determining one or both of (i) a guaranteed dynamic threshold for the flow to which the packet belongs and (ii) an allocation factor for allocation of free buffer space in the buffer memory to the flow to which the packet belongs.

15. The network device of claim 12, wherein the threshold determination engine is configured to determine the value of the threshold based on (i) a guaranteed amount of buffer space allocated for the flow and (ii) a dynamically calculated amount of buffer space allocated to the flow, the dynamically calculated amount of buffer space being calculated based on a measure of the amount of free buffer space currently available for buffering packets in the buffer memory.

16. The network device of claim 11, wherein the threshold determination engine is configured to determine the amount of free buffer space currently available for buffering packets in the buffer memory based on a mathematical difference between i) a preconfigured value of a total amount of buffer space in the buffer memory and ii) a value of a counter corresponding to an amount of total buffer space currently used by queues in the buffer memory.

17. The network device of claim 11, wherein:

the buffer memory is configured to queue packets to be transmitted via ones of ports among a plurality of ports of the network device; and

the threshold determination engine is configured to determine the amount of free buffer space based on a mathematical difference between i) a preconfigured value of a total amount of buffer space in the buffer memory and ii) a value of a counter corresponding to an amount of buffer space currently used by a subset of queues, among a set of queues in the buffer memory, the subset of queues corresponding to a particular port, among the plurality of ports, via which the packet is to transmitted.

18. The network device of claim 11, wherein:

the packet processor is further configured to determine a particular port, among a plurality of ports of the network device, via which the packet is to be transmitted; and

the threshold determination engine is configured to;

determine, based on the particular port via which the packet is to be transmitted, one or more port-specific parameters to be used for determining the value of the threshold, and

determine the value of the threshold further using the one or more port-specific parameters.

19. The network device of claim 18, wherein the threshold determination engine is configured to retrieve the one or more port-specific parameters from a memory.

20. The network device of claim 11, wherein the threshold determination engine is configured to dynamically determining the value of the threshold for triggering one of:

(i) a tail-drop operation to drop the packet,

(ii) an explicit congestion notification (ECN) operation to include ECN marking in a header of the packet,

(iii) transmission of a flow control message based on the packet, and

(iv) mirroring of the packet to an analyzer.