Memory Module Runtime Backup via Volatile to Non-Volatile Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing storage systems face challenges in maintaining data consistency and preventing data loss in volatile memory due to the slow data access operations in persistent secondary storage, especially during system faults or power loss.
Innovation Solution
Implementing a memory module with both volatile and non-volatile memory for caching data, where data is backed up from volatile to non-volatile memory during runtime, either opportunistically during idle times or in response to specific events, to prevent data loss and reduce system performance degradation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If data is cached in volatile memory for higher-speed access, then system performance is improved, but data loss risk increases during system faults or power loss
Solution Approach 1:
The memory module is segmented into two distinct memory types: volatile memory for high-speed data access and non-volatile memory for data safety. This segmentation allows the system to simultaneously achieve fast access speeds and data protection by storing data in appropriate memory types based on access frequency and importance requirements
Solution Approach 2:
The non-volatile memory acts as an intermediary between the volatile memory and persistent secondary storage. It provides a safety buffer that protects against data loss during power loss or system faults, while maintaining the high-speed access characteristics of volatile memory for active data
2Reliability
If data is frequently written back to persistent secondary storage to maintain consistency, then data consistency is improved, but system performance degradation increases due to slow access operations
Solution Approach 1:
The patent introduces a new dimension of storage hierarchy by adding non-volatile memory between volatile memory and persistent secondary storage. This creates a three-tier storage architecture that resolves the contradiction by providing both fast access (volatile memory) and data consistency (non-volatile memory as backup) without requiring frequent slow write operations to persistent storage
3Reliability
If runtime backup operations are implemented within the memory module, then data safety is improved without involving persistent storage, but device complexity increases
Solution Approach 1:
The patent merges the backup function directly into the memory module by integrating non-volatile memory with volatile memory in a single module. This combining approach enables runtime backup operations to occur within the memory module itself, eliminating the need for complex external backup mechanisms while maintaining data safety
Data Source
AI summary
During runtime of a system, a memory controller is caused to relinquish control of a memory module that includes a volatile memory and a non-volatile memory. After the triggering, an indication is activated to the memory module, the indication causing a backup operation in the memory module, the backup operation being controlled by an internal controller in the memory module, and the backup operation involving a transfer of data from the volatile memory to the non-volatile memory in the memory module.