Positive Feedback Ethernet Flow Control for Lossless Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Ethernet link layer protocols lack effective flow control mechanisms, leading to buffer overflow and frame loss issues, especially in data centers and high-performance computing applications where lossless behavior is required, as existing PAUSE and Per Priority Pause (PPP) frames do not provide adequate control over different service classes and may introduce latency and increase complexity.

Innovation Solution

A positive feedback credit-based Ethernet link flow control system where nodes exchange credit information to manage frame transmission, allowing only authorized frames to be sent, preventing buffer overflow and ensuring lossless behavior for priority classes, particularly in mixed protocol environments like Fibre Channel over Ethernet.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PAUSE frame flow control is used to prevent buffer overflow, then frame loss is reduced, but transmission latency increases and CPU utilization decreases

Engineering Contradiction:
Improveframe loss preventionVSAvoidtransmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The receiver pre-allocates buffer space and sends credit information to the transmitter before the buffer is actually needed. This allows the transmitter to send frames immediately without waiting for buffer availability confirmation, eliminating the pause-induced latency while preventing buffer overflow through advance buffer reservation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback through credit information exchange between receiver and transmitter. The receiver monitors buffer status and dynamically updates credit values, which are sent to the transmitter to control its sending rate. This real-time feedback mechanism prevents buffer overflow while maintaining continuous transmission when buffers are available.

Inventive Principle:
Principle #23Feedback

2Reliability

If PAUSE frame is sent to control flow, then buffer overflow is prevented, but device complexity increases due to timeout and retransmission mechanisms

Engineering Contradiction:
Improvebuffer overflow preventionVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the error recovery function from the flow control mechanism. Instead of using PAUSE frames with complex timeout and retransmission logic, the system uses pure credit-based flow control where the receiver manages its own buffer and proactively controls transmitter behavior through credit information, eliminating the need for retransmission protocols.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The receiver independently manages its buffer allocation and sends credit information to the transmitter without requiring the transmitter to implement complex flow control logic or timeout mechanisms. The transmitter simply follows the credit guidance, making the system easier to implement while maintaining reliability.

Inventive Principle:
Principle #25Self-service

3Reliability

If Per Priority Pause frame is used for different service classes, then lossless behavior is achieved for priority classes, but transmission speed for non-lossless classes is reduced

Engineering Contradiction:
Improvelossless transmissionVSAvoidtransmission speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system segments the flow control mechanism by priority class, maintaining separate credit counters and buffer allocations for each priority level. This allows lossless behavior (credit-based control) to be applied only to priority classes that require it, while other classes can use simpler, faster transmission mechanisms without being constrained by credit checks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different flow control strategies are applied locally to different priority classes based on their requirements. High-priority lossless classes receive credit-based flow control with dedicated buffer space, while lower-priority classes that tolerate loss can use more aggressive transmission rates, optimizing overall system performance.

Inventive Principle:
Principle #3Local quality

4Productivity

If credit-based flow control is implemented, then transmission efficiency is improved, but device complexity increases due to credit management

Engineering Contradiction:
Improvetransmission efficiencyVSAvoidcredit management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The receiver autonomously manages credit allocation based on its buffer status without requiring complex coordination with the transmitter. The transmitter passively receives and follows credit instructions, significantly reducing the computational burden and complexity on both ends compared to symmetric credit management or PAUSE frame mechanisms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9025451B2Positive feedback ethernet link flow control for promoting lossless ethernet
Publication Date: 2015.05.05 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • US9025451B2 patent drawing
  • US9025451B2 patent drawing
  • US9025451B2 patent drawing

AI summary

An Ethernet node includes a receiver and transmitter for coupling to an Ethernet link for transceiving Ethernet frames with a remote Ethernet node at a remote end of the Ethernet link. The Ethernet node sends to the remote Ethernet node credit information that enables the remote Ethernet node to know an amount of Ethernet frames the remote Ethernet node is allowed to send to the Ethernet node. The credit information may be specified on a VLAN priority basis and may be included in a header piggy-backed on a host Ethernet frame or may be included in an explicit frame. The credit information may incrementally replenish credits or may specify an absolute credit amount and may be sent in response to processing frames, detection of a frame error, receipt of a request from the remote node or other events.