Storage Device Metadata Mapping for Selective Flash Flushes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Frequent updates and flushes of meta data in flash memory devices cause flash wear and degrade performance, reducing the lifespan reliability of non-volatile memory devices.
Innovation Solution
A storage device with a non-volatile memory device and a storage controller that includes a user area and a meta area, where meta data is managed through sub-address mapping tables and meta data mapping tables, with controlled update and flush operations based on event occurrence, reducing the amount of meta data flushed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If meta data is frequently updated and flushed to ensure data consistency, then data reliability is improved, but flash wear increases and performance degrades
Solution Approach 1:
The address mapping table is divided into multiple sub-address mapping tables, each managing a specific range of logical addresses. This segmentation allows the system to update and flush only the necessary sub-tables rather than the entire address mapping table, reducing flash wear while maintaining data consistency.
Solution Approach 2:
The system performs partial updates by only flushing sub-address mapping tables that have been modified, rather than flushing the entire address mapping table. This selective approach reduces the frequency and volume of flash write operations, thereby reducing flash wear while ensuring that only necessary data is persisted.
2Reliability
If meta data is frequently updated and flushed to ensure data consistency, then data reliability is improved, but performance degrades
Solution Approach 1:
By segmenting the address mapping table into sub-tables, the system reduces the amount of data that needs to be flushed at once. This segmentation enables more efficient flush operations with reduced data transfer volumes, improving overall flush operation performance while maintaining data consistency through selective updates.
Solution Approach 2:
The system performs partial flush operations by identifying and flushing only the modified sub-address mapping tables. This approach significantly reduces the time and resources required for flush operations compared to flushing the entire address mapping table, thereby improving performance while ensuring data consistency for updated portions.
3Reliability
If the entire address mapping table is flushed to ensure data persistence, then data reliability is improved, but the amount of data to be flushed increases
Solution Approach 1:
The address mapping table is segmented into multiple sub-address mapping tables, each handling a specific portion of the address space. This segmentation enables the system to flush only the necessary sub-tables containing updated data, significantly reducing the total amount of data flushed while ensuring that all persistent changes are properly saved.
Solution Approach 2:
Instead of flushing the entire address mapping table, the system performs partial flushes by identifying and flushing only the modified sub-address mapping tables. This selective approach minimizes the quantity of data written to flash memory while maintaining complete data persistence for all updated entries.
Data Source
AI summary
A storage device includes a non-volatile memory device including a user area including a plurality of first memory blocks, and a meta area including an address mapping table including an address mapping information for the plurality of first memory blocks and a meta data mapping table including meta data for the address mapping table. The address mapping table includes a sub-address mapping table, and the meta data mapping table includes meta data for the sub-address mapping table. A storage controller of the storage device updates at least one of the meta data to perform a first update operation on the sub-address mapping table and address mapping information of the sub-address mapping table to perform a second update operation on the sub-address mapping table, and flushes the address mapping table into the meta area based on a result of the update.


