Abstract:
Hierarchical congestion identification and control hardware supports multi-level congestion control at flow, tenant and virtual machine (VM) levels. Hardware implementation expedites response to congestion notifications and frees-up processor bandwidth. A hierarchy of transmit shapers in a transmit ring scheduler isolate rate adjustments for flows, tenants and VMs. The hierarchy of shapers provide a hierarchy of congestion control nodes to control flows and aggregate flows. Hardware quickly associates congested flows with shapers before or after receiving a congestion notification. The associations may be used by any flow control algorithm to selectively rate-control shapers to control flow rates. Shaper associations and configured states, scheduler configuration, congestion states, thresholds and other flow information may be stored and monitored to filter data flows that need attention and to raise alerts at flow, tenant and VM levels. Congestion control occurs fast and without packet modification, queue or ring switching or queue accumulation.
Abstract:
Hierarchical congestion identification and control hardware supports multi-level congestion control at flow, tenant and virtual machine (VM) levels. Hardware implementation expedites response to congestion notifications and frees-up processor bandwidth. A hierarchy of transmit shapers in a transmit ring scheduler isolate rate adjustments for flows, tenants and VMs. The hierarchy of shapers provide a hierarchy of congestion control nodes to control flows and aggregate flows. Hardware quickly associates congested flows with shapers before or after receiving a congestion notification. The associations may be used by any flow control algorithm to selectively rate-control shapers to control flow rates. Shaper associations and configured states, scheduler configuration, congestion states, thresholds and other flow information may be stored and monitored to filter data flows that need attention and to raise alerts at flow, tenant and VM levels. Congestion control occurs fast and without packet modification, queue or ring switching or queue accumulation.
Abstract:
A network device implementing the subject system for end to end flow control may include at least one processor circuit that may be configured to detect that congestion is being experienced by at least one queue of a port and identify another network device that is transmitting downstream traffic being queued at the at least one queue of the port that is at least partially causing the congestion. The at least one processor circuit may be further configured to generate an end to end flow control message that comprises an identifier of the port, the end to end flow control message indicating that the downstream traffic should be flow controlled at the another network device. The at least one processor circuit may be further configured to transmit, out-of-band and through at least one intermediary network device, the end to end flow control message to the another network device.