Virtual Data Transfer Between Memory and Storage Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional memory subsystem architectures expend energy and increase wear by physically moving data between system memory and storage memory domains, even when using nonvolatile memory (NVM) for both roles, due to physical separation and distinct memory media requirements.
Innovation Solution
A domain map is maintained to manage NVM block addresses, allowing data to be transferred between memory and storage domains without physical movement by switching the domain attribute of NVM block addresses, thus updating the domain map to reflect the data transfer while keeping the data in the same physical location.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If data is physically moved between system memory and storage memory domains, then data transfer is completed, but energy is expended and wear on NVM media increases
Solution Approach 1:
The patent creates a virtual copy of the data transfer process by maintaining domain map entries that represent data locations in different domains. Instead of physically moving data, the system updates domain map attributes to reflect the logical transfer, achieving the effect of data movement without the physical transfer overhead.
Solution Approach 2:
The patent replaces the mechanical/physical data movement mechanism with a logical/addressing mechanism. By updating domain map attributes and using address translation, the system substitutes physical data relocation with virtual address manipulation, eliminating the energy consumption and wear associated with physical movement.
2Loss of time
If data is physically moved between memory and storage domains, then data transfer is completed, but data transfer latency increases
Solution Approach 1:
The patent creates a virtual representation of data transfer through domain map updates. The domain map serves as a copy or abstraction layer that tracks data locations across domains, allowing the system to achieve transfer semantics without the time penalty of physical data movement.
Solution Approach 2:
The domain map acts as an intermediary between the processor and the physical memory/storage domains. By updating domain map attributes rather than moving data directly, the system introduces a virtual mediation layer that eliminates the latency of physical data transfer while maintaining the appearance of completed transfer operations.
3Object-affected harmful factors
If data is physically moved between memory and storage domains, then data transfer is completed, but wear on NVM media increases
Solution Approach 1:
The patent uses domain map entries as virtual copies that track data locations. When data needs to be transferred between domains, the system updates the domain map attributes rather than physically moving data, thereby achieving transfer functionality without the wear that would result from repeated physical write operations to NVM media.
Solution Approach 2:
The patent substitutes the mechanical act of writing data to NVM media with a logical operation of updating domain map attributes in system memory. This replacement eliminates the wear on NVM media that would occur during physical data movement while preserving the data transfer capability through address translation and domain attribute updates.
4Device complexity
If physical data movement is performed between domains, then data transfer is completed, but error correction and encryption/decryption operations are required
Solution Approach 1:
The patent uses the domain map as a virtual copy that tracks data locations and domain attributes. By maintaining this abstraction layer, the system can perform logical transfers without the overhead of error correction and encryption/decryption that would be required during physical data movement, as the data remains stationary and already in its target domain's physical location.
Data Source
AI summary
Devices, systems, and methods for transferring data between the memory domain and the storage domain are described. Transferring data between domains can comprise changing the validity of the block address of the data from one domain to the other, and updating a memory domain map and a storage domain map to reflect the transfer.