Memory Controller Mapping Synchronization via Header Copy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data storage devices face performance issues and data inconsistencies due to race conditions during the synchronization of management tables between volatile and non-volatile memory, which can lead to reduced throughput and potential data loss.

Innovation Solution

A system and method for synchronizing mapping information between logical and physical addresses in a memory device, where a controller generates headers and entries indicating updates, allowing for safe recording of additional updates during synchronization without blocking operations, by maintaining a copy of headers and updating them after changes, thereby avoiding race conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the management table is synchronized to non-volatile memory periodically, then data consistency is improved, but device throughput deteriorates due to blocked operations

Engineering Contradiction:
Improvedata consistencyVSAvoiddevice throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by generating a copy of the header before the synchronization process begins. This copy is used as a reference during synchronization, allowing the system to proceed with the synchronization operation without blocking subsequent update operations. The header copy is prepared in advance, enabling the synchronization to use this static reference while the original header can be updated independently.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism by using a copy of the header as a mediator between the synchronization process and the update process. This copy acts as a buffer that allows both operations to proceed simultaneously without interfering with each other. The synchronization uses the copy as reference, while updates modify the original header, eliminating the need to block either operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If operations are allowed to update the management table during synchronization, then device throughput is improved, but data consistency deteriorates due to race conditions

Engineering Contradiction:
Improvedevice throughputVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by creating a copy of the header before synchronization starts. This copy serves as a fixed reference point that captures the state of the header at the beginning of synchronization. By having this preliminary copy, the system can safely allow updates to the original header during synchronization without risking inconsistencies, because the synchronization process references the unchanged copy rather than the evolving original.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent directly applies the copying principle by creating a duplicate of the header structure. This copy contains the same information as the original header but is isolated from subsequent updates. The synchronization process reads from this static copy, ensuring consistency, while the original header remains free to be updated by concurrent operations without affecting the synchronization integrity.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If the header indicating number of entries is updated during synchronization, then mapping information accuracy is improved, but race conditions worsen

Engineering Contradiction:
Improvemapping information accuracyVSAvoidrace condition prevention
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The patent applies preliminary action by generating a copy of the header before the synchronization operation begins. This copy freezes the header state at a specific point in time, creating a stable reference that does not change during synchronization. Even if the number of entries in the mapping information changes during the synchronization process, the copy remains unchanged, preventing any race conditions while still allowing the mapping information to be updated accurately in the original header after synchronization completes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10802744B2Updating mapping information during synchronization of memory device
Publication Date: 2020.10.13 SANDISK TECHNOLOGIES LLC
  • US10802744B2 patent drawing
  • US10802744B2 patent drawing
  • US10802744B2 patent drawing

AI summary

Disclosed herein are related to a controller, a method, and a system for updating mapping information between a logical address and a physical address of a corresponding region of a memory device. In one aspect, the controller generates a plurality of entries, where each entry indicates an update in the mapping information associated with the corresponding region. The controller generates a plurality of headers, where each header is associated with one or more entries in the corresponding region. The controller receives an instruction to synchronize the mapping information stored on the memory device with the update in the mapping information. The controller generates a copy of the plurality of headers in response to receiving the instruction to synchronize. The controller synchronizes the mapping information stored on the memory device according to the copy of the plurality of headers and the plurality of entries.