Storage Controller Atomic Write Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for executing atomic write commands in storage devices with rewritable non-volatile memory modules are inefficient due to high resource and time consumption during recovery from sudden power-off events, making it difficult to determine the validity of write data.
Innovation Solution
A data writing method and storage controller that record meta data with specific identification codes and sizes for each write operation, allowing for efficient determination of write data validity during special events by differentiating between atomic write commands and ensuring data recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current methods for executing atomic write commands are used with host application support and unique command identification codes, then atomic write command effectiveness is achieved, but resource consumption and time consumption increase significantly
Solution Approach 1:
The storage device autonomously manages atomic write operations by embedding identification codes and sequence numbers directly in meta data structures, eliminating the need for host application intervention. The storage controller independently tracks write operations using unit crossing flags and validates atomicity through internal mechanisms, making the system self-sufficient for atomic write guarantee.
Solution Approach 2:
The invention extracts the atomic write management functionality from the host application layer and relocates it to the storage device layer. By separating the atomicity guarantee mechanism from host-dependent implementations, the system achieves atomic write reliability while reducing host resource consumption and improving overall working efficiency.
2Reliability
If host application support and unique command identification code sequences are used for atomic write commands, then atomic write effectiveness is achieved, but time consumption increases
Solution Approach 1:
The system performs preliminary actions by pre-allocating unique identification codes and sequence numbers to write commands before execution. Meta data structures are prepared with identification fields and unit crossing flags in advance, enabling rapid validation during sudden power-off recovery without time-consuming host application processing or complex code sequence verification.
Solution Approach 2:
The storage device independently handles atomic write validation and recovery operations using embedded identification codes, eliminating time-consuming host application involvement. The storage controller autonomously checks unit crossing flags and validates write completeness during power recovery, significantly reducing overall time consumption while maintaining atomic write effectiveness.
3Reliability
If meta data with identification codes and unit crossing flags is recorded for each write operation, then write data validity can be determined during special events, but device complexity increases
Solution Approach 1:
The meta data structure is segmented into distinct functional fields: identification codes for command recognition, sequence numbers for ordering, and unit crossing flags for boundary detection. This segmentation allows each field to serve a specific validation purpose during sudden power-off recovery, simplifying the complexity management by organizing data validation functions into modular, purpose-specific segments.
Solution Approach 2:
The meta data structure serves multiple functions simultaneously: it tracks write operations, validates atomicity, determines data validity during recovery, and manages sequence ordering. By making the meta data structure multi-functional, the invention reduces the need for separate data structures for each function, thereby managing overall device complexity while enhancing reliability.
4Reliability
If unit crossing flags and write identification codes are embedded in meta data, then atomic write validation is improved, but resource consumption increases
Solution Approach 1:
The system applies partial validation by using unit crossing flags only when necessary for atomic write boundary detection, rather than validating every single write operation with full identification code verification. This partial action approach reduces resource consumption while maintaining atomic write validation reliability for critical operations.
Solution Approach 2:
The invention changes the parameter representation by using compact bit-flag fields for unit crossing indicators instead of verbose descriptive data. This parameter optimization reduces the quantity of resources consumed for storing and processing validation information while maintaining the reliability of atomic write validation through efficient binary state representation.
Data Source
AI summary
A data writing method is provided. The method includes writing a first write data into a first physical sub-unit in a storage device according to a first write command; recording a first meta data corresponding to the first write data into the storage device; writing a second write data into a second physical sub-unit in the storage device; recording a second meta data corresponding to the second write data into the storage device. A second write identification code of the second meta data is set to be different from a first write identification code of the first meta data if the second physical unit is closely adjacent to the first physical unit and the second write data is written according to the second write command; and whether the second write data is valid or invalid is determined according to the second meta data if a special event occurs.