Transferring congestion notifications

Patent metadata

Field	Value
Publication number	US-2026046191-A1
Application number	US-202418796767-A
Country	US
Kind code	A1
Filing date	Aug 7, 2024
Priority date	Aug 7, 2024
Publication date	Feb 12, 2026
Grant date	—

Abstract

Systems, devices, and methods are provided. In one example, a system is described that includes circuits to receive a packet associated with a source, determine a device that received the packet is congested, in response to determining the switch that received the packet is congested, generate a congestion notification, transfer the congestion notification to a second device, wherein the second device is between the device and the source, set a timer, and in response to the congestion in the device not being resolved when the timer ends, generate and send a new congestion notification.

First claim

What is claimed is:

1 . A system comprising one or more circuits to:
receive a packet associated with a source; determine a switch that received the packet is congested; in response to determining the switch that received the packet is congested, generate a congestion notification; transfer the congestion notification to a second switch, wherein the second switch is between the switch and the source; set a timer; and in response to congestion in the switch not being resolved when the timer ends, generate and send a new congestion notification.

2 . The system of claim 1 , wherein the one or more circuits are further to:
process the congestion notification and re-route network traffic based on the congestion notification; and generate and transfer a second congestion notification to a third switch, wherein the third switch is between the second switch and the source.

3 . The system of claim 2 , wherein the one or more circuits are further to:
process the second congestion notification and re-route network traffic based on the second congestion notification; generate a third congestion notification; and transfer the third congestion notification to a fourth switch, wherein the fourth switch is between the third switch and the source.

4 . The system of claim 3 , wherein when the third switch is directly connected to the source, the third congestion notification is not generated or transferred.

5 . The system of claim 1 , wherein the one or more circuits are further to:
generate the congestion notification in response to determining at least one port in the switch and an associated bandwidth are below a threshold.

6 . The system of claim 1 , wherein congestion in the switch is determined based on one or more of a queue latency and a queue occupancy.

7 . The system of claim 2 , wherein re-routing the network traffic comprises using adaptive routing to re-route the network traffic.

8 . The system of claim 1 , wherein the congestion notification comprises an Adaptive Routing Notification (ARN).

9 . A device comprising one or more circuits to:
receive a congestion notification from a second device, wherein the congestion notification is addressed to a source node, and wherein the device is between the second device and the source node; process the congestion notification and re-route network traffic based on the congestion notification; generate a second congestion notification; and transfer the second congestion notification to a third device, wherein the second congestion notification is addressed to the source node, and wherein the third device is between the second device and the source node.

10 . The device of claim 9 , wherein when the device is connected to the source node, the second congestion notification is not generated or transferred.

11 . The device of claim 9 , wherein the congestion notification is generated in response to determining at least one port in the second device and an associated bandwidth are below a threshold.

12 . The device of claim 9 , wherein congestion in the second device is determined based on one or more of a queue latency and a queue occupancy.

13 . The device of claim 9 , wherein re-routing the network traffic comprises using adaptive routing to re-route the network traffic.

14 . The device of claim 9 , wherein the congestion notification comprises an Adaptive Routing Notification (ARN).

15 . A network comprising:
a first device comprising one or more circuits to:
receive a congestion notification from a second device, wherein the congestion notification is addressed to a source node, and wherein the first device is between the second device and the source node;
process the congestion notification and re-route network traffic based on the congestion notification;
generate a second congestion notification; and
transfer the second congestion notification to a third device, wherein the second congestion notification is addressed to the source node, and wherein the third device is between the first device and the source node.

16 . The network of claim 15 , wherein when the first device is connected to the source node, the second congestion notification is not generated or transferred.

17 . The network of claim 15 , wherein the congestion notification is generated in response to determining at least one port in the second device and an associated bandwidth are below a threshold.

18 . The network of claim 15 , wherein congestion in the second device is determined based on one or more of a queue latency and a queue occupancy.

19 . The network of claim 15 , wherein re-routing the network traffic comprises using adaptive routing to re-route the network traffic.

20 . The network of claim 15 , wherein the congestion notification comprises an Adaptive Routing Notification (ARN).

Assignees

• Mellanox Technologies Ltd

Inventors

• Beracha Eran Gil
• Mey-Tal Gil
• Mund Tal

Classifications

• H04L47/11

  Identifying congestion · CPC title

• H04L41/06 Primary

  Management of faults, events, alarms or notifications · CPC title

• H04L47/125 Primary

  by balancing the load, e.g. traffic engineering · CPC title