HBA Rate Limiting for Fibre Channel SAN Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network congestion in storage area networks (SANs) occurs due to data overflow, leading to reduced network throughput and performance issues, particularly in devices using Fibre Channel protocols, without effective solutions to manage traffic congestion.

Innovation Solution

Implementing a host bus adapter (HBA) with a rate limiting unit that regulates data transmission and reception rates to prevent data overflow, using techniques such as command and transmit rate limiting, ensuring data is transmitted and received at rates compatible with the network's capacity, thereby reducing congestion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data transmission rate is increased to improve network throughput, then productivity is improved, but network congestion occurs leading to reduced reliability

Engineering Contradiction:
Improvenetwork throughputVSAvoidnetwork performance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The rate limiting unit proactively regulates data transmission rates before congestion occurs by monitoring network conditions and adjusting transmission rates in advance. This preliminary control prevents data overflow and maintains network reliability while optimizing throughput.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors network congestion conditions and adjusts transmission rates based on feedback from the network state. The rate limiting unit uses this feedback to dynamically control data flow, ensuring optimal throughput while preventing congestion-related performance degradation.

Inventive Principle:
Principle #23Feedback

2Reliability

If rate limiting is implemented to reduce congestion, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvenetwork performanceVSAvoidhost bus adapter complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The host bus adapter includes an integrated rate limiting unit that autonomously regulates data transmission without requiring external control or host intervention. This self-service capability reduces congestion while minimizing the need for complex host-side processing or additional control systems.

Inventive Principle:
Principle #25Self-service

3Productivity

If CPU intervention is used to manage traffic congestion, then productivity is improved, but loss of time increases due to CPU overhead

Engineering Contradiction:
Improvecongestion management efficiencyVSAvoidCPU overhead
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The rate limiting unit operates autonomously within the host bus adapter, managing data transmission rates without requiring CPU intervention. This eliminates the time loss associated with CPU overhead for congestion management while maintaining optimal network throughput.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The rate limiting unit acts as an intermediary between the host system and the network, handling traffic regulation tasks that would otherwise require CPU involvement. This intermediary function offloads congestion management from the CPU, reducing overhead and improving overall system efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4080851B1System of and method for reducing congestion in a network
Publication Date: 2026.02.11 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • EP4080851B1 patent drawingFigure 1A
  • EP4080851B1 patent drawingFigure 1B
  • EP4080851B1 patent drawingFigure 1C

AI summary

Systems and methods of communicating in a network use rate limiting. Rate limiting units (either receive side or transmit side) can perform rate limiting in response to a) a maximum number of bytes that can be solicited over a first period of time is exceeded, b) a maximum number of bytes that are outstanding over a second period of time is exceeded; or c) a maximum number of commands that are outstanding over a period of time is exceeded as part of CMD_RXRL. The CMD_RXRL can have three components (a) max bytes, b) outstanding bytes, c) outstanding commands. TXRL contains the component of max bytes or maximum number of bytes that can be transmitted over a third period of time to match the speed of a receive link, or any node or link through the network/fabric.