Direct-Mapped Flash Storage Write Consistency via OS-Level Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional storage systems face inefficiencies in data management and storage operations, particularly in handling control information and wear leveling across flash drives, leading to unnecessary write operations and reduced reliability.

Innovation Solution

The implementation of a direct-mapped flash storage system where the operating system initiates and controls storage processes, including data allocation and garbage collection, without relying on lower-level storage controllers, using non-volatile memory as a buffer for write operations and employing erasure coding for redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional storage controllers manage flash drives with wear leveling and garbage collection, then storage operations are automated, but redundant write operations increase and reliability decreases

Engineering Contradiction:
Improvestorage operation automationVSAvoiddata integrity
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent extracts the storage controller from the storage system, eliminating the intermediate layer that causes redundant write operations. The operating system directly manages flash drives without a storage controller, removing the source of reliability issues while maintaining automation at the OS level.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent inverts the traditional storage architecture by having the operating system (higher-level software) directly control storage operations instead of having storage controllers (lower-level hardware) manage them. This inversion eliminates the reliability problems caused by traditional controllers while preserving automation.

Inventive Principle:
Principle #13The other way round (Inversion)

2Ease of operation

If storage controllers perform data management and wear leveling, then storage operations are simplified, but unnecessary write operations increase reducing device lifespan

Engineering Contradiction:
Improvestorage management simplicityVSAvoidflash drive lifespan
Core Design Contradiction:
Ease of operationVSDuration of action of stationary object

Solution Approach 1:

The patent removes the storage controller that performs harmful wear leveling operations, eliminating the source of unnecessary write operations. The OS directly manages data placement without intermediate controller interference, simplifying the system while extending device lifespan.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent converts the harmful effect of controller-managed wear leveling (which causes excessive writes) into a benefit by having the OS directly manage storage. This eliminates the harmful intermediate layer while maintaining efficient data management, thereby extending flash drive lifespan.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

3Adaptability or versatility

If multiple storage controllers are used for redundancy, then system availability improves, but write consistency and data integrity deteriorate

Engineering Contradiction:
Improvesystem availabilityVSAvoidwrite consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent merges the storage control function directly into the operating system, eliminating multiple independent storage controllers. This consolidation ensures a single source of truth for write operations, maintaining data integrity while providing redundancy through OS-level management and erasure coding.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent inverts the redundancy approach by moving control from multiple hardware controllers to the operating system software layer. This inversion ensures write consistency through centralized OS management while maintaining availability through software-based fault tolerance and erasure coding.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS10509581B1Maintaining write consistency in a multi-threaded storage system
Publication Date: 2019.12.17 PURE STORAGE INC
  • US10509581B1 patent drawing
  • US10509581B1 patent drawing
  • US10509581B1 patent drawing

AI summary

Maintaining identifier service consistency within a storage system, including, responsive to a write operation for a dataset: assigning an identifier for the write operation, wherein the identifier is equal to a current identifier from an allowable set of identifiers; storing, within a metadata header for the dataset, metadata indicating the assigned identifier; and incrementing the current identifier; and responsive to determining that the incremented current identifier has caused a reservation event: updating a range corresponding to the allowable set of identifiers.