Stacked-Die Memory Architecture with Vault Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current semiconductor memory technologies face a mismatch in performance with modern host processors, leading to inefficiencies such as high idle times in servers due to memory request delays, and lack of optimization for memory power and interface uniqueness between processors and memory subsystems, limiting memory bandwidth and density.
Innovation Solution
The implementation of a stacked-die memory architecture with shared control logic and standardized interfaces, utilizing through-wafer interconnects and memory vault controllers to enhance energy efficiency, scalability, and bandwidth, while allowing for reconfiguration to accommodate evolving memory technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If higher bandwidth memory interfaces are implemented, then memory bandwidth is improved, but the number of memory cards or modules that can be connected is limited due to JEDEC electrical specifications
Solution Approach 1:
The memory system is divided into multiple independent memory vaults, each with its own controller and interface. This segmentation allows multiple memory modules to be connected in parallel, each operating within JEDEC specifications, while achieving aggregate bandwidth that exceeds what a single high-bandwidth interface could provide. Each vault operates independently, enabling scalable connection of multiple memory cards or modules.
2Productivity
If memory subsystem interface is made unique between host processor and memory, then specific performance requirements are met, but redesign is needed when processor or memory technologies change
Solution Approach 1:
The memory vault controller implements a universal interface architecture that can accommodate different memory technologies and processor types. The controller is designed to work with various memory standards (DDR, DDR2, DDR3, etc.) and can be configured for different processor architectures. This multi-functionality eliminates the need for complete redesign when technologies evolve, as the same basic vault controller structure can be adapted to new standards through configuration rather than fundamental redesign.
3Quantity of substance
If memory density is increased, then storage capacity is improved, but power optimization is compromised
Solution Approach 1:
The memory system is divided into multiple independent memory vaults, each with its own controller. This segmentation enables selective activation of individual vaults based on workload requirements. When full memory capacity is not needed, only the necessary number of vaults remain active, reducing overall power consumption while maintaining access to high-density memory when required. Each vault can be independently powered on or off, providing fine-grained power optimization.
Solution Approach 2:
The memory vault controller includes integrated power management capabilities that automatically optimize power consumption based on actual memory usage patterns. The controller monitors access patterns and dynamically adjusts power states of memory banks and internal circuits, enabling the high-density memory system to consume only the power necessary for current operations rather than maintaining full power for all memory resources at all times.
Data Source
AI summary
Systems and methods disclosed herein substantially concurrently transfer a plurality of streams of commands, addresses, and/or data across a corresponding plurality of serialized communication link interfaces (SCLIs) between one or more originating devices or destination devices such as a processor and a switch. At the switch, one or more commands, addresses, or data corresponding to each stream can be transferred to a corresponding destination memory vault controller (MVC) associated with a corresponding memory vault. The destination MVC can perform write operations, read operations, and/or memory vault housekeeping operations independently from concurrent operations associated with other MVCs coupled to a corresponding plurality of memory vaults.