Non-Volatile Memory Cache Hibernation Resume Acceleration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of evicting run-time user data from a non-volatile memory cache to make room for hiberfile data during hibernation and recovering this data upon resume involves additional write operations, which shorten the effective operational life of the non-volatile memory and complicate the system's power management.
Innovation Solution
Utilizing non-volatile memory as a disk cache to store hiberfile data before hibernation and employing a write-through cache policy to ensure data integrity, allowing for faster system resume without waiting for the disk to spin up, while also using reserve space in the NV memory to store more hiberfile data and reduce the need for additional block erase operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If hiberfile data is stored in non-volatile memory cache before hibernation, then resume time is shortened by avoiding disk spin-up delay, but additional write operations are required to evict run-time user data and recover user data, which shortens the effective operational life of the non-volatile memory
Solution Approach 1:
The system performs preliminary actions by pre-writing hiberfile data to the non-volatile memory cache before hibernation occurs. This allows the data to be ready for immediate retrieval upon resume, eliminating the need to wait for disk spin-up. The preliminary write operation prepares the storage medium in advance, directly reducing resume time without requiring additional operations during the resume process itself.
2Reliability
If additional write operations are performed to evict and recover user data during hibernation and resume, then data integrity is maintained, but the effective operational life of non-volatile memory is shortened due to increased block erase operations
Solution Approach 1:
The invention extracts the hiberfile data from the volatile memory and places it directly into the non-volatile memory cache before hibernation. By separating the hiberfile data from the run-time user data and storing it in a dedicated non-volatile cache, the system eliminates the need for additional write operations during resume to recover user data. This extraction approach maintains data integrity while preserving the operational life of the non-volatile memory by avoiding repeated erase cycles.
Data Source
AI summary
A non-volatile (NV) memory may store hiberfile data before entering a hibernate state, and retrieve the data upon resume from hibernation. The reserve space in the NV memory (i.e., the erased blocks available to be used while in the run-time mode) may be used to store hiberfile data. Further, a write-through cache policy may be used to assure that all of the hiberfile data saved in cache will also be stored on the disk drive during the hibernation, so that if the cache and the disk drive are separated during hibernation, the full correct hiberfile data will still be available for a resume operation.