Tiered Memory and Storage Rollback With Write-Order Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional rollback technologies face challenges in reliably restoring data states in cached and tiered storage systems due to out-of-order data flushing and write coalescing, leading to synchronization issues between front-end and back-end devices.
Innovation Solution
Implementing a system that coordinates front-end and back-end media devices in tiered storage systems to enforce write-ordered FIFO policies and track write insertion order and time, allowing for controlled rollback of data states across multiple memory levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If out-of-order data flushing and write coalescing are used in cached storage systems, then data migration efficiency between tiers is improved, but synchronization reliability between front-end and back-end devices deteriorates
Solution Approach 1:
The system performs preliminary actions by tracking and recording the order and timing of write insertions before they are flushed. This creates a log of write operations that can be used to reconstruct the correct write order during rollback operations, ensuring synchronization reliability is maintained even when out-of-order flushing occurs for performance optimization.
Solution Approach 2:
The system implements feedback mechanisms by monitoring and tracking write operations in real-time, recording their order and timing information. This feedback data is then used to adjust and coordinate rollback operations between front-end and back-end devices, ensuring that synchronization reliability is maintained while allowing out-of-order flushing for improved data migration efficiency.
2Device complexity
If conventional rollback technologies are used without coordination, then implementation simplicity is maintained, but data restoration reliability in tiered storage systems deteriorates
Solution Approach 1:
The system segments the rollback operation into coordinated steps that independently manage front-end and back-end devices. By dividing the rollback process into manageable segments that can be executed in a coordinated manner, the system maintains implementation simplicity while achieving reliable data restoration through structured progression through each segment.
Solution Approach 2:
The system introduces an intermediary coordination mechanism that mediates between front-end and back-end devices during rollback operations. This intermediary layer tracks write operations and coordinates the rollback process, ensuring data restoration reliability without requiring complex direct coordination between all components, thus maintaining implementation simplicity.
3Reliability
If write-ordered FIFO policies are enforced, then data synchronization between tiers is improved, but write performance and throughput deteriorate
Solution Approach 1:
The system applies dynamics by making the write ordering policy adaptive rather than static. It dynamically tracks and records write order information on a per-transaction basis, allowing the system to maintain synchronization reliability when needed while permitting out-of-order operations when performance optimization is prioritized, thus balancing data synchronization with write performance.
Solution Approach 2:
The system changes the parameter of write ordering from a fixed strict FIFO requirement to a flexible tracked order mechanism. By recording write insertion order and timing as parameters rather than enforcing rigid ordering, the system maintains data synchronization reliability through accurate tracking while allowing performance-optimized write paths, thus improving both synchronization and write performance.
Data Source
AI summary
An embodiment of an electronic apparatus may comprise one or more substrates, and circuitry coupled to the one or more substrates, the circuitry to track transactions that access a first memory level of a multi-level memory, control access to at least the first memory level of the multi-level memory, and control a roll back of at least the first memory level of the multi-level memory based on the tracked transactions. In another embodiment, the circuitry is to control a roll back of a multi-level memory in response to a request to roll back the multi-level memory. Other embodiments are disclosed and claimed.