Log File Track Reservation for Storage Controller Write Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The processing of log files in storage controllers is inefficient due to the overhead of repeatedly releasing and reacquiring tracks with empty space, which hinders performance and resource utilization during subsequent writes.

Innovation Solution

Reserving data structures and resources for a predetermined period after completing writes to log files, allowing for periodic destaging and asynchronous replication without waiting for specific processors, and terminating operations based on priority or error conditions to optimize resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If tracks are released after each log file write completion, then resource utilization is improved, but the overhead of repeated release and reacquisition increases processing time

Engineering Contradiction:
Improvetrack resource availabilityVSAvoidtrack management overhead time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary action by allocating and holding tracks for a predetermined period after log file write completion, before releasing them. This anticipates future write operations that will need these tracks, eliminating the need for repeated allocation/deallocation cycles. The track is prepared and held in advance, reducing the time loss from repeated management operations while maintaining resource availability for subsequent writes.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If tracks are held for future writes, then track management overhead is reduced, but resource availability for other processes decreases

Engineering Contradiction:
Improvelog file write efficiencyVSAvoidtrack resource flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system applies preliminary action by allocating tracks in advance for a predetermined period, preparing them for future log file writes before they are actually needed. This improves log file write efficiency by eliminating repeated allocation overhead. The track is held in a reserved state, balancing productivity improvement with controlled resource unavailability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamics by making track allocation flexible through a predetermined holding period rather than permanent allocation. Tracks are dynamically held for a specific time window after write completion, then automatically released. This dynamic approach maintains productivity benefits while restoring resource flexibility after the holding period expires, allowing other processes to access tracks when no longer needed for log operations.

Inventive Principle:
Principle #15Dynamics

3Reliability

If post-processing operations wait for processor execution, then processing accuracy is maintained, but processing speed decreases

Engineering Contradiction:
Improvedata consistencyVSAvoiddestaging and replication speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system applies self-service by enabling post-processing operations (destaging and replication) to execute autonomously when log file data is hardened, without waiting for dedicated processor availability. The log file monitoring mechanism automatically detects hardening events and triggers post-processing operations immediately. This maintains data consistency through proper hardening verification while dramatically improving processing speed by eliminating processor wait states.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback by continuously monitoring log file hardening status and using this information to trigger post-processing operations. When data is hardened, the monitoring mechanism provides feedback that initiates destaging and replication operations. This feedback-driven approach ensures processing accuracy by only acting on properly hardened data while improving speed through immediate response to hardening events rather than scheduled processor execution.

Inventive Principle:
Principle #23Feedback

4Reliability

If all log file data is processed uniformly, then data completeness is ensured, but processing efficiency decreases due to unnecessary data handling

Engineering Contradiction:
Improvedata completenessVSAvoidprocessing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies local quality by differentiating processing based on data characteristics and requirements. Different post-processing operations (destaging, replication, monitoring) are applied selectively to different portions of log file data based on their specific needs. This ensures data completeness for critical operations while improving processing throughput by avoiding uniform processing of all data with the same operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements partial action by performing only the necessary post-processing operations on specific log file data rather than applying all operations to all data. For example, not all log data requires replication or destaging. This selective approach maintains data completeness for operations that are actually needed while improving processing efficiency by skipping unnecessary operations on data that don't require them.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10216429B2Performing post-processing operations for log file writes
Publication Date: 2019.02.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10216429B2 patent drawing
  • US10216429B2 patent drawing
  • US10216429B2 patent drawing

AI summary

A storage controller receives one or more host writes to a log file. A track is allocated to the log file. In response to completion of the one or more host writes to the log file, a determination is made that the track has remaining space. Data structures are reserved to avoid releasing the track having the remaining space to accommodate potential future writes to the log file in the remaining space of the track.