Memory Controller Garbage Collection Threshold Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory systems face inefficiencies in garbage collection operations, particularly when handling sequential and random write commands, leading to unnecessary performance degradation due to improper threshold settings and command type identification.

Innovation Solution

A memory system and method that determine whether a write command is sequential or random, and perform garbage collection based on specific threshold values and the number of sequential commands, optimizing operations to prevent unnecessary garbage collection and enhance performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If garbage collection operation is performed frequently to maintain memory performance, then memory stability is improved, but productivity deteriorates due to unnecessary operations

Engineering Contradiction:
Improvememory stabilityVSAvoidproductivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The garbage collection operation is made dynamic by adjusting the threshold value based on the type of write command (sequential vs. random). The controller determines the command type and selectively applies different threshold criteria, allowing the system to adapt GC frequency to actual workload conditions rather than performing fixed frequent operations

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of threshold value for garbage collection based on command type. For sequential write commands, a higher threshold is used, while for random write commands, a lower threshold is applied. This parameter adjustment prevents unnecessary GC operations during sequential writes while maintaining stability during random writes

Inventive Principle:
Principle #35Parameter changes

2Reliability

If garbage collection operation is performed based on total data capacity threshold, then memory stability is improved, but device complexity increases due to improper threshold settings

Engineering Contradiction:
Improvememory stabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the garbage collection threshold into different types based on command characteristics. Instead of using a single uniform threshold, the system divides thresholds into sequential write threshold and random write threshold, making the control logic more manageable and accurate

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controller continuously monitors the type of write command being executed and provides feedback to adjust the appropriate threshold. This feedback mechanism ensures the system uses the correct threshold value (sequential or random) based on actual command types, preventing misuse of improper thresholds

Inventive Principle:
Principle #23Feedback

3Productivity

If the system cannot distinguish between sequential and random write commands, then device complexity is reduced, but productivity deteriorates due to inefficient garbage collection

Engineering Contradiction:
ImproveproductivityVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies local quality by treating different command types differently. The controller identifies whether each write command is sequential or random and applies locally appropriate GC strategies to each command type, optimizing productivity for each specific case rather than using a one-size-fits-all approach

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11099981B2Memory system and operating method thereof
Publication Date: 2021.08.24 SK HYNIX INC
  • US11099981B2 patent drawing
  • US11099981B2 patent drawing
  • US11099981B2 patent drawing

AI summary

An operating method of a memory system includes determining whether a write command currently provided is a sequential write command or a random write command, performing a garbage collection operation based on whether a total capacity of data provided after a preceding garbage collection operation exceeds a sequential command threshold value, when it is determined that the write command is a sequential write command, and performing the garbage collection operation based on whether a number of sequential write commands among a set number of commands currently provided, is greater than or equal to a predetermined number and whether the total capacity of the data provided after the preceding garbage collection operation exceeds the sequential command threshold value, when it is determined that the write command is a random write command.