Memory Controller Garbage Collection for Sustained Random Writes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage devices face challenges in accurately determining and managing random write performance during garbage collection, leading to potential bottlenecks and reduced quality of service (QoS) due to unpredictable random write performance.

Innovation Solution

A memory controller with a garbage collection controller and sustain detector that calculates valid page count values and generates sustain information to determine if the random write performance is sustainable, allowing for controlled write throttling to maintain consistent performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If garbage collection is performed on victim blocks, then empty blocks are secured for storing user data, but random write performance deteriorates due to unpredictable performance during collection

Engineering Contradiction:
Improveempty block availabilityVSAvoidrandom write performance
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The sustain detector determines whether random write performance is in a sustain state before and during garbage collection operations. By preliminarily assessing performance sustainability based on valid page count values, the system can proactively adjust write throttling settings to maintain reliable random write performance while performing garbage collection to secure empty blocks.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If write throttling is applied during garbage collection, then random write performance is maintained, but write latency increases

Engineering Contradiction:
Improverandom write performanceVSAvoidwrite latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The memory controller dynamically adjusts write throttling settings based on the sustain state determination. When random write performance is determined to be in a sustain state, the controller can apply write throttling to maintain performance reliability. When not in a sustain state, the controller reduces or eliminates throttling to minimize write latency, creating a dynamic adaptation mechanism.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the write throttling parameter based on the sustain state of random write performance. By monitoring valid page count values and determining sustain state, the controller adjusts the throttling parameter to balance between maintaining performance reliability and minimizing write latency.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If valid page count values are monitored to determine sustain state, then random write performance can be managed effectively, but device complexity increases

Engineering Contradiction:
Improverandom write performance managementVSAvoidcontroller structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The sustain detector is integrated into the existing memory controller structure, allowing the controller to perform multiple functions: monitoring valid page count values, determining sustain state, and adjusting write throttling settings. This multi-functionality approach manages random write performance effectively without requiring a completely separate control system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260010473A1Memory controller and method of operating the same
Publication Date: 2026.01.08 SK HYNIX INC
  • US20260010473A1 patent drawing
  • US20260010473A1 patent drawing
  • US20260010473A1 patent drawing

AI summary

The present technology relates to an electronic device. According to the present technology, a memory controller may include a garbage collection controller and a sustain detector. The garbage collection controller may generate garbage collection information including valid page count values of victim memory blocks on which garbage collection is to be performed among a plurality of memory blocks included in a memory device. The sustain detector in communication with the garbage collection controller may generate sustain information indicating whether random write performance for the memory device is in a sustain state in which a random write performance value related to a capability of the random write performance is greater than or equal to a threshold value based on the garbage collection information.