SAS Expander Deadlock Detection via Modified Open Address Frame

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In SAS environments, deadlock detection is delayed due to partial pathway timeouts, leading to slowed system performance and unnecessary pathway recovery, especially when true deadlock conditions are not present.

Innovation Solution

The SAS expander includes a processor that detects deadlock conditions by generating a modified Open Address Frame (OAF) with a deadlock indicator, allowing for immediate pathway recovery only when a valid deadlock is confirmed, thus avoiding unnecessary recovery processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If path recovery is used to avoid deadlock by tearing down partial pathways, then system reliability is improved, but system performance deteriorates due to delayed deadlock detection and unnecessary pathway recovery

Engineering Contradiction:
Improvedeadlock avoidanceVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by detecting potential deadlock conditions before they fully develop into actual deadlocks. The system monitors connection requests and identifies when a device is waiting for a response that may never come, triggering pathway recovery proactively rather than waiting for timeout expiration. This early intervention prevents true deadlocks while avoiding unnecessary recovery operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms by continuously monitoring the state of partial pathways and connection requests. The system receives feedback about arbitration in progress status and uses this information to determine whether pathway recovery is actually needed. This feedback loop allows the system to distinguish between true deadlock conditions and temporary delays, thereby improving both reliability and performance.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If pathway recovery is initiated after partial pathway timeout expiration, then deadlock detection is achieved, but detection time is delayed and system performance slows

Engineering Contradiction:
Improvedeadlock detection accuracyVSAvoiddeadlock detection delay
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary deadlock detection by monitoring connection requests and arbitration status before the timeout period expires. When a connection request is sent and arbitration is in progress, the system proactively checks for deadlock conditions by examining whether the destination device is also waiting for a response. This preliminary detection occurs well before timeout expiration, eliminating the detection delay while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the deadlock detection process into distinct phases: connection request initiation, arbitration status monitoring, and deadlock condition verification. By breaking down the detection process, the system can intervene at the appropriate moment (when arbitration is in progress) rather than waiting for the complete timeout period, thereby reducing detection time while maintaining precision.

Inventive Principle:
Principle #1Segmentation

3Speed

If pathway recovery is initiated without verifying true deadlock conditions, then response time is reduced, but false deadlock initiations increase and cause unnecessary pathway teardowns

Engineering Contradiction:
Improveresponse speedVSAvoidfalse deadlock detection
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system uses feedback from multiple sources to verify true deadlock conditions before initiating pathway recovery. It monitors both the source device's connection request and the destination device's arbitration status. Only when feedback confirms that both devices are waiting for each other (true deadlock) does the system initiate recovery. This multi-source feedback mechanism reduces false detections while maintaining fast response times.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system applies self-service by having devices provide information about their own state. The source device indicates it is waiting for a response, and the destination device indicates arbitration is in progress. By using self-reported status information from the devices themselves, the system can accurately determine true deadlock conditions without making assumptions, thereby reducing false detections while maintaining rapid response.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9378159B2Deadlock detection and recovery in SAS
Publication Date: 2016.06.28 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • US9378159B2 patent drawing
  • US9378159B2 patent drawing
  • US9378159B2 patent drawing

AI summary

Systems and methods herein provide for managing devices through a Serial Attached Small Computer System Interface (SAS) expander. The SAS expander includes a processor adapted to detect deadlock conditions in a SAS environment. In one embodiment, the SAS expander is operable to detect an Open Address Frame associated with a connection request from a source device to a destination device. The Open Address Frame includes a source address and a destination address associated with the source device and the destination device, respectively. The expander receives an arbitration in progress status on a partial pathway that is associated with the connection request. The expander is further operable to modify the Open Address Frame to include a deadlock indicator and forward the modified Open Address Frame on the partial pathway. When the modified Open Address Frame is received, the expander initiates pathway recovery upon determination that the deadlock indicator is valid.