Namespace Map Allocation Without Free-List Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory sub-systems suffer from redundancy in namespace management due to the use of both a free list and a namespace map, occupying unnecessary memory resources and reducing efficiency and latency.

Innovation Solution

A memory sub-system that manages namespace blocks using a unified namespace map without a separate free list, utilizing indicators within the namespace map to differentiate between allocated and unallocated blocks, thereby eliminating redundancy and enhancing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a separate free list is used alongside the namespace map, then namespace block allocation can be tracked, but memory redundancy increases and efficiency decreases

Engineering Contradiction:
Improvenamespace block allocation trackingVSAvoidmemory structure redundancy
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the free list functionality into the namespace map by using a reserved entry at a predetermined location within the namespace map to indicate available namespace blocks. This eliminates the need for a separate free list structure, reducing memory redundancy while maintaining allocation tracking capability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The namespace map is designed to serve multiple functions: it stores namespace block mappings, tracks allocated blocks through the reserved entry mechanism, and provides allocation information without requiring separate data structures. This multi-functionality reduces overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If a separate free list is maintained, then allocation status can be managed, but memory resources are occupied unnecessarily

Engineering Contradiction:
Improveallocation status managementVSAvoidmemory resources
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The free list functionality is merged into the namespace map structure itself. The reserved entry at the predetermined location serves dual purposes: it is part of the namespace map's structural framework and simultaneously indicates the availability of namespace blocks for allocation, eliminating the need for separate memory resources.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If both free list and namespace map are used, then comprehensive namespace management is achieved, but latency increases due to additional memory access

Engineering Contradiction:
Improvenamespace management capabilityVSAvoidaccess latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

By combining the free list functionality into the namespace map, the patent reduces the number of separate memory structures that must be accessed. The reserved entry within the namespace map provides allocation status information in a single memory access, eliminating the sequential access pattern required when querying both a free list and namespace map separately.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250355802A1Namespace management for memory sub-systems
Publication Date: 2025.11.20 MICRON TECHNOLOGY INC
  • US20250355802A1 patent drawing
  • US20250355802A1 patent drawing
  • US20250355802A1 patent drawing

AI summary

Methods, systems, and devices for clock domain crossing queue are described. A memory sub-system can generate a namespace map having a set of namespace blocks associated with a memory sub-system. The namespace blocks can include one or more logical block addresses associated with the memory sub-system. One namespace block of the set of namespace blocks can include an indication that can indicate that the namespace block and each namespace block following the namespace block are available for mapping. The memory sub-system can receive a request to create a namespace and sequentially map one or more available namespace blocks to the namespace according to the ordering of the namespace map, including the namespace block with the indication.