Compressed Memory Lookup Tables for Faster Address Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory compression techniques suffer from high latency and bandwidth overhead due to computationally-intensive compression and decompression operations, fragmented memory utilization, and inefficient lookup table caching, leading to suboptimal performance.

Innovation Solution

Implementing an improved lookup table scheme that uses partitioned memory with configurable compression ratios and identifiers to store compressed data, reducing the size of the lookup table and enhancing cache hit rates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If memory compression is implemented using traditional lookup table schemes, then data storage capacity is increased, but latency and bandwidth overhead increase due to computationally-intensive compression and decompression operations

Engineering Contradiction:
Improvedata storage capacityVSAvoidlatency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The memory space is divided into multiple partitions, each with its own compression ratio and identifier. This segmentation allows the system to manage compressed data more efficiently by organizing it into discrete, addressable units, reducing the computational overhead required for compression and decompression operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An improved lookup table scheme is introduced as an intermediary mechanism to map host addresses to compressed memory locations. This lookup table uses partition identifiers and segment identifiers to efficiently translate addresses without requiring full decompression, thereby reducing latency and bandwidth overhead while maintaining data storage capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If traditional lookup table caching is used, then address translation is performed, but cache hit rates are suboptimal due to inefficient lookup table organization

Engineering Contradiction:
Improveaddress translation efficiencyVSAvoidcache hit rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The lookup table is reorganized using partition identifiers and segment identifiers, dividing the address translation task into smaller, more manageable segments. This segmentation improves cache utilization by allowing the system to search smaller, more targeted portions of the lookup table, thereby increasing cache hit rates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The lookup table scheme changes its organizational parameters by incorporating partition identifiers and segment identifiers alongside traditional address mappings. This parameter change enables more efficient caching strategies and improves overall address translation efficiency without sacrificing cache hit rates.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If memory is used for storing compressed data with full address tracking, then data accessibility is maintained, but memory utilization is fragmented and inefficient

Engineering Contradiction:
Improvedata accessibilityVSAvoidmemory utilization efficiency
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential identification elements (partition identifier and segment identifier) from the full address, storing these compact keys in the lookup table rather than complete address mappings. This extraction maintains data accessibility while significantly improving memory utilization efficiency by reducing the overhead required for address tracking.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of storing full addresses and deriving partition/segment information during translation, the system inverts the approach by pre-storing partition and segment identifiers directly in the lookup table. This inversion enables more efficient memory utilization while maintaining ease of data access through the improved lookup scheme.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS20260016956A1Memory compression with improved lookup table scheme
Publication Date: 2026.01.15 MICRON TECHNOLOGY INC
  • US20260016956A1 patent drawing
  • US20260016956A1 patent drawing
  • US20260016956A1 patent drawing

AI summary

A system can include a memory; and a processing device, operatively coupled with the memory, to perform operations including: receiving a request to access data; identifying a location among a plurality of locations on a memory partition, among a plurality of memory partitions of the memory, by using a segment identifier and a unit offset address, wherein each of the plurality of locations is associated with a corresponding segment identifier, and wherein the unit offset address is determined in view of a compression ratio range associated with the memory partition; and performing an operation regarding the data at the identified location on the memory partition.