Persistent Information Unit Pacing in Fibre Channel

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Fibre Channel architecture's IU pacing protocol limits the first burst of information units to 16, causing delays in channel programs, especially at long distances or high link speeds, as it requires a round trip for subsequent information units to be sent, leading to inefficiencies in I/O operations.

Innovation Solution

Implementing a method to enable persistent information unit pacing by setting a concurrent persistent pacing enablement bit in node descriptors, allowing the channel and control unit to retain pacing settings across command chains without re-establishing logical paths, thus enabling more efficient data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the default IU pacing limit of 16 is enforced, then the protocol simplicity is maintained, but the I/O program execution speed deteriorates at long distances

Engineering Contradiction:
ImproveI/O program execution speedVSAvoidRound trip delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent changes the IU pacing parameter from a fixed default value of 16 to a persistent value that can be adjusted and retained across command chains. The channel can set a higher pacing count value that persists for subsequent channel programs, allowing more information units to be in flight simultaneously and reducing round trip delays.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The channel performs preliminary action by setting the persistent pacing count value in advance during the first command chain execution. This pre-configured pacing value is then retained and applied to subsequent channel programs without requiring re-negotiation, enabling faster execution from the outset.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the pacing parameter is made persistent across command chains, then the data transfer efficiency is improved, but the device complexity increases

Engineering Contradiction:
ImproveData transfer efficiencyVSAvoidPacing management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically retaining and reusing the pacing count value across command chains without requiring manual intervention or complex reconfiguration. The channel automatically applies the persistent pacing value to subsequent channel programs, simplifying the management overhead.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The persistent pacing mechanism serves multiple functions: it acts as a performance optimization for long-distance connections, a configuration retention mechanism, and a simplification tool by eliminating the need for repeated pacing negotiations. This multi-functionality justifies the added complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If code for persistent pacing is loaded concurrently without re-establishing logical paths, then the system availability is improved, but the indicator setting complexity increases

Engineering Contradiction:
ImproveSystem availabilityVSAvoidConcurrent enablement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses preliminary action by pre-defining a specific indicator bit in the node descriptor that signals support for concurrent persistent pacing enablement. This pre-established mechanism allows the channel and control unit to recognize and enable persistent pacing functionality without disrupting existing logical paths, maintaining system availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The node descriptor indicator acts as an intermediary that mediates between the channel and control unit to enable persistent pacing functionality. This indicator serves as a communication bridge that allows both ends to understand and support the new functionality without requiring path re-establishment or complex negotiation protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8005082B2Concurrent enablement of persistent information unit pacing
Publication Date: 2011.08.23 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8005082B2 patent drawing
  • US8005082B2 patent drawing
  • US8005082B2 patent drawing

AI summary

Provided are a method, system, and article of manufacture, in which a logical path is established between a control unit and a channel over a fiber channel connection. Code for persistent information unit pacing is loaded into the control unit and the channel. An indicator is set in node descriptors of the control unit and the channel to indicate concurrent enablement of persistent pacing while retaining the established logical path between the control unit and the channel.