Operating System Direct-Mapped Flash Storage Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional storage systems face inefficiencies in data management and storage operations, particularly in handling flash drives without integrated storage controllers, leading to unnecessary write operations and reduced reliability.

Innovation Solution

Implementing a direct-mapped flash storage system where the operating system initiates and controls data operations across multiple flash drives, eliminating the need for lower-level storage controllers and reducing redundant write processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional storage controllers are used to manage flash drives, then storage operations can be controlled and coordinated, but unnecessary write operations occur and reliability is reduced

Engineering Contradiction:
Improvestorage reliabilityVSAvoidwrite operation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the storage controller functionality from the traditional storage subsystem and places it directly in the operating system. This eliminates the intermediate storage controller layer that was causing redundant write operations, thereby improving both reliability and write operation efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a new intermediary layer in the form of an operating system module that directly manages flash drives without requiring traditional storage controllers. This new mediator eliminates the harmful intermediary (storage controller) that was causing the technical contradiction.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If storage controllers are used to manage data operations, then coordination is possible, but system complexity increases

Engineering Contradiction:
Improvedata operation controlVSAvoidstorage system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges the storage controller functionality with the operating system, combining two previously separate components into one integrated system. This reduces overall system complexity while maintaining ease of operation for data management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The operating system is given multi-functional capability by incorporating storage management functions directly into it. This universal approach eliminates the need for dedicated storage controllers, reducing system complexity while preserving operational control.

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

3Adaptability or versatility

If multiple flash drives are managed independently, then flexibility is maintained, but centralized control and efficiency are reduced

Engineering Contradiction:
Improveflash drive management flexibilityVSAvoidstorage operation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the storage management function at the software level within the operating system, allowing individual flash drives to be managed independently while maintaining centralized control through the OS. This enables both flexibility and efficiency simultaneously.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12019522B2Container recovery layer prioritization
Publication Date: 2024.06.25 PURE STORAGE INC
  • US12019522B2 patent drawing
  • US12019522B2 patent drawing
  • US12019522B2 patent drawing

AI summary

An illustrative method of container recovery using layer prioritization includes identifying a set of immutable layers of container images included in a dataset used by a container system to run containerized applications on a first cluster; copying the set of immutable layers of container images to a second cluster in preparation for a recovery event; receiving, after the set of immutable layers of container images are copied to the second cluster, a recovery request to recover the containerized applications; and copying, in response to the recovery request, a set of mutable layers included in the dataset to the second cluster, the second cluster configured to use the copied set of immutable layers and the copied set of mutable layers to recover the containerized applications on the second cluster.