Dynamic Mapping Granularity Storage Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional storage device mapping systems have fixed granularity, leading to inefficiencies in mapping table usage and increased processing cycles due to Read-Modify-Write operations, especially when handling data of varying sizes, which occupies significant DDR DRAM and reduces SSD performance.
Innovation Solution
An Information Handling System with a storage controller engine that configures dynamic mapping granularity by associating multiple Logical Block Addresses (LBAs) with Logical Allocation Addresses (LAAs) and writes data to Physical Allocation Addresses (PAAs) based on a specified combined LBA size, reducing the need for multiple mapping entries and minimizing Read-Modify-Write operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If fixed mapping granularity of eight LBAs per LAA is used, then mapping table structure is simple, but mapping table occupies excessive DDR DRAM (up to 80%) and requires multiple mapping entries for large data writes
Solution Approach 1:
The patent implements dynamic mapping granularity by allowing the storage controller to adjust the number of LBAs associated with each LAA based on the actual data write size. Instead of a fixed 8-LBA granularity, the system can configure different granularities (e.g., 1, 2, 4, 8, 16, 32 LBAs per LAA) to match the data size, thereby optimizing mapping table usage and reducing DDR DRAM occupancy.
Solution Approach 2:
The patent changes the mapping granularity parameter dynamically based on data size. The storage controller receives configuration commands that specify the desired mapping granularity, and adjusts the LAA-LBA association accordingly. This parameter change allows the system to adapt to different data write scenarios, reducing the number of mapping entries required and freeing up DDR DRAM resources.
2Ease of manufacture
If fixed mapping granularity of eight LBAs per LAA is used, then mapping table implementation is straightforward, but Read-Modify-Write operations increase processing cycles and reduce SSD performance
Solution Approach 1:
The patent implements dynamic mapping granularity by allowing the storage controller to adjust the number of LBAs associated with each LAA based on the actual data write size. Instead of a fixed 8-LBA granularity, the system can configure different granularities (e.g., 1, 2, 4, 8, 16, 32 LBAs per LAA) to match the data size, thereby optimizing mapping table usage and reducing DDR DRAM occupancy.
Solution Approach 2:
The patent changes the mapping granularity parameter dynamically based on data size. The storage controller receives configuration commands that specify the desired mapping granularity, and adjusts the LAA-LBA association accordingly. This parameter change allows the system to adapt to different data write scenarios, reducing the number of mapping entries required and freeing up DDR DRAM resources.
3Quantity of substance
If dynamic mapping granularity is configured, then mapping table usage is optimized and DDR DRAM occupancy is reduced, but storage controller configuration complexity increases
Solution Approach 1:
The patent applies preliminary action by allowing the host system to configure the desired mapping granularity in advance through configuration commands received by the storage controller. This pre-configuration enables the storage controller to optimize mapping table usage and reduce DDR DRAM occupancy before actual data writes occur, avoiding the need for complex real-time adjustments during data operations.
4Productivity
If dynamic mapping granularity is configured, then direct data writing is enabled and processing overhead is reduced, but host system configuration requirements increase
Solution Approach 1:
The patent applies preliminary action by allowing the host system to configure the desired mapping granularity in advance through configuration commands received by the storage controller. This pre-configuration enables the storage controller to optimize mapping table usage and reduce DDR DRAM occupancy before actual data writes occur, avoiding the need for complex real-time adjustments during data operations.
Data Source
AI summary
A storage device includes a storage subsystem and a logical/physical storage location mapping database that maps LAAs to PAAs that identify physical locations in the storage subsystem. A storage controller receives a storage device mapping granularity configuration command from a host that identifies a number of LBAs to associate with a plurality of LAAs and, in response, associates each of the plurality of LAAs with the number of LBAs identified in the command. The storage controller then writes data to a PAA that includes a data size that is equal to a combined LBA size of the number of LBAs that were identified in the command and associated with each of the plurality of LAAs and maps, in the logical/physical storage location mapping database, the PAA to one of the plurality of LLAs that is associated the number of LBAs identified in the command.