Storage Controller Extent Conflict Checking via Track Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Storage controllers face challenges in satisfying host application requests to avoid extent conflict checking during copy services operations, as copy services processes often have to wait too long to access extents, leading to performance issues.
Innovation Solution
The storage controller implements a mechanism where the host I/O process periodically queries the copy services process about track needs and opportunistically transfers tracks to the copy services process when no longer needed by the host I/O process, thereby avoiding blocking entire extents and improving system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If extent conflict checking is performed during copy services operations, then data consistency is ensured, but copy services process wait time increases and performance deteriorates
Solution Approach 1:
The patent segments the extent data structure into multiple tracks, allowing the copy services process to access individual tracks independently. This segmentation enables selective conflict checking at the track level rather than blocking entire extents, thereby reducing wait time while maintaining data consistency for accessed tracks.
Solution Approach 2:
The patent implements local conflict checking only for specific tracks that are currently being accessed by the copy services process, rather than performing global conflict checking across entire extents. This local approach reduces the scope of conflict checking operations, decreasing wait time while ensuring consistency for the specific tracks being copied.
2Productivity
If extent conflict checking is avoided to improve performance, then copy services process speed increases, but data consistency and conflict prevention may be compromised
Solution Approach 1:
The patent implements a feedback mechanism where the copy services process periodically queries the host I/O process to determine whether tracks are currently being accessed. This feedback loop enables dynamic conflict checking - conflicts are detected when the copy process attempts to access tracks that are actively being modified, ensuring data consistency while allowing uninterrupted access to tracks that are safe to copy.
Solution Approach 2:
The patent performs preliminary conflict checking by having the copy services process query track availability before initiating copy operations. This preliminary action allows the system to identify and avoid conflicts in advance, ensuring data consistency while enabling the copy process to proceed efficiently without unnecessary blocking when tracks are available.
3Reliability
If entire extents are blocked for conflict checking, then data consistency is maintained, but system performance and I/O throughput deteriorate
Solution Approach 1:
The patent divides extents into multiple smaller tracks and implements conflict checking at the track level rather than blocking entire extents. This segmentation allows the host I/O process to continue accessing tracks that are not currently being copied, maintaining data consistency for active tracks while preserving I/O throughput through parallel access to non-conflicting tracks.
Solution Approach 2:
The patent performs conflict checking partially - only for specific tracks that are currently being accessed by the copy services process, rather than performing exhaustive conflict checking across all tracks in an extent. This partial action approach maintains consistency for the specific tracks being copied while allowing other tracks to remain accessible, thereby preserving overall I/O throughput.
Data Source
AI summary
A storage controller receives a request to avoid extent conflict checking from a host application executing in a host that is coupled to the storage controller. In response to receiving a request, a host I/O process that executes in the storage controller to satisfy I/O requests from the host application opportunistically releases a track of an extent to a copy services process at an earliest point in time when the track of the extent is longer needed by the host I/O process and is needed by the copy services process.