Storage Controller Minimum Write Size Enforcement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Storage devices, such as SSDs, face inefficiencies in programming time and throughput due to the need to write multiple small commands, which slows down the programming process and decreases overall efficiency.
Innovation Solution
The storage device is divided into zones with a controller that restricts host devices to send write commands in a minimum write size, calculated based on the number of erase blocks, pages per cell, and metadata space, optimizing programming efficiency by ensuring data is written in full wordline sizes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the storage device writes multiple small commands to the memory device as received, then the host device can send data of any size, but the programming time increases and overall programming efficiency decreases
Solution Approach 1:
The patent changes the parameter of write command size by implementing a minimum write size requirement. The controller calculates and enforces a minimum write size based on the memory device's architecture (wordline size, erase block structure), transforming the system from accepting arbitrary small writes to requiring writes of optimized size, thereby improving programming efficiency while maintaining adaptability through buffer aggregation
Solution Approach 2:
The controller performs preliminary actions by buffering incoming write commands and aggregating them before writing to the memory device. Instead of immediately writing each small command as received, the controller accumulates data in a buffer until the minimum write size is reached, then performs a single optimized write operation, reducing the number of programming cycles required
2Productivity
If the storage device restricts host device to send write commands in minimum write size, then programming efficiency increases, but the host device loses flexibility in command size
Solution Approach 1:
The controller acts as an intermediary between the host device and the memory device. It receives write commands from the host, aggregates them in a buffer to meet the minimum write size requirement, and then issues optimized write commands to the memory device. This intermediary role shields the host from the minimum size restriction while still achieving efficient programming
Solution Approach 2:
The controller performs preliminary aggregation of write commands in a buffer before issuing them to the memory device. By accumulating data until the minimum write size is reached, the controller prepares optimized write operations in advance, improving programming efficiency without requiring the host to be aware of or enforce minimum size constraints
Data Source
AI summary
The present disclosure generally relates to methods of operating storage devices. The storage device comprises a controller and a storage unit divided into a plurality of zones. The storage unit comprises a plurality of dies, where each die comprises two planes. One erase block from each plane of a die is selected for zone formation. Each erase block comprises a plurality of wordlines. A zone comprises one or two dies dedicated to storing parity data and a plurality of dies dedicated to storing user data. The zone further comprises space devoted for controller metadata. The storage device restricts a host device to send write commands in a minimum write size to increase programming efficiency. The minimum write size equals one wordline from one erase block from each plane of each die in the zone dedicated to storing user data minus the space dedicated to metadata.