Dual Changelog Mapping for Continuous Memory Throughput
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Memory systems face challenges in supporting higher throughput without increasing the size of changelogs, leading to paused or delayed continuous host access operations.
Innovation Solution
Implementing concurrent changelog management with a foreground changelog for new mappings and a background changelog for old mappings, transferring old mappings to a volatile memory while new mappings are received, and updating non-volatile memory when the background changelog is emptied.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the changelog size is increased to support higher throughput, then the throughput capability is improved, but the memory space consumption increases
Solution Approach 1:
The patent divides the changelog into two separate changelogs: a foreground changelog for storing new mappings and a background changelog for storing old mappings. This segmentation allows the system to maintain a limited foreground changelog size while using the background changelog to manage historical mappings, thereby supporting higher throughput without proportionally increasing the active changelog size.
Solution Approach 2:
The patent introduces a temporal dimension to changelog management by separating mappings into foreground (new) and background (old) categories. This dimensional separation allows the system to manage mappings across different time periods independently, enabling higher throughput by retaining older mappings in the background changelog without consuming space in the foreground changelog.
2Productivity
If the changelog size is increased to support higher throughput, then the throughput capability is improved, but the device complexity increases
Solution Approach 1:
The patent segments the changelog management process into distinct foreground and background changelogs with clear separation of responsibilities. The foreground changelog handles new mappings while the background changelog manages old mappings, simplifying the overall management complexity by dividing a complex single-changelog system into two more manageable components.
Solution Approach 2:
The patent introduces a mapping table as an intermediary structure that mediates between the foreground and background changelogs. The mapping table stores mappings from logical addresses to physical addresses, facilitating efficient translation and coordination between the two changelogs without requiring direct complex interactions between them.
3Reliability
If continuous host access operations are paused to manage changelog, then the data integrity is maintained, but the productivity decreases
Solution Approach 1:
The patent performs preliminary actions by pre-allocating and pre-managing foreground and background changelogs before host access operations need to pause. The system prepares the background changelog in advance to receive old mappings, allowing continuous host access operations to proceed without interruptions for changelog management.
Solution Approach 2:
The patent enables continuity of useful action by implementing concurrent foreground and background changelog operations that do not require pausing host access. The foreground changelog continues to receive new mappings while the background changelog simultaneously manages old mappings, maintaining continuous productivity without sacrificing data integrity.
Data Source
AI summary
Methods, systems, and devices for techniques for changelog management are described. A memory system may implement a foreground changelog associated with storing new mappings received from a host system and a background changelog associated with storing old mappings received from the foreground changelog. The memory system may be configured to transfer old mappings from the background changelog to a mapping table stored at a volatile memory of the memory system, while new mappings are received at the foreground changelog. Then, the memory system may transfer the new mappings from the foreground changelog to the background changelog based on satisfying a capacity of the foreground changelog. The memory system may update the mapping table with the old mappings each time the background changelog is emptied, and may flush the mapping table to a mapping table stored at a non-volatile memory of the memory system other times the background changelog is emptied.