Flash Translation Layer Map Synchronization via Shared TOC Pages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data storage systems experience significant latency and resource consumption due to the need for multiple layers of processing when writing and reading data from persistent storage, particularly in constructing and synchronizing flash translation layer (FTL) maps across multiple components in a multiprocessing environment.

Innovation Solution

A storage system architecture where a primary control module constructs a table of contents (TOC) page and shares it with a secondary control module via an inter-processor link, allowing the secondary module to update its FTL map without constructing the TOC page itself, thereby reducing redundant processing and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple control modules construct and synchronize their own FTL maps independently, then each module can service requests autonomously, but the time and resources required to store data significantly increase

Engineering Contradiction:
Improveautonomous request servicingVSAvoiddata storage time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The primary control module pre-constructs the TOC page and stores it in the shared storage module before the secondary control module needs it. This preliminary action eliminates the need for the secondary module to reconstruct the same TOC page, reducing redundant processing time while maintaining the ability of each module to service requests autonomously

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The secondary control module copies the TOC page from the shared storage module instead of constructing it independently. This copying mechanism preserves data consistency across modules while significantly reducing the time and processing resources required, as the secondary module only needs to replicate existing data rather than perform full construction and synchronization operations

Inventive Principle:
Principle #26Copying

2Stability of the object's composition

If the secondary control module waits for TOC page synchronization from the primary module, then data consistency is maintained, but write request acknowledgment latency increases

Engineering Contradiction:
ImproveFTL map consistencyVSAvoidwrite acknowledgment latency
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The shared storage module acts as an intermediary between the primary and secondary control modules. The primary module writes the TOC page to this intermediary storage, and the secondary module retrieves it independently. This mediator mechanism maintains FTL map consistency across modules while eliminating the need for the secondary module to wait for synchronization, thereby reducing write request acknowledgment latency

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The TOC page is pre-stored in the shared storage module by the primary control module before the secondary module needs to access it. This preliminary storage action ensures that when the secondary module needs to update its FTL map, the data is already available, maintaining consistency without introducing synchronization wait time that would increase write acknowledgment latency

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If TOC pages are constructed and synchronized across multiple control modules, then accurate FTL maps are maintained, but processing resources and time are significantly consumed

Engineering Contradiction:
ImproveFTL map accuracyVSAvoiddata storage efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

Instead of each control module independently constructing and synchronizing FTL maps through complex coordination, the secondary module simply copies the pre-constructed TOC page from shared storage. This copying approach maintains accurate FTL maps across all modules while dramatically improving data storage efficiency by eliminating redundant construction operations and reducing processing resource consumption

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9921756B2Method and system for synchronizing an index of data blocks stored in a storage system using a shared storage module
Publication Date: 2018.03.20 EMC IP HLDG CO LLC
  • US9921756B2 patent drawing
  • US9921756B2 patent drawing
  • US9921756B2 patent drawing

AI summary

A storage system includes a first and second control modules (CMs) connected to a client and a storage module over a communication fabric. In response to a data fragment written to the storage module, the first CM is to create a table of contents (TOC) entry in a TOC page maintained in a first storage partition of the storage module, update its FTL map, determine whether the TOC page contains a predetermined number of TOC entries, and in response to determining that the TOC page contains the predetermined number of TOC entries, send a control signal to the second CM via an inter-processor link. In response to the control signal received from the first CM via the inter-processor link, the second CM is to copy the TOC page from the first storage partition to a memory associated with the second CM to allow the second CM to update its FTL map.