Controller Namespace Management via Segmented Allocation Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current memory systems face complexity in managing allocation tables, leading to inefficiencies in namespace management and increased time required for operations such as allocation and release, due to the need for frequent updates and storage of extensive mapping information.
Innovation Solution
A controller is designed with a storage region for mapping information between logical and physical addresses, an interface region for storing allocation information, and a processing region to manage logical units, allowing for efficient allocation and release of namespaces by using a logical region table and an allocation table, where the allocation table is updated without altering the logical region table, reducing operational time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If mapping information between logical addresses and physical addresses is stored in detail, then allocation accuracy is improved, but device complexity and memory capacity requirements increase
Solution Approach 1:
The allocation table is segmented into two distinct parts: a logical region table storing mapping information between logical addresses and physical addresses, and an allocation table storing only allocation status and capacity information. This segmentation allows detailed mapping information to be separated from allocation management information, reducing the complexity of overall allocation table management while maintaining accurate mapping capabilities.
Solution Approach 2:
The patent extracts the detailed mapping information function from the allocation table and places it in a separate logical region table. The allocation table retains only essential allocation management data (status and capacity), thereby simplifying allocation table management while preserving the ability to track logical-to-physical address mappings through the dedicated logical region table.
2Measurement precision
If extensive mapping information is stored and updated frequently, then namespace management accuracy is improved, but operational time increases
Solution Approach 1:
By segmenting allocation management into two tables, the patent enables independent update operations. The allocation table can be updated quickly with only status and capacity information, while the logical region table handles detailed mapping updates separately. This reduces the time required for allocation and release operations as the allocation table updates are simpler and faster.
Solution Approach 2:
The patent extracts detailed mapping update operations from the allocation table management process. Since the allocation table stores only essential allocation information rather than complete mapping details, updates to allocation status and capacity can be performed more rapidly without the overhead of updating extensive mapping information, thus reducing operational time while maintaining namespace management accuracy through the separate logical region table.
3Adaptability or versatility
If detailed allocation information is stored for all logical regions, then namespace management capability is improved, but memory capacity requirements increase
Solution Approach 1:
The patent segments allocation information storage into two tables with different functions and size requirements. The allocation table stores only compact allocation status and capacity information for each logical unit, while the logical region table stores the detailed mapping information. This segmentation reduces the memory capacity required for allocation table operations while maintaining full namespace management capability through the combined information in both tables.
Solution Approach 2:
The patent extracts detailed mapping information from the allocation table structure and places it in a separate logical region table. The allocation table retains only essential allocation management data, significantly reducing its memory footprint. Full namespace management capability is preserved because the logical region table contains the detailed mapping information that complements the allocation table's compact representation.
Data Source
AI summary
There are provided a controller and a memory system having the controller. The controller includes: a first storage area configured to store mapping information between logical addresses of logical regions of a storage device coupled to the controller and physical addresses of memory blocks of the storage device, the logical regions being divided into logical units including a first logical unit; and a second storage area configured to store allocation information on logical addresses of logical regions allocated to the first logical unit, each of the logical regions allocated to the first logical unit having a corresponding index, wherein the second storage area is further configured to store a location table for the first logical unit that includes index information having a smallest index corresponding to a logical region allocated to the first logical unit without having other indices corresponding to remaining logical regions allocated to the first logical unit and number information on a total number of the logical regions allocated to the first logical unit.