SSD Atomicity Awareness for System File Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current storage systems lack awareness of the specific properties of system files, such as atomicity, leading to inefficient storage handling.
Innovation Solution
Implementing a system where a host marks specific logical block address (LBA) ranges as belonging to atomic or log files, allowing the storage device to treat these ranges as single atomic units or incremental update units, respectively, and disassembling write commands into smaller sectors for atomic writing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If storage devices treat all data uniformly without file type awareness, then device complexity is reduced, but storage optimization and data integrity for specific file types (atomic files, log files) deteriorate
Solution Approach 1:
The patent segments the storage handling process by file type, creating distinct processing paths for atomic files, log files, and temporary files. The host device annotates file types and the storage device applies type-specific operations, dividing the monolithic storage system into specialized subsystems that handle different file types with appropriate atomicity and reliability guarantees.
Solution Approach 2:
The patent applies different quality levels of atomicity and protection to different regions of storage based on file type. Atomic files receive full atomic write protection, log files receive append-only protection with crash consistency, and temporary files receive minimal protection. This local differentiation optimizes reliability for critical files while maintaining acceptable performance for non-critical files.
2Reliability
If storage devices implement comprehensive file type awareness and special handling, then storage optimization and data integrity improve, but device complexity increases
Solution Approach 1:
The patent introduces an intermediary annotation layer where the host device marks files with type information (atomic, log, temporary) before transmission to the storage device. This intermediary mechanism allows the storage device to implement complex file-type-specific handling without embedding file system logic within the storage device itself, maintaining a clear separation of concerns.
Solution Approach 2:
The patent implements partial file type handling by focusing on three major file types (atomic, log, temporary) rather than attempting to handle all possible file types comprehensively. This selective approach provides sufficient optimization for critical scenarios while avoiding the exponential complexity growth that would result from exhaustive file type classification and handling.
3Reliability
If atomic files are written as complete units, then data integrity is ensured, but write time and storage efficiency deteriorate due to inability to perform incremental updates
Solution Approach 1:
The patent segments large atomic file writes into smaller chunks that can be processed incrementally through a pipeline, while maintaining atomicity guarantees through coordination mechanisms. The host device divides the atomic file content into manageable segments and the storage device processes them in sequence with proper acknowledgment and rollback capability, enabling parallel preparation while ensuring atomic commitment.
4Productivity
If log files allow incremental appends, then write efficiency improves, but risk of partial writes and data corruption increases
Solution Approach 1:
The patent applies preliminary actions to log file writing by pre-allocating space, pre-checking write boundaries, and preparing crash recovery mechanisms before actual writes occur. The storage device establishes write boundaries and checkpoint markers in advance, so that if a crash occurs during an append operation, the system can reliably identify the last successful write point and maintain consistency without requiring complete rewrite of the log file.
Data Source
AI summary
Instead of a system with no awareness to the specific properties of the described system files, such as atomicity of different types of system files, utilize the special characteristics of the corresponding system files to optimize storage handling. A host marks a certain logical block address (LBA) range as belonging to an atomic file. That entire range will be treated as a single atomic unit. Conversely, an LBA range being used to append to a log file may have very small atomic units, allowing for incremental updates without changing the atomicity of the rest of the media. When a write command is passed, the write command will have a certain length. Depending on the length of the write command, the device can disassemble the write command into smaller write sectors of the smallest possible write portion. The device will then write the small write portions to a storage location, while keeping an atomic principle of each of the small write portions.