Dynamic Data Path Architecture for Storage I/O Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage systems lack the ability to dynamically customize data paths for storage objects based on specific data services, leading to inefficient use of resources and potential bottlenecks in I/O operations.

Innovation Solution

A method and system for determining and modifying data paths by receiving administrative commands to enable, disable, or modify data services for storage objects, dynamically adding or removing components from the call stack based on the required services, allowing for customized data paths for each storage object.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a fixed data path configuration is used for all storage objects, then system simplicity is maintained, but I/O operation efficiency deteriorates due to bottlenecks and resource inefficiency

Engineering Contradiction:
ImproveI/O operation efficiencyVSAvoiddata path configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The data path configuration is segmented into multiple customizable components rather than using a monolithic fixed structure. Each storage object can have its data path divided into discrete service components that are selectively activated based on specific needs, allowing efficient I/O operations without universal complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The data path configuration transitions from a static fixed structure to a dynamic customizable structure. The system can modify the data path configuration in real-time based on administrative commands and service requirements, enabling optimization of I/O operations without permanent structural changes.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If data services are dynamically customized for each storage object, then adaptability and performance are improved, but system complexity increases

Engineering Contradiction:
Improvedata service customization capabilityVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A universal data path configuration framework is provided that can serve multiple storage objects with different requirements. The same base structure and service components are reused across different storage objects, enabling customization without proportional increases in overall system complexity.

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

Solution Approach 2:

The system enables self-service customization where data services are automatically configured and modified based on administrative commands and service requirements. The data path configuration adjusts itself without requiring manual intervention for each customization, reducing operational complexity.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If the data path configuration is modified while I/O operations are in progress, then service flexibility is improved, but system stability may deteriorate

Engineering Contradiction:
Improveservice modification capabilityVSAvoidsystem stability during modification
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary validation and preparation before modifying data path configurations during active I/O operations. Administrative commands are processed and configured in advance where possible, and modifications are applied in a controlled manner that pre-checks for potential stability issues.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that monitor the state of I/O operations and data path modifications in real-time. This feedback allows the system to adjust modification timing and methods to maintain stability, ensuring that changes are applied when they will have minimal impact on ongoing operations.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10552071B1Layered data path architecture for data protection and mobility
Publication Date: 2020.02.04 EMC IP HLDG CO LLC
  • US10552071B1 patent drawing
  • US10552071B1 patent drawing
  • US10552071B1 patent drawing

AI summary

A data path for each storage object may be customized for the particular services enabled for the storage object. Techniques for determining and using data paths may include: receiving an administrative command on a control path, wherein the administrative command is a request to perform any of enable, disable and modify a data service for a first storage object; determining, in accordance with the administrative command, a modification to be made to a current configuration of a data path for the first storage object in order to implement the administrative command, wherein the current configuration includes a plurality of components forming a call stack invoked in connection with I/O processing for I/Os directed to the first storage object; and modifying the data path in accordance with the modification determined.