Memory Subsystem Namespace Mapping With Integrated Free-Block Tracking

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, which occupies unnecessary memory and reduces efficiency and latency.

Innovation Solution

A memory sub-system that manages namespace blocks using a single namespace map without a separate free list, utilizing indicators within the namespace map to differentiate between allocated and unallocated blocks, allowing for efficient mapping and allocation of namespace blocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If both a free list and a namespace map are used to manage namespace blocks, then namespace allocation can be tracked, but memory redundancy increases and efficiency decreases

Engineering Contradiction:
Improvenamespace allocation trackingVSAvoidmemory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent combines the free list and namespace map into a single namespace map structure. The namespace map directly tracks the allocation state of each namespace block using status indicators (e.g., allocated, free, reserved), eliminating the need for a separate free list. This merging reduces memory redundancy while maintaining reliable namespace allocation tracking.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The namespace map is designed to serve multiple functions simultaneously: it tracks allocated blocks, identifies free blocks, and manages reserved blocks all within a single data structure. This multi-functionality replaces the traditional two-structure approach (free list + namespace map), reducing overall memory consumption while maintaining full namespace management capability.

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

2Ease of operation

If a separate free list is maintained alongside the namespace map, then free namespace blocks can be identified, but device complexity increases

Engineering Contradiction:
Improvefree block identificationVSAvoiddata structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges the free list functionality into the namespace map by incorporating status indicators that directly mark free blocks within the same data structure. This eliminates the need for separate free list maintenance and reduces operational complexity while preserving the ability to easily identify free namespace blocks.

Inventive Principle:
Principle #5Merging (Combining)

3Manufacturing precision

If redundant namespace management structures are used, then namespace blocks can be mapped accurately, but latency increases

Engineering Contradiction:
Improvenamespace block mapping accuracyVSAvoidmapping latency
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent combines multiple namespace management structures into a single unified namespace map, reducing the number of data structure operations required during namespace block mapping. This consolidation maintains mapping accuracy through comprehensive status tracking while reducing latency by eliminating redundant lookups and operations across separate structures.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12393510B2Namespace management for memory sub-systems
Publication Date: 2025.08.19 MICRON TECHNOLOGY INC
  • US12393510B2 patent drawing
  • US12393510B2 patent drawing
  • US12393510B2 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.