Priority Address Cache Management for Non-Volatile Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage cache management techniques in non-volatile memory devices are inefficient due to reliance on simple heuristics like FIFO or aging algorithms, which do not optimally manage the limited intermediate storage (IS) memory, leading to suboptimal write and read performance.

Innovation Solution

A method that involves a memory controller using a priority address table to manage IS memory, where priority host data is identified and kept in IS memory, while non-priority data is relocated to main storage (MS) memory, based on user selection and usage monitoring, allowing for improved performance by prioritizing critical data access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If simple heuristics like FIFO or aging algorithms are used for cache management, then the system is easy to implement, but write and read performance deteriorates

Engineering Contradiction:
Improveease of implementationVSAvoidwrite and read performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent changes the parameter of cache management from simple temporal heuristics to priority-based classification. By introducing priority levels and classification mechanisms, the system transforms the management approach to optimize both performance and resource utilization effectively.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system enables self-service through automated priority-based cache management. The cache controller automatically classifies data, determines priority levels, and manages relocation without requiring complex external intervention, thereby maintaining ease of operation while improving performance.

Inventive Principle:
Principle #25Self-service

2Speed

If more data is kept in IS memory, then read performance improves, but the storage capacity available for other data decreases

Engineering Contradiction:
Improveread performanceVSAvoidstorage capacity availability
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent applies local quality by differentiating cache management for different data types. Instead of uniform treatment, the system assigns different priority levels and retention policies to different data, allowing critical data to occupy IS memory while less critical data is relocated to MS memory, thus optimizing both read performance and storage capacity utilization.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically changes the parameter of data retention based on priority classification. By introducing priority as a variable parameter, the system can adaptively determine which data should remain in IS memory, balancing read performance requirements with available storage capacity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If frequent relocation occurs to free up IS memory, then cache hit rate improves, but write throughput deteriorates

Engineering Contradiction:
Improvecache hit rateVSAvoidwrite throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent ensures continuity of useful action by minimizing disruptive relocation operations. Through priority-based management, the system maintains stable data in IS memory longer, reducing the frequency of relocation operations and thereby maintaining high write throughput while still achieving acceptable cache hit rates through intelligent prioritization.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system changes the parameter of relocation frequency based on data priority. Low-priority data is relocated less frequently, allowing write operations to proceed without interruption, while high-priority data remains in IS memory to maintain cache hit rates, thus balancing both metrics.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If IS memory is used as a safe-zone for quick data storage, then write safety improves, but the storage capacity for main data decreases

Engineering Contradiction:
Improvewrite safetyVSAvoidstorage capacity for main data
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by designating specific portions of IS memory for safe-zone functionality based on data priority. Critical data requiring immediate safe storage is directed to IS memory, while less critical data is stored in MS memory, thus providing write safety for important data without significantly reducing overall storage capacity availability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10776268B2Priority addresses for storage cache management
Publication Date: 2020.09.15 SANDISK TECHNOLOGIES LLC
  • US10776268B2 patent drawing
  • US10776268B2 patent drawing
  • US10776268B2 patent drawing

AI summary

Techniques for management of IS memory in a non-volatile storage device, and methods for use therewith, are described herein. The non-volatile storage device can include non-volatile memory, wherein a portion of the non-volatile memory is designated as intermediate storage (IS) memory and another portion of the non-volatile memory is designated as main storage (MS) memory. The IS memory may have lower read and write latencies than the MS memory. A host device may provide priority addresses to a memory controller with an indication that host data having one of the priority addresses is to receive priority to remain in IS memory over other host data.