Non-Volatile Memory Garbage Collection Cost Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data storage devices using non-volatile memory face inefficiencies in garbage collection operations, leading to slower operational speeds and response times due to the mixing of valid and invalid data, which affects the performance in handling requests from host devices.

Innovation Solution

A method and system for optimizing garbage collection in data storage devices by determining and comparing garbage collection costs for memory blocks with the least valid pages, allowing for efficient data transfer between regions within the non-volatile memory device, thereby optimizing operational speed and response time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If garbage collection operations are performed without optimization, then data storage devices can maintain basic functionality, but operational speed and response time deteriorate due to mixing of valid and invalid data

Engineering Contradiction:
Improveoperational speedVSAvoidgarbage collection complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The memory device is divided into multiple regions (first region and second region) with different characteristics. The control unit segments the garbage collection process by selectively performing operations in different regions based on valid page counts, allowing efficient handling of garbage collection without processing the entire memory space uniformly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The control unit changes the operational parameters of garbage collection based on the valid page count threshold. When the valid page count in a memory block exceeds the threshold, the control unit performs garbage collection; otherwise, it skips the operation. This dynamic parameter adjustment optimizes operational speed by avoiding unnecessary garbage collection operations.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If garbage collection operations are performed on all memory blocks, then data management is simplified, but response time increases due to processing unnecessary blocks

Engineering Contradiction:
Improverequest processing efficiencyVSAvoidgarbage collection time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The control unit performs preliminary assessment of memory blocks by checking valid page counts before initiating garbage collection operations. This preliminary action identifies which memory blocks actually require garbage collection, preventing waste of time on blocks that are already optimized or do not need intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of performing garbage collection on all memory blocks (excessive action), the control unit applies partial action by selectively performing the operation only on memory blocks where the valid page count exceeds the threshold. This partial approach reduces unnecessary processing time while maintaining data management effectiveness.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If data is frequently transferred between memory regions, then garbage collection efficiency improves, but power consumption increases

Engineering Contradiction:
Improvedata management reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Different regions of the memory device are assigned different functions and characteristics. The first region and second region have distinct roles in the storage hierarchy, allowing data to be managed locally with appropriate garbage collection strategies for each region's specific requirements, reducing unnecessary data transfers and associated power consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Each memory region manages its own garbage collection needs independently based on its valid page count. The control unit enables regions to self-determine when they need garbage collection, avoiding unnecessary data transfers to other regions and reducing overall power consumption while maintaining data management reliability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10671527B2Data storage device and method for operating the same
Publication Date: 2020.06.02 SK HYNIX INC
  • US10671527B2 patent drawing
  • US10671527B2 patent drawing
  • US10671527B2 patent drawing

AI summary

A method for operating a data storage device including a non-volatile memory device including a first region and a second region includes: storing data from a data cache memory in memory blocks in the first region; determining a first garbage collection cost with respect to a first target memory block having the least valid page among the memory blocks in the first region in which the data are kept; determining a second garbage collection cost with respect to a second target memory block having the least valid page among the memory blocks in the first region from which the data are cleared; and performing a garbage collection operation to copy valid data of a garbage collection target memory block into memory blocks in the second region based on a comparison result of the first garbage collection cost and the second garbage collection cost.