Multi-Core Memory Controller Atomic Data Write

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory systems face challenges in maintaining data atomicity during write operations, especially in multi-core environments, and in handling sudden power-off scenarios where uncorrectable errors may occur, leading to incomplete or corrupted data.

Innovation Solution

A memory system with a multi-core architecture where a main core divides data into units and allocates them to sub-cores for writing, ensuring that either the entire data unit is written or none is, and includes error detection and recovery mechanisms to maintain atomicity during sudden power-off events by reporting uncorrectable errors and unmapping affected sub-data units.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is divided into multiple units and written by multiple sub-cores in parallel, then writing speed is improved, but data atomicity cannot be ensured when sudden power-off occurs

Engineering Contradiction:
Improvewriting speedVSAvoiddata atomicity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by writing metadata (data unit identifier, size, offset) to the memory device before actually writing the data content. This metadata serves as a preparatory marker that enables the memory controller to identify and rollback incomplete data units after a sudden power-off event, thus ensuring data atomicity while maintaining parallel writing performance

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback through the SPQR (Sudden Power-Off Recovery) operation that continuously monitors writing status and detects uncorrectable errors. When an error is detected in one sub-core, the system receives feedback about the failed data unit and triggers a rollback mechanism that coordinates with other sub-cores to maintain atomicity across all parallel writing operations

Inventive Principle:
Principle #23Feedback

2Reliability

If the entire data unit is controlled to be written or none written, then data atomicity is maintained, but system complexity increases due to coordination requirements

Engineering Contradiction:
Improvedata atomicityVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data writing process into independent data units, each with its own metadata record containing identifier, size, and offset information. This segmentation allows each sub-core to write data units independently while the memory controller maintains a simplified coordination mechanism through metadata management, reducing the complexity of inter-core coordination

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces metadata as an intermediary between the parallel sub-cores and the main control logic. The metadata records act as intermediaries that encode the state and characteristics of each data unit, allowing the memory controller to make atomicity decisions based on simple metadata checks rather than complex real-time coordination between multiple sub-cores

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If error detection and rollback mechanisms are implemented, then data integrity is improved, but processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-writing metadata that includes data unit identifier, size, and offset before the actual data writing begins. This preliminary metadata preparation enables rapid error detection and rollback by providing pre-computed reference information, avoiding the need for time-consuming analysis of written data during error recovery

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements skipping by directly jumping to the offset position of the failed data unit using the pre-stored offset information in metadata. When an uncorrectable error is detected, the system rushes through the rollback process by directly seeking to the correct offset position and overwriting, rather than sequentially checking or partially rolling back through multiple data units, thus minimizing processing time loss

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS11544002B2Memory system, memory controller and operating method thereof
Publication Date: 2023.01.03 SK HYNIX INC
  • US11544002B2 patent drawing
  • US11544002B2 patent drawing
  • US11544002B2 patent drawing

AI summary

A memory system, a memory controller and an operating method are disclosed. When a target command which instructs an operation of writing target data to a memory device is received from a host, the target data is divided into data units, and a first data unit among the data units is controlled such that the entire first data unit is written to the memory device or none of the first data unit is written to the memory device. As a consequence, it is possible to write data in specific units in a memory system using a multi-core.