Rolling XOR Protection for Flash Storage Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Flash storage devices employing multi-level cell (MLC) technology face challenges such as wordline to wordline shorts during the write process, leading to data reliability issues and the need for effective XOR signature management to prevent data loss, especially during power failures and other exceptions.
Innovation Solution
A storage device controller generates and manages XOR signature metadata by appending it to data strings, XORing them with existing signatures, and storing the updated signatures in a single-level cell (SLC) non-volatile memory, enabling recovery from power losses and other exceptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If direct write to MLC is used, then write latency is improved, but data reliability deteriorates due to WL2WL shorts
Solution Approach 1:
The patent introduces SLC storage as an intermediary component in a hybrid storage architecture. Host data is first written to SLC blocks (reliable storage), then relocated to MLC blocks (high-speed storage) after verification. This mediator approach allows the system to enjoy both reliability from SLC and speed from MLC, resolving the contradiction between write latency and data reliability.
Solution Approach 2:
The storage system is segmented into two distinct parts: SLC blocks for reliable initial storage and MLC blocks for high-speed bulk storage. This segmentation allows different functions to be performed by different storage types, with SLC handling reliability-critical operations and MLC handling performance-critical operations, thereby resolving the latency-reliability tradeoff.
2Reliability
If SLC first approach is used, then data reliability is improved, but sustained write performance deteriorates due to frequent relocation requirements
Solution Approach 1:
The system performs preliminary verification and validation of data before initiating relocation from SLC to MLC. This preliminary action ensures data integrity is confirmed, allowing the system to minimize unnecessary relocation operations and optimize the write path for sustained performance while maintaining reliability.
Solution Approach 2:
The patent implements a dynamic write path that adapts based on data characteristics and storage conditions. The system can dynamically choose between direct MLC writing (when reliability risks are low) or SLC-first approach (when reliability is critical), optimizing sustained write performance by selecting the appropriate path dynamically rather than following a fixed procedure.
3Reliability
If SLC first approach is used, then data reliability is improved, but device endurance deteriorates due to double writing requirement
Solution Approach 1:
The system incorporates feedback mechanisms that track data movement statistics and wear distribution across SLC and MLC blocks. Based on this feedback, the system can optimize write distribution, perform wear-leveling, and intelligently manage the relocation process to reduce unnecessary double-writes, thereby extending device endurance while maintaining reliability benefits.
4Quantity of substance
If rolling XOR is used, then overprovisioning is minimized, but XOR signature management complexity increases
Solution Approach 1:
The patent uses copying mechanisms to manage XOR signatures efficiently. Instead of maintaining complex metadata structures, the system creates copies of necessary signature information and stores them in a simplified format. This copying approach reduces the management overhead and complexity while maintaining the benefits of rolling XOR and minimizing overprovisioning requirements.
Data Source
AI summary
Systems, apparatus and methods for generation of XOR signature metadata and XOR signature management are presented. In one or more embodiments, a storage device controller includes a host interface, configured to receive one or more string lines (SLs) of data from a host, the one or more SLs to be programmed into a non-volatile memory (NVM), and processing circuitry. The processing circuitry is configured to, for each of the one or more SLs, generate signature metadata and provide the signature metadata in a header of the SL. The processing circuitry is still further configured to XOR two or more of the SLs with their respective signature metadata to generate a snapshot, and write the snapshot to the NVM.