Conditional Journaling for Storage Class Memory Failure Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing devices face inefficiencies in accessing storage class memory due to high access latency and limited capacity, which can lead to increased processing load and data bandwidth usage, especially during failure recovery processes.

Innovation Solution

Implementing a storage class memory device with a journaling mechanism that creates entries only upon failure occurrence, allowing for efficient data recovery and remapping of logical addresses to physical addresses, thereby reducing processing load and data bandwidth usage while maintaining non-volatile storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If journaling mechanism is implemented for every access command, then data reliability is improved, but processing load and data bandwidth usage increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidprocessing load
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by creating journal entries only for a subset of access commands - specifically those that fail or require recovery - rather than journaling every command. This selective approach maintains data reliability for critical operations while reducing the overall processing load and bandwidth consumption associated with comprehensive journaling.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements local quality by applying different journaling strategies to different types of access commands based on their failure characteristics. Successful commands may not require journaling, while failed commands or those involving recovery operations do require journal entries. This localized differentiation optimizes the balance between reliability and processing efficiency.

Inventive Principle:
Principle #3Local quality

2Reliability

If journaling mechanism is implemented for every access command, then data recovery capability is improved, but data bandwidth usage increases

Engineering Contradiction:
Improvedata recovery capabilityVSAvoiddata bandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent reduces data bandwidth usage by applying partial journaling - only creating journal entries when necessary for recovery purposes rather than for every access command. This selective journaling maintains data recovery capability for failed operations while minimizing the bandwidth consumption associated with writing journal entries.

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If access latency is reduced, then system performance is improved, but storage capacity may be limited

Engineering Contradiction:
Improveaccess latencyVSAvoidstorage capacity
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments the storage class memory device into multiple planes, allowing parallel access operations that reduce access latency. By organizing memory into multiple independently accessible planes, the system can service multiple requests simultaneously, improving speed without requiring an increase in total storage capacity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10467074B2Conditional journal for storage class memory devices
Publication Date: 2019.11.05 SANDISK TECHNOLOGIES LLC
  • US10467074B2 patent drawing
  • US10467074B2 patent drawing
  • US10467074B2 patent drawing

AI summary

Systems and methods are disclosed for a journal for a storage class memory device. The storage class memory device may execute an access command for a first page in the storage class memory device. The storage class memory device may also determine whether a failure occurred while executing the access command. The storage class memory device may create an entry in a journal for the storage class memory device if a failure occurred while executing the access command. The storage class memory device may refrain from creating the entry if a failure does not occur while executing the access command.