Memory Sub-System Data Block Switching for Write Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional memory sub-systems face reduced write performance due to the inability to write host data to available cache data blocks in SLC mode when user space data blocks are not closed, resulting in increased write latency as incoming host data is written to user space data blocks in XLC mode instead.
Innovation Solution
The implementation of a second host cursor to indicate a second available data block allows host data to be written to cache data blocks in SLC mode even when user space data blocks are not closed, reducing write operation latency by enabling the selection of an appropriate data block for writing incoming host data based on availability and mode.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the memory sub-system writes host data to user space data blocks in XLC mode when user space data blocks are not closed, then data storage is maintained, but write latency increases and write performance decreases
Solution Approach 1:
The memory sub-system is segmented into cache portion and user space portion, with separate host cursors managing each. The first host cursor manages user space data blocks while the second host cursor manages cache data blocks, allowing independent operation and selection of optimal write targets based on availability and performance requirements
Solution Approach 2:
The second host cursor acts as an intermediary mechanism that enables writing to cache data blocks in SLC mode even when user space data blocks are not closed. This intermediary cursor provides an alternative write path that bypasses the latency issue of writing to unclosed user space blocks
2Device complexity
If the memory sub-system uses a single host cursor to manage user space data blocks, then management is simplified, but the ability to write to cache data blocks in SLC mode is lost when user space blocks are not closed
Solution Approach 1:
The single host cursor management is segmented into two separate host cursors: the first host cursor for user space data blocks and the second host cursor for cache data blocks. This segmentation allows the system to maintain simplified management within each portion while enabling high-performance SLC writes to cache blocks independently of user space block closure status
Solution Approach 2:
The dual host cursor implementation provides multi-functionality where the system can selectively write to either user space data blocks or cache data blocks based on availability and performance requirements, making the cursor system adaptable to different write scenarios
Data Source
AI summary
Host data can be written to a first portion of a memory sub-system in a first write mode. An indication can be received that a data block of a second portion of the memory sub-system is available to be written to in a second write mode. In response to receiving the indication, it is determined to write a second portion of the host data to the data block of the second portion. In response to determining to write the second portion of the host data to the data block of the second portion, the second portion of the host data is written to the second available data block in the second write mode prior to closing the first available data block in the first write mode.