WO2013016723A2 - Flash-dram hybrid memory module - Google Patents
Flash-dram hybrid memory module Download PDFInfo
- Publication number
- WO2013016723A2 WO2013016723A2 PCT/US2012/048750 US2012048750W WO2013016723A2 WO 2013016723 A2 WO2013016723 A2 WO 2013016723A2 US 2012048750 W US2012048750 W US 2012048750W WO 2013016723 A2 WO2013016723 A2 WO 2013016723A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- memory
- data
- controller
- volatile
- volatile memory
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0683—Plurality of storage devices
- G06F3/0685—Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
- G06F13/28—Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access DMA, cycle steal
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/16—Constructional details or arrangements
- G06F1/18—Packaging or power distribution
- G06F1/183—Internal mounting support structures, e.g. for printed circuit boards, internal connecting means
- G06F1/185—Mounting of expansion boards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/06—Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication
- G06F12/0638—Combination of memories, e.g. ROM and RAM such as to permit replacement or supplementing of words in one module by words in another module
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
- G06F13/1694—Configuration of memory controller to different memory types
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4004—Coupling between buses
- G06F13/4027—Coupling between buses using bus bridges
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4234—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a memory bus
- G06F13/4243—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a memory bus with synchronous protocol
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
- G06F3/0613—Improving I/O performance in relation to throughput
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C11/00—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor
- G11C11/005—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor comprising combined but independently operative RAM-ROM, RAM-PROM, RAM-EPROM cells
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C14/00—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down
- G11C14/0009—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down in which the volatile element is a DRAM cell
- G11C14/0018—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down in which the volatile element is a DRAM cell whereby the nonvolatile element is an EEPROM element, e.g. a floating gate or metal-nitride-oxide-silicon [MNOS] transistor
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C7/00—Arrangements for writing information into, or reading information out from, a digital store
- G11C7/10—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
- G11C7/1072—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers for memories with random access ports synchronised on clock signal pulse trains, e.g. synchronous memories, self timed memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/20—Employing a main memory using a specific memory technology
- G06F2212/205—Hybrid memory, e.g. using both volatile and non-volatile memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/72—Details relating to flash memory management
- G06F2212/7208—Multiple device management, e.g. distributing data over multiple flash devices
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C11/00—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor
- G11C11/21—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using electric elements
- G11C11/34—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using electric elements using semiconductor devices
- G11C11/40—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using electric elements using semiconductor devices using transistors
- G11C11/401—Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using electric elements using semiconductor devices using transistors forming cells needing refreshing or charge regeneration, i.e. dynamic cells
- G11C11/4063—Auxiliary circuits, e.g. for addressing, decoding, driving, writing, sensing or timing
- G11C11/407—Auxiliary circuits, e.g. for addressing, decoding, driving, writing, sensing or timing for memory cells of the field-effect type
- G11C11/409—Read-write [R-W] circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Definitions
- the present disclosure relates generally to computer memory devices, and more particularly, to devices that employ different types of memory devices such as combinations of Flash and random access memories.
- FIG. 1 The data transfer limitations by the CPU are exemplified by the arrangement shown in FIG. 1, and apply to data transfers between main storage (for example the hard disk (HD) or solid state drive (SSD) and the memory subsystems (for example DRAM DIMM (Dynamic Random Access Memory Dual In-line Memory Module) connected to the front side bus (FSB)).
- main storage for example the hard disk (HD) or solid state drive (SSD)
- DRAM DIMM Dynamic Random Access Memory Dual In-line Memory Module
- FIG. 1 specifically shows, through the double-headed arrow, the data flow path between the computer or server main storage (SSD/HD) to the DRAM DIMMs.
- the CPU Since the SSD/HD data I/O and the DRAM DIMM data I/O are controlled by the CPU, the CPU needs to allocate its process cycles to control these I/Os, which may include the IRQ (Interrupt Request) service which the CPU performs periodically. As will be appreciated, the more time a CPU allocates to controlling the data transfer traffic, the less time the CPU has to perform other tasks. Therefore, the overall performance of a server will deteriorate with the increased amount of time the CPU has to expend in performing data transfer.
- IRQ Interrupt Request
- This arrangement is capable of delivering higher throughput rate than a standard SSD based system since the EcoRAMTM is connected to the CPU (central processing unit) via a high speed interface, such as the HT (Hyper Transport) interface, while an SSD/HD is typically connected via SATA (serial AT attachment), USB (universal serial bus), or PCI Express (peripheral component interface express).
- a high speed interface such as the HT (Hyper Transport) interface
- an SSD/HD is typically connected via SATA (serial AT attachment), USB (universal serial bus), or PCI Express (peripheral component interface express).
- SATA Serial AT attachment
- USB universal serial bus
- PCI Express peripheral component interface express
- the read random access throughput rate of EcoRAMTM is near 3GB/s compared with 400MB/s for a NAND SSD memory subsystem using the standard PCI Express-based. This is a 7.5X performance improvement.
- the performance improvement for write random access throughput rate is less than 2X (197MBs for the EcoRAM vs
- Figure 2 is an example of EcoRAMTM using SSD with the form factor of a standard DIMM such that it can be connected to the FSB (front side bus).
- EcoRAM AcceleratorTM an interface device, EcoRAM AcceleratorTM which occupies one of the server's CPU sockets is used, and hence further reducing server's performance by reducing the number of available CPU sockets available, and in turn reducing the overall computation efficiency.
- the server's performance will further suffer due to the limited utilization of the CPU bus due to the large difference in the data transfer throughput rate between read and write operations.
- the EcoRAMTM architecture enables the CPU to view the Flash DIMM controller chip as another processor with a large size of memory available for CPU access.
- the access speed of a Flash based system is limited by four items: the read/write speed of the Flash memory, the CPU's FSB bus speed and efficiency, the Flash DIMM controller's inherent latency, and the HT interconnect speed and efficiency which is dependent on the HT interface controller in the CPU and Flash DIMM controller chip.
- the method includes receiving control information from the memory controller, wherein the control information is received using a protocol of the volatile memory subsystem.
- the method further includes identifying a data path to be used for transferring data to or from the memory module using the received control information, and using a data manager and a controller of the memory module to transfer data between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on at least one of the received control information and the identified data path.
- Also described herein is a memory module wherein the data manager controls data traffic between any two or more of the memory controller, the volatile memory subsystem, and the non- volatile memory subsystem based on instructions received from the controller.
- data traffic control relates to any one or more of data flow rate, data transfer size, data buffer size, data transfer bit width, formatting information, direction of data flow, and the starting time of data transfer.
- a memory module wherein the controller configures at least one of a first memory address space of the volatile memory subsystem and a second memory address space of the non- volatile memory subsystem in response to at least one of a received command from the memory controller and memory address space initialization information of the memory module.
- the data manager is configured as a bi-directional data transfer fabric having two or more sets of data ports coupled to any one of the volatile and non-volatile memory subsystems.
- non- volatile memory subsystem comprises flash memory
- a memory module wherein at least one set of data ports is operated by the data manager to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or non- volatile memory subsystems.
- the data manager further includes a data format module configured to format data to be transferred between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on control information received from the controller.
- controller is operable to perform one or more of memory address translation, memory address mapping, address domain conversion, memory access control, data error correction, and data width modulation between the volatile and non-volatile memory subsystems.
- controller is configured to effect operation with the host system in accordance with a prescribed protocol.
- controller configures the memory space in the memory module using partitioning instructions that are application-specific.
- controller includes a volatile memory control module, a non-volatile memory control module, data manager control module, a command interpreter module, and a scheduler module.
- Also described herein is a memory module wherein commands from the volatile memory control module to the volatile memory subsystem are subordinated to commands from the memory controller to the controller.
- Also described herein is a memory module wherein the controller effects pre-fetching of data from the non-volatile to the volatile memory.
- Also described herein is a memory module wherein the pre-fetching is initiated by the memory controller writing an address of requested data into a register of the controller.
- a memory module wherein the controller is operable to initiate a copy operation of data of a closed block in the volatile memory subsystem to a target block in the non-volatile memory subsystem.
- the controller is operable to abort the copy operation and to erase the target block from the nonvolatile memory subsystem.
- Also described herein is a method for managing a memory module wherein the transfer of data includes a bidirectional transfer of data between the non-volatile and the volatile memory subsystems.
- Also described herein is a method for managing a memory module further comprising operating the data manager to control data traffic between the memory controller and at least one of the volatile and non- volatile memory subsystems.
- Also described herein is a method for managing a memory module wherein data traffic control relates to any one or more of data transfer size, formatting information, direction of data flow, and the starting time of the transfer of data.
- Also described herein is a method for managing a memory module wherein data traffic control by the data manager is based on instructions received from the controller.
- each memory segment comprises at least one memory circuit, memory device, or memory die.
- Also described herein is a method for managing a memory module wherein the volatile memory subsystem comprises DRAM memory.
- Also described herein is a method for managing a memory module wherein the nonvolatile memory subsystem comprises Flash memory. [0050] Also described herein is a method for managing a memory module further comprising operating the data ports to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or non- volatile memory subsystems.
- Also described herein is a method for managing a memory module further comprising directing transfer of data bi-directionally between the volatile and non-volatile memory subsystems using the data manager and in response to memory access commands received by the controller from the memory controller.
- Also described herein is a method for managing a memory module further comprising buffering the data transferred between the memory controller and non-volatile memory subsystem using the volatile memory subsystem.
- Also described herein is a method for managing a memory module further comprising using the controller to perform one or more of memory address translation, memory address mapping, address domain conversion, memory access control, data error correction, and data width modulation between the volatile and non- volatile memory subsystems.
- Also described herein is a method for managing a memory module further comprising using the controller to effect communication with a host system by the volatile memory subsystem in accordance with a prescribed protocol.
- Also described herein is a method for managing a memory module wherein the prescribed protocol is selected from one or more of DDR, DDR2, DDR3, and DDR4 protocols.
- Also described herein is a method for managing a memory module further comprising using the controller to configure memory space in the memory module based on at least one of a command received from the memory controller, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non-volatile memory subsystem, and a timing value.
- Also described herein is a method for managing a memory module wherein the controller configures the memory space of the memory module using at least a first portion of the volatile memory subsystem and a first portion of the non- volatile memory subsystem, and the controller presents a unified memory space to the memory controller.
- Also described herein is a method for managing a memory module wherein the controller configures the memory space in the memory module using partitioning instructions that are application-specific. [0059] Also described herein is a method for managing a memory module further comprising using the controller to copy booting information from the non- volatile to the volatile memory subsystem during power up.
- Also described herein is a method for managing a memory module wherein the controller includes a volatile memory control module, the method further comprising generating commands by the volatile memory control module in response to commands from the memory controller, and transmitting the generated commands to the volatile memory subsystem.
- Also described herein is a method for managing a memory module further comprising pre-fetching of data from the non-volatile memory subsystem to the volatile memory subsystem.
- Also described herein is a method for managing a memory module wherein the prefetching is initiated by the memory controller writing an address of requested data into a register of the controller.
- Also described herein is a method for managing a memory module further comprising initiating a copy operation of data of a closed block in the volatile memory subsystem to a target block in the non-volatile memory subsystem.
- FIG. 1 is a block diagram illustrating the path of data transfer, via a CPU, of a conventional memory arrangement
- FIG. 2 is a block diagram of a known EcoRAMTM architecture
- FIGS. 4A and 4B are block diagrams of a Flash-DRAM hybrid DIMM or
- FIG. 5A is a block diagram of a memory module 500 in accordance with certain embodiments described herein;
- FIG. 5B is a block diagram showing some functionality of a memory module such as that shown in FIG. 5A;
- FIG. 7 is a functional block diagram of the on-module controller (CDC).
- FIG. 8A is a block diagram showing more details of the prior art Flash-DRAM hybrid DIMM (FDHDIMM) of FIGS. 4 A and 4B;
- FIG. 8B is a block diagram of a Flash-DRAM hybrid DIMM (FDHDIMM) in accordance with certain embodiments disclosed herein;
- FIG. 9 is a flow diagram directed to the transfer of data from Flash memory to DRAM memory and vice versa in an exemplary FDHDIMM;
- FIG. 11 is a table showing estimates of the maximum allowed closed blocks in a queue to be written back to Flash memory for different DRAM densities using various average block use time.
- Example embodiments are described herein in the context of a system of computers, servers, controllers, memory modules, hard disk drives and software. Those of ordinary skill in the art will realize that the following description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the example embodiments as illustrated in the accompanying drawings. The same reference indicators will be used to the extent possible throughout the drawings and the following description to refer to the same or like items.
- the components, process steps, and/or data structures described herein may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines.
- devices of a less general purpose nature such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
- a method comprising a series of process steps is implemented by a computer or a machine and those process steps can be stored as a series of instructions readable by the machine, they may be stored on a tangible medium such as a computer memory device (e.g., ROM (Read Only Memory), PROM (Programmable Read Only Memory), EEPROM (Electrically Eraseable Programmable Read Only Memory), Flash memory, Jump Drive, and the like), magnetic storage medium (e.g., tape, magnetic disk drive, and the like), optical storage medium (e.g., CD-ROM, DVD-ROM, paper card, paper tape and the like) and other types of program memory.
- ROM Read Only Memory
- PROM Programmable Read Only Memory
- EEPROM Electrically Eraseable Programmable Read Only Memory
- Flash memory Jump Drive, and the like
- magnetic storage medium e.g., tape, magnetic disk drive, and the like
- optical storage medium e.g., CD-ROM, DVD-ROM, paper card, paper tape and the like
- FDHDIMM Flash-DRAM-hybrid DIMM
- Methods for controlling such an arrangement are described.
- the actual memory density (size or capacity) of the DIMM and/or the ratio of DRAM memory to Flash memory are configurable for optimal use with a particular application (for example, POS, inter-bank transaction, stock market transaction, scientific computation such as fluid dynamics for automobile and ship design, weather prediction, oil and gas expeditions, medical diagnostics such as diagnostics based on the fuzzy logic, medical data processing, simple information sharing and searching such as web search, retail store website, company home page, email or information distribution and archive, security service, and entertainment such as video-on-demand).
- the device contains a high density Flash memory with a low density DRAM, wherein the DRAM is used as a data buffer for read/write operation.
- the Flash serves as the main memory.
- a memory system 300 includes a non- volatile (for example Flash) memory subsystem 302 and a volatile (for example DRAM) memory subsystem 304.
- the examples of FIGS. 3A and 3B are directed to architectures of a non- volatile DIMM (NVDIMM) NVDIMM system that may use a power subsystem (not shown) that can include a battery or a capacitor as a means for energy storage to copy DRAM memory data into Flash memory when power loss occurs, is detected, or is anticipated to occur during operation.
- NVDIMM non- volatile DIMM
- the NVDIMM controller 306' of NVDIMM 300' monitors events or commands and enables data transfer to occur in a first mode between the DRAM 304' and Flash 302' or in a second mode between the DRAM and the MCH.
- the FDHDIMM controller the FDHDIMM overall performance is governed by the Flash access time.
- the volatile memory subsystem (for example DRAM) 406 is primarily used as a data buffer or a temporary storage location such that data from the Flash memory 402 is transferred to the DRAM 406 at the Flash access speed, and buffered or collected into the DRAM 406, which then transfers the buffered data to the MCH based on the access time of DRAM.
- the FDHDIMM controller 404 manages the data transfer from the DRAM 406 to the Flash 402. Since the Flash memory access speed (both read and write) is relatively slower than DRAM, (e.g.
- the average data throughput rate of FDHDIMM 400 is limited by the Flash access speed.
- the DRAM 406 serves as a data buffer stage that buffers the MCH read or write data.
- the DRAM 406 serves as a temporary storage for the data to be transferred from/to the Flash 402.
- the MCH recognizes the physical density of an FDHDIMM operating as a high density DIMM as the density of Flash alone.
- a read operation can be performed by the MCH by sending an activate command (may be simply referred to as RAS, or row address strobe) to the FDHDIMM 400 to conduct a pre-fetch read data operation from the Flash 402 to the DRAM 406, with the pre-fetch data size being for example a page (1KB or 2KB, or may be
- RAS row address strobe
- the MCH then sends a read command (may be simply referred to as CAS, or column address strobe) to read the data out input of the DRAM.
- a read command may be simply referred to as CAS, or column address strobe
- the data transfer from Flash to DRAM occurs at Flash access speed rates
- data transfer from DRAM to MCH occurs at DRAM access speed rates.
- data latency and throughput rates are the same as any DRAM operation as long as the read operations are executed onto the pages that were opened with the activate command previously sent to pre-fetch data from the Flash to DRAM.
- a longer separation time period between the RAS e.g. Activate command
- the first CAS column address strobe
- FIG. 4B An example of FDHDIMM operating as a DDR DIMM with SSD is shown in FIG. 4B, wherein the FDHDIMM 400'supports two different interface interpretations to the MCH.
- the MCH views the FDHDIMM 400' as a combination of DRAM DIMM and SSD (not illustrated).
- the MCH needs to manage two address spaces, one for the DRAMs 402' and one for the Flash 404'.
- the MCH is coupled to, and controls, both of the DRAM and Flash memory subsystems.
- the CPU does not need to be in the data path when data is moved from DRAM to Flash or from Flash to DRAM.
- the MCH views the FDHDIMM 400' as an on-DIMM Flash with the SSD in an extended memory space that is behind the DRAM space.
- the MCH physically fetches data from the SSD to the DDR DRAM and then the DRAM sends the data to the MCH. Since all data movement occurs on the FDHDIMM, this mode will provide better performance than if the data were to be moved through or via the CPU.
- the FDHDIMM 400' receives control signals 408 from the MCH, where the control signals may include one or more control signals specifically for the DRAM 402' operation and one or more control signals specifically for the Flash 404' operation.
- the MCH or CPU is coupled to the FDHDIMM via a single data bus interface 410 which couples the MCH to the DRAM.
- FIGS. 5A and 5B are block diagrams of a memory module 500 that is couplable to a host system (not shown).
- the host system may be a server or any other system comprising a memory system controller or an MCH for providing and controlling the read/write access to one or more memory systems, wherein each memory system may include a plurality of memory subsystems, a plurality of memory devices, or at least one memory module.
- read/write access means the ability of the MCH to interface with a memory system or subsystem in order to write data into it or read data from it, depending on the particular requirement at a particular time.
- memory module 500 is a Flash-DRAM hybrid memory subsystem which may be integrated with other components of a host system.
- memory module 500 is a Flash-DRAM hybrid memory module that has the DIMM (dual-inline memory module) form factor, and may be referred to as a FDHDIMM, although it is to be understood that in both structure and operation it may be different from the FDHDIMM discussed above and described with reference to FIGS. 4 A and 4B.
- Memory module 500 includes two on-module intermediary components: a controller and a data manager.
- on-module intermediary components may be physically separate components, circuits, or modules, or they may be integrated onto a single integrated circuit or device, or integrated with other memory devices, for example in a three dimensional stack, or in any one of several other possible expedients for integration known to those skilled in the art to achieve a specific design, application, or economic goal.
- these on-module intermediary components are an on-DIMM Controller (CDC) 502 and an on-DIMM data manager (DMgr) 504. While the DIMM form factor will predominate the discussion herein, it should be understood that this is for illustrative purposes only and memory systems using other form factors are contemplated as well.
- CDC 502 and data manager DMgr 504 are operative to manage the interface between a non-volatile memory subsystem such as a Flash 506, a volatile memory subsystem such as a DRAM 508, and a host system represented by MCH 510.
- CDC 502 controls the read/write access to/from Flash memory 506 from/to DRAM memory 508, and to/from DRAM memory from/to MCH 510.
- Read/write access between DRAM 508, Flash 506 and MCH 510 may be referred to herein generally as communication, wherein control and address information C/A 560 is sent from MCH 510 to CDC 502, and possible data transfers follow as indicated by Data 550, Data 555, and/or Data 556.
- the CDC 502 performs specific functions for memory address transformation, such as address translation, mapping, or address domain conversion, Flash access control, data error correction, manipulation of data width or data formatting or data modulation between the Flash memory and DRAM, and so on.
- the CDC 502 ensures that memory module 500 provides transparent operation to the MCH in accordance with certain industry standards, such as DDR, DDR2, DDR3, DDR4 protocols.
- certain industry standards such as DDR, DDR2, DDR3, DDR4 protocols.
- the Flash access speed has minimal impact on the overall FDHDIMM access speed.
- the CDC controller 502 receives standard DDR commands from the MCH, interprets, and produces commands and/or control signals to control the operation of the Data manager (DMgr), the Flash memory and the DRAM memory.
- the DMgr controls the data path routing amongst DRAMs, Flash and MCH, as detailed below.
- the data path routing control signals are independently operated without any exclusivity.
- An exemplary role of DMgr 504 is described with reference to FIG. 6.
- DMgr 504 provides a variety of functions to control data flow rate, data transfer size, data buffer size, data error monitoring or data error correction. For example, these functions or operations can be performed on-the-fly (while data is being transferred via the DMgr 504) or performed on buffered or stored data in DRAM or a buffer.
- one role of DMgr 504 is to provide interoperability among various memory subsystems or components and/or MCH 510.
- an exemplary host system operation begins with initialization.
- the CDC 502 receives a first command from the MCH 510 to initialize FDHDIMM 500 using a certain memory space.
- the memory space as would be controlled by MCH 510 can be configured or programmed during initialization or after initialization has completed.
- the MCH 510 can partition or parse the memory space in various ways that are optimized for a particular application that the host system needs to run or execute.
- the CDC 502 maps the actual physical Flash 506 and DRAM 508 memory space using the information sent by MCH 510 via the first command.
- MCH 510 may send a command to restore a certain amount of data information from Flash 506 to DRAM 508.
- the CDC 502 provides control information to DMgr 504 to appropriately copy the necessary information from Flash 506 to the DRAM 508. This operation can provide support for various host system booting operations and/or a special host system power up operation.
- DMgr 504 also functions as a bi-directional data transfer fabric.
- DMgr 504 may have more than 2 sets of data ports facing the Flash 506 and the DRAM 508.
- Multiplexers 611 and 612 provide controllable data paths from any one of the DRAMs 508(1) and 508(2) (DRAM-A and DRAM-B) to any one of the MCH 510 and the Flash 506.
- multiplexers 621 and 622 provide controllable data paths from any one of the MCH and the Flash memory to any one of the DRAMs 508(1) and 508(2) (DRAM-A and DRAM-B).
- DRAM 508(1) is a segment of DRAM 508, while in other embodiments, DRAM 508(1) is a separate DRAM memory subsystem. It will be understood that each memory segment can comprise one or more memory circuits, a memory devices, and/or memory integrated circuits. Of course other configurations for DRAM 508 are possible, and other data transfer fabrics using complex data paths and suitable types of multiplexing logic are contemplated.
- the two sets of multiplexors 611, 612 and 621, 622 allow independent data transfer to Flash 506 from DRAM-A 508(1) and DRAM-B 508(2).
- DMgr 504 can transfer data from DRAM-A 508(1) to MCH 510, via multiplexer 611, at the same time as from DRAM-B 508(2) to the Flash 506, via multiplexer 612; or data is transferred from DRAM-B 508(2) to MCH 510, via multiplexer 611, and simultaneously data is transferred from the Flash 506 to DRAM-A 508(1), via multiplexer 621.
- the illustrated arrangement of data transfer fabric of DMgr 504 also allows the CDC 502 to control data transfer from the Flash memory to the MCH by buffering the data from the Flash 506 using a buffer 602, and matching the data rate and/or data format of MCH 510.
- the buffer 602 is shown in FIG. 6 as a portion of a data format module 604; however, buffer 602 may also be a distributed buffer such that one buffer is used for each one of the set of multiplexer logic elements shown as multiplexers 611, 612, 621, and 622.
- data format module 604 contains a data formatting subsystem (not shown) to enable DMgr 504 to format and perform data transfer in accordance with control information received from CDC502.
- Data buffer 604 of data format module 602, discussed above, also supports a wide data bus 606 coupled to the Flash memory 506 operating at a first frequency, while receiving data from DRAM 508 using a relatively smaller width data bus 608 operating at a second frequency, the second frequency being larger than the first frequency in certain embodiments.
- the buffer 602 is designed to match the data flow rate between the DRAM 508 and the Flash 506.
- a register 690 provides the ability to register commands received from MCH 510 via C/A 560 (FIG. 5A).
- the register 690 may communicate these commands to CDC 502 and/or to the DRAM 508 and/or Flash 506.
- the register 690 communicates these registered commands to CDC 502 for processing.
- the register 690 may also include multiple registers (not shown), such that it can provide the ability to register multiple commands, a sequence of commands, or provide a pipeline delay stage for buffering and providing a controlled execution of certain commands received form MCH 510.
- the register 690 may register commands from MCH 510 and transmit the registered commands to DRAM 508 and/or Flash 506 memory subsystems.
- the CDC 502 monitors commands received from MCH 510, via control and address bus C/A 560, and provides appropriate control information to DMgr 504, DRAM 508, or Flash 506 to execute these commands and perform data transfer operations between MCH 510 and FDHDIMM 500 via MCH data bus 610.
- the major functional blocks of the CDC 502 are a DRAM control block
- the Scheduler 708 assigns time slots for the DRAMCtrl 702 and FlashCtrl 704 operation based on the current status and the pending command received or to be received from the MCH.
- the DMgrCtrl 710 generates and sends appropriate control information and control signals for the proper operation and control of the data transfer fabric to enable or disable data paths between Flash 506, DRAM 508, and the MCH 510.
- this data transfer mechanism provides direct support for executing commands from the MCH without having the MCH directly controlling the data transfer, and thus improving data transfer performance from Flash 803 to the DRAM 805.
- the MCH needs to manage two address spaces and two different memory protocols simultaneously.
- the MCH needs to map the DRAM memory space into the Flash memory space, and the data interface time suffers due to the difference in the data access time between the Flash memory and the DRAM memory.
- a memory space mapping of a Flash-DRAM hybrid DIMM is shown in FIG. 8B.
- a memory controller of a host system (not shown) controls both of the DRAM 508 address space and the Flash 506 address space using a single unified address space.
- the CDC 502 receives memory access commands from the MCH and generates control information for appropriate mapping and data transfer between Flash and DRAM memory subsystem to properly carry out the memory access commands.
- the memory controller of the host system views the large Flash memory space as a DRAM memory space, and accesses this unified memory space with a standard DDR (double data rate) protocol used for accessing DRAM.
- DDR double data rate
- the unified memory space in this case can exhibit overlapping memory address space between the Flash 506 and the DRAM 508.
- the overlapping memory address space may be used as a temporary storage or buffer for data transfer between the Flash 506 and the DRAM 508.
- the DRAM memory space may hold a copy of data from the selected Flash memory space such that the MCH can access this data normally via DDR memory access commands.
- the CDC 502 controls the operation of the Flash 506 and DRAM 508 memory subsystems in response to commands received from a memory controller of a host system.
- the unified memory space corresponds to a contiguous address space comprising a first portion of the address space of the Flash 506 and a first portion of the address space of the DRAM 508.
- the first portion of the address space of the Flash 506 can be determined via a first programmable register holding a first value corresponding to the desired Flash memory size to be used.
- the first portion of the address space of the DRAM 508 can be determined via a second programmable register holding a second value corresponding to the desired DRAM memory size to be used.
- the controller can configure memory space in the memory module based on at least one of one or more commands received from the MCH, instructions received from the MCH, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non-volatile memory subsystem, and a timing value.
- the block size can be configurable by the memory controller of the host system, such that the number pages in a block can be optimized to support a particular application or a task.
- the block size may be configured on-the-fly, e.g. CDC 502 can receive instruction regarding a desired block size from the memory controller via a memory command, or via a programmable value.
- the CDC 502 alerts the memory controller to retrieve the data information from the DRAM 508.
- the memory controller initiates the copying of data information from Flash 506 to DRAM 508 by writing, into a register in the CDC 502, the target Flash address along with a valid block size.
- the CDC 502 executes appropriate operations and generates control information to copy the data information to the DRAM 508. Consequently, the memory controller can access or retrieve the data information using standard memory access commands or protocol.
- FIG. 9 An exemplary flow chart is shown in FIG. 9, a starting step or power up 902, is followed by an initialization step 904, the memory controller initiates, at step 906, a data move from the Flash 506 to the DRAM 508 by writing target address and size, to a control register in the CDC 502, which then copies, at 908, data information from the Flash 506 to the DRAM 508 and erases the block in the Flash. Erasing the data information from Flash may be accomplished independently from (or concurrently with) other steps that CDC 502 performs in this flow chart, i.e. other steps can be executed concurrently with the Erase the Flash block step.
- the memory controller can operate on this data block using standard memory access protocol or commands at 910.
- the CDC 502 checks, at 912, if any of the DRAM 508 blocks, or copied blocks, are closed. If the memory controller closed any open blocks in DRAM 508, then the CDC 502 initiate a Flash write to write the closed block from the DRAM 508 to the Flash 506, at 914. In addition, the memory controller, at 916, reopens the closed block that is currently being written into the Flash 506, then the CDC 502 stops the Flash write operation and erases the Flash block which was being written to, as shown at 918. Otherwise, the CDC 502 continues and completes the writing operation to the Flash at 920.
- the dashed lines in FIG. 9 indicate independent or parallel activities that can be performed by the CDC 502.
- the CDC 502 receives a DRAM load command from a memory controller which writes a Flash target address and/or block size information into the RC register(s) at 922, as described above, then the CDC 502 executes a load DRAM w/RC step 906 and initiates another branch (or a thread) of activities that includes steps 908 - 922.
- the CDC 502 controls the data transfer operations between DRAM 508 and Flash 506 such that the Flash 506 is completely hidden from the memory controller.
- the CDC 502 monitors all memory access commands sent by the memory controller using standard DRAM protocol and appropriately configures and manipulate both Flash 506 and DRAM 508 memory subsystems to perform the requested memory access operation and thus achieve the desired results.
- the memory controller does not interface directly with the Flash memory subsystem. Instead, the memory controller interfaces with the CDC 502 and/or DMgr 504 as shown in Fig. 5 and Fig. 6. Moreover, the memory controller may use one or more protocol, such as DDR, DDR2, DDR3, DDR4 protocols or the like.
- FIG. 10 an example of mapping a DRAM address space to Flash memory address space is shown in FIG. 10.
- Two sets (1002, 1004) of address bits AD6 to AD 17, forming a 24 bit extended memory page address, are allocated for the block address. For example, assuming a Block size of 256K Bytes, then a 24-bit block address space (using the two sets of AD6 to AD 17 1002 and 1004) would enable access to 4TB of Flash memory storage space. If a memory module has 1GB of DRAM storage capacity, then it can hold approximately 4K Blocks of data in the DRAM memory, each Block comprise 256 K Bytes of data.
- the DRAM address space corresponding to the 4K blocks, can be assigned to different virtual ranks and banks, where the number of virtual ranks and banks is configurable and can be manipulated to meet a specific design or performance needs. For example, if a 1G Bytes memory module is configured to comprise two ranks with eight banks per rank, then each bank would hold two hundred fifty (250) blocks or the equivalent of 62 M Bytes or 62K pages, where each page correspond to a IK Bytes. Other configurations using different page, block, banks, or ranks numbers may also be used. Furthermore, an exemplary mapping of 24-bit DDR DIMM block address to Flash memory address, using Block addressing as described above, is shown in Fig. 10.
- the 24-bit can be decomposed into fields, such as a logical unit number LUN address 1060 field, a Block address 1050 field, a Plane address 1040, a Page address 1030, and a group of least significant address bits A 0 Ai 1020.
- the Plane address 1040 is a sub address of the block address, and it may be used to support multiple page IO so as to improve Flash memory subsystem operation. In this example, it is understood that different number of bits may be allocated to each field of the 24-bit
- the CDC 502 manages the block write-back operation by queuing the blocks that are ready to be written back to the Flash memory. As described above, if any page in a queued block for a write operation is reopened, then the CDC 502 will stop the queued block write operation, and remove the block from the queue. Once all the pages in a block are closed, then the CDC 502 restarts the write-back operation and queue the block for a write operation.
- an exemplary read operation from Flash 506 to DRAM 508 can be performed in approximately 400 ⁇ 8, while a write operation from DRAM 508 to Flash 506 can be performed in approximately 22ms resulting in a read to write ratio of 55 to 1.
- the block write-back operation from DRAM to Flash would not impact performance and hence the disparity between read and write access may be completely hidden from the memory controller.
- the block usage time is 1 1ms instead of 22ms, then the CDC 502 control the data transfer operation between DRAM 508 and Flash 506 such that there are no more than 9 closed blocks in the queue to be written-back to the Flash memory, hence approximately an average of 100ms can be maintained for a standard DDR DRAM operation.
- the number of closed Blocks in the queue to be written-back to the Flash memory subsystem varies with the average block usage time and the desired performance for a specific host system or for a specific application running using the host system resources.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computer Hardware Design (AREA)
- Power Engineering (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Memory System (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
A memory module that is couplable to a memory controller hub (MCH) of a host system includes a non- volatile memory subsystem, a data manager coupled to the non- volatile memory subsystem, a volatile memory subsystem coupled to the data manager and operable to exchange data with the non- volatile memory subsystem by way of the data manager, and a controller operable to receive read/write commands from the MCH and to direct transfer of data between any two or more of the MCH, the volatile memory subsystem, and the non- volatile memory subsystem based on the commands.
Description
Flash-DRAM Hybrid Memory Module
PRIORITY CLAIM
[0001] This application claims the benefit of U.S. provisional patent application serial no.
61/512,871, filed July 28, 2011, and of U.S. patent application serial 13/559,476, filed July 26, 2012, which is a continuation-in-part (CIP) of U.S. patent application serial no. 12/240,916, filed September 29, 2008, which is a continuation of U.S. patent application serial no. 12/131,873, filed June 2, 2008, which claims the benefit of U.S. provisional patent application serial no. 60/941,586, filed June 1, 2007, the contents of all of which are incorporated herein by reference in their entirety.
[0002] This application may also be considered to be related to co-pending U.S. patent application serial no. 13/536,173, filed on June 28, 2012, and commonly owned herewith.
TECHNICAL FIELD
[0003] The present disclosure relates generally to computer memory devices, and more particularly, to devices that employ different types of memory devices such as combinations of Flash and random access memories.
BACKGROUND
[0004] As technology advances and the usage of portable computing devices, such as tablet notebook computers, increases, more data needs to be transferred among data centers and to/from end users. In many cases, data centers are built by clustering multiple servers that are networked to increase performance.
[0005] Although there are many types of networked servers that are specific to the types applications envisioned, the basic concept is generally to increase server performance by dynamically allocating computing and storage resources. In recent years, server technology has evolved to be specific to particular applications such as 'finance transactions' (for example, point-of-service, inter-bank transaction, stock market transaction), 'scientific computation' (for example, fluid dynamic for automobile and ship design, weather prediction, oil and gas expeditions), 'medical diagnostics' (for example, diagnostics based on the fuzzy logic, medical data processing), 'simple information sharing and searching' (for example, web search, retail
store website, company home page), 'email' (information distribution and archive), 'security service', 'entertainment' (for example, video-on-demand), and so on. However, all of these applications suffer from the same information transfer bottleneck due to the inability of a high speed CPU (central processing unit) to efficiently transfer data in and out of relatively slower speed storage or memory subsystems, particularly since data transfers typically pass through the CPU input/output (I/O) channels.
[0006] The data transfer limitations by the CPU are exemplified by the arrangement shown in FIG. 1, and apply to data transfers between main storage (for example the hard disk (HD) or solid state drive (SSD) and the memory subsystems (for example DRAM DIMM (Dynamic Random Access Memory Dual In-line Memory Module) connected to the front side bus (FSB)). In arrangements such as that of FIG. 1, the SSD/HD and DRAM DIMM of a conventional memory arrangement are connected to the CPU via separate memory control ports (not shown). FIG. 1 specifically shows, through the double-headed arrow, the data flow path between the computer or server main storage (SSD/HD) to the DRAM DIMMs. Since the SSD/HD data I/O and the DRAM DIMM data I/O are controlled by the CPU, the CPU needs to allocate its process cycles to control these I/Os, which may include the IRQ (Interrupt Request) service which the CPU performs periodically. As will be appreciated, the more time a CPU allocates to controlling the data transfer traffic, the less time the CPU has to perform other tasks. Therefore, the overall performance of a server will deteriorate with the increased amount of time the CPU has to expend in performing data transfer.
[0007] There have been various approaches to increase the data transfer throughput rates from/to the main storage, such as SSD/HD, to local storage, such as DRAM DIMM. In one example as illustrated in FIG. 2, EcoRAM™ developed by Spansion provides a storage SSD based system that assumes a physical form factor of a DIMM . The EcoRAM™ is populated with Flash memories and a relatively small memory capacity using DRAMs which serve as a data buffer. This arrangement is capable of delivering higher throughput rate than a standard SSD based system since the EcoRAM™ is connected to the CPU (central processing unit) via a high speed interface, such as the HT (Hyper Transport) interface, while an SSD/HD is typically connected via SATA (serial AT attachment), USB (universal serial bus), or PCI Express (peripheral component interface express). For example, the read random access throughput rate of EcoRAM™ is near 3GB/s compared with 400MB/s for a NAND SSD memory subsystem
using the standard PCI Express-based. This is a 7.5X performance improvement. However, the performance improvement for write random access throughput rate is less than 2X (197MBs for the EcoRAM vs. 104MBs for NAND SSD). This is mainly due to the fact that the write speed is cannot be faster than the NAND Flash write access time. Figure 2 is an example of EcoRAM™ using SSD with the form factor of a standard DIMM such that it can be connected to the FSB (front side bus). However, due to the interface protocol difference between DRAM and Flash, an interface device, EcoRAM Accelerator™), which occupies one of the server's CPU sockets is used, and hence further reducing server's performance by reducing the number of available CPU sockets available, and in turn reducing the overall computation efficiency. The server's performance will further suffer due to the limited utilization of the CPU bus due to the large difference in the data transfer throughput rate between read and write operations.
[0008] The EcoRAM™ architecture enables the CPU to view the Flash DIMM controller chip as another processor with a large size of memory available for CPU access.
[0009] In general, the access speed of a Flash based system is limited by four items: the read/write speed of the Flash memory, the CPU's FSB bus speed and efficiency, the Flash DIMM controller's inherent latency, and the HT interconnect speed and efficiency which is dependent on the HT interface controller in the CPU and Flash DIMM controller chip.
[0010] The published results indicate that these shortcomings are evident in that the maximum throughput rate is 1.56 GBs for the read operation and 104 MBs for the write operation. These access rates are 25% of the DRAM read access speed, and 1.7% of the DRAM access speed at 400MHz operation. The disparity in the access speed (15 to 1) between the read operation and write operation highlight a major disadvantage of this architecture. The discrepancy of the access speed between this type of architecture and JEDEC standard DRAM DIMM is expected to grow wider as the DRAM memory technology advances much faster than the Flash memory.
OVERVIEW
[0011] Described herein is a memory module couplable to a memory controller of a host system. The memory module includes a non- volatile memory subsystem, a data manager coupled to the non- volatile memory subsystem, a volatile memory subsystem coupled to the data manager and operable to exchange data with the non- volatile memory subsystem by way of the
data manager, and a controller operable to receive commands from the memory controller and to direct (i) operation of the non-volatile memory subsystem, (ii) operation of the volatile memory subsystem, and (iii) transfer of data between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on at least one received command from the memory controller.
[0012] Also described herein is a method for managing a memory module by a memory controller, the memory module including volatile and non- volatile memory subsystems. The method includes receiving control information from the memory controller, wherein the control information is received using a protocol of the volatile memory subsystem. The method further includes identifying a data path to be used for transferring data to or from the memory module using the received control information, and using a data manager and a controller of the memory module to transfer data between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on at least one of the received control information and the identified data path.
[0013] Also described herein is a memory module wherein the data manager is operable to control one or more of data flow rate, data transfer size, data buffer size, data error monitoring, and data error correction in response to receiving at least one of a control signal and control information from the controller.
[0014] Also described herein is a memory module wherein the data manager controls data traffic between any two or more of the memory controller, the volatile memory subsystem, and the non- volatile memory subsystem based on instructions received from the controller.
[0015] Also described herein is a memory module wherein data traffic control relates to any one or more of data flow rate, data transfer size, data buffer size, data transfer bit width, formatting information, direction of data flow, and the starting time of data transfer.
[0016] Also described herein is a memory module wherein the controller configures at least one of a first memory address space of the volatile memory subsystem and a second memory address space of the non- volatile memory subsystem in response to at least one of a received command from the memory controller and memory address space initialization information of the memory module.
[0017] Also described herein is a memory module wherein the data manager is configured as a bi-directional data transfer fabric having two or more sets of data ports coupled to any one of the volatile and non-volatile memory subsystems.
[0018] Also described herein is a memory module wherein at least one of the volatile and non- volatile memory subsystems comprises one or more memory segments.
[0019] Also described herein is a memory module wherein each memory segment comprises at least one memory circuit, memory device, or memory die.
[0020] Also described herein is a memory module wherein the volatile memory subsystem comprises DRAM memory.
[0021] Also described herein is a memory module wherein the non- volatile memory subsystem comprises flash memory.
[0022] Also described herein is a memory module wherein at least one set of data ports is operated by the data manager to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or non- volatile memory subsystems.
[0023] Also described herein is a memory module wherein the data manager and controller are configured to effect data transfer between the memory controller and the non-volatile memory subsystem in response to memory access commands received by the controller from the memory controller.
[0024] Also described herein is a memory module wherein the volatile memory subsystem is operable as a buffer for the data transfer between the memory controller and non- volatile memory.
[0025] Also described herein is a memory module wherein the data manager further includes a data format module configured to format data to be transferred between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on control information received from the controller.
[0026] Also described herein is a memory module wherein the data manager further includes a data buffer for buffering data delivered to or from the non- volatile memory subsystem.
[0027] Also described herein is a memory module wherein the controller is operable to perform one or more of memory address translation, memory address mapping, address domain conversion, memory access control, data error correction, and data width modulation between the volatile and non-volatile memory subsystems.
[0028] Also described herein is a memory module wherein the controller is configured to effect operation with the host system in accordance with a prescribed protocol.
[0029] Also described herein is a memory module wherein the prescribed protocol is selected from one or more of DDR, DDR2, DDR3, and DDR4 protocols.
[0030] Also described herein is a memory module wherein the controller is operable to configure memory space in the memory module based on at least one of a command received from the memory controller, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non-volatile memory subsystem, and a timing value.
[0031] Also described herein is a memory module wherein the controller configures the memory space of the memory module using at least a first portion of the volatile memory subsystem and a first portion of the non-volatile memory subsystem, and the controller presents a unified memory space to the memory controller.
[0032] Also described herein is a memory module wherein the controller configures the memory space in the memory module using partitioning instructions that are application-specific.
[0033] Also described herein is a memory module wherein the controller is operable to copy booting information from the non- volatile to the volatile memory subsystem during power up.
[0034] Also described herein is a memory module wherein the controller includes a volatile memory control module, a non-volatile memory control module, data manager control module, a command interpreter module, and a scheduler module.
[0035] Also described herein is a memory module wherein commands from the volatile memory control module to the volatile memory subsystem are subordinated to commands from the memory controller to the controller.
[0036] Also described herein is a memory module wherein the controller effects pre-fetching of data from the non-volatile to the volatile memory.
[0037] Also described herein is a memory module wherein the pre-fetching is initiated by the memory controller writing an address of requested data into a register of the controller.
[0038] Also described herein is a memory module wherein the controller is operable to initiate a copy operation of data of a closed block in the volatile memory subsystem to a target block in the non-volatile memory subsystem.
[0039] Also described herein is a memory module wherein, if the closed block is re-opened, the controller is operable to abort the copy operation and to erase the target block from the nonvolatile memory subsystem.
[0040] Also described herein is a method for managing a memory module wherein the transfer of data includes a bidirectional transfer of data between the non-volatile and the volatile memory subsystems.
[0041] Also described herein is a method for managing a memory module further comprising operating the data manager to control one or more of data flow rate, data transfer size, data width size, data buffer size, data error monitoring, data error correction, and the starting time of the transfer of data.
[0042] Also described herein is a method for managing a memory module further comprising operating the data manager to control data traffic between the memory controller and at least one of the volatile and non- volatile memory subsystems.
[0043] Also described herein is a method for managing a memory module wherein data traffic control relates to any one or more of data transfer size, formatting information, direction of data flow, and the starting time of the transfer of data.
[0044] Also described herein is a method for managing a memory module wherein data traffic control by the data manager is based on instructions received from the controller.
[0045] Also described herein is a method for managing a memory module further comprising operating the data manager as a bi-directional data transfer fabric with two or more sets of data ports coupled to any one of the volatile and non- volatile memory subsystems.
[0046] Also described herein is a method for managing a memory module wherein at least one of the volatile and non- volatile memory subsystems comprises one or more memory segments.
[0047] Also described herein is a method for managing a memory module wherein each memory segment comprises at least one memory circuit, memory device, or memory die.
[0048] Also described herein is a method for managing a memory module wherein the volatile memory subsystem comprises DRAM memory.
[0049] Also described herein is a method for managing a memory module wherein the nonvolatile memory subsystem comprises Flash memory.
[0050] Also described herein is a method for managing a memory module further comprising operating the data ports to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or non- volatile memory subsystems.
[0051] Also described herein is a method for managing a memory module further comprising directing transfer of data bi-directionally between the volatile and non-volatile memory subsystems using the data manager and in response to memory access commands received by the controller from the memory controller.
[0052] Also described herein is a method for managing a memory module further comprising buffering the data transferred between the memory controller and non-volatile memory subsystem using the volatile memory subsystem.
[0053] Also described herein is a method for managing a memory module further comprising using the controller to perform one or more of memory address translation, memory address mapping, address domain conversion, memory access control, data error correction, and data width modulation between the volatile and non- volatile memory subsystems.
[0054] Also described herein is a method for managing a memory module further comprising using the controller to effect communication with a host system by the volatile memory subsystem in accordance with a prescribed protocol.
[0055] Also described herein is a method for managing a memory module wherein the prescribed protocol is selected from one or more of DDR, DDR2, DDR3, and DDR4 protocols.
[0056] Also described herein is a method for managing a memory module further comprising using the controller to configure memory space in the memory module based on at least one of a command received from the memory controller, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non-volatile memory subsystem, and a timing value.
[0057] Also described herein is a method for managing a memory module wherein the controller configures the memory space of the memory module using at least a first portion of the volatile memory subsystem and a first portion of the non- volatile memory subsystem, and the controller presents a unified memory space to the memory controller.
[0058] Also described herein is a method for managing a memory module wherein the controller configures the memory space in the memory module using partitioning instructions that are application-specific.
[0059] Also described herein is a method for managing a memory module further comprising using the controller to copy booting information from the non- volatile to the volatile memory subsystem during power up.
[0060] Also described herein is a method for managing a memory module wherein the controller includes a volatile memory control module, the method further comprising generating commands by the volatile memory control module in response to commands from the memory controller, and transmitting the generated commands to the volatile memory subsystem.
[0061] Also described herein is a method for managing a memory module further comprising pre-fetching of data from the non-volatile memory subsystem to the volatile memory subsystem.
[0062] Also described herein is a method for managing a memory module wherein the prefetching is initiated by the memory controller writing an address of requested data into a register of the controller.
[0063] Also described herein is a method for managing a memory module further comprising initiating a copy operation of data of a closed block in the volatile memory subsystem to a target block in the non-volatile memory subsystem.
[0064] Also described herein is a method for managing a memory module further comprising aborting the copy operation when the closed block of the volatile memory subsystem is reopened, and erasing the target block in the non-volatile memory subsystem.
BRIEF DESCRIPTION OF THE DRAWINGS
[0065] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more examples of embodiments and, together with the description of example embodiments, serve to explain the principles and implementations of the embodiments.
[0066] In the drawings:
FIG. 1 is a block diagram illustrating the path of data transfer, via a CPU, of a conventional memory arrangement;
FIG. 2 is a block diagram of a known EcoRAM™ architecture;
FIGS. 3 A and 3B are block diagrams of a non- volatile memory DIMM or
NVDIMM;
FIGS. 4A and 4B are block diagrams of a Flash-DRAM hybrid DIMM or
FDHDIMM;
FIG. 5A is a block diagram of a memory module 500 in accordance with certain embodiments described herein;
FIG. 5B is a block diagram showing some functionality of a memory module such as that shown in FIG. 5A;
FIG. 6 is a block diagram showing some details of the data manager (DMgr);
FIG. 7 is a functional block diagram of the on-module controller (CDC);
FIG. 8A is a block diagram showing more details of the prior art Flash-DRAM hybrid DIMM (FDHDIMM) of FIGS. 4 A and 4B;
FIG. 8B is a block diagram of a Flash-DRAM hybrid DIMM (FDHDIMM) in accordance with certain embodiments disclosed herein;
FIG. 9 is a flow diagram directed to the transfer of data from Flash memory to DRAM memory and vice versa in an exemplary FDHDIMM;
FIG. 10 is a block diagram showing an example of mapping of DRAM address space to Flash memory address space; and
FIG. 11 is a table showing estimates of the maximum allowed closed blocks in a queue to be written back to Flash memory for different DRAM densities using various average block use time.
DESCRIPTION OF EXAMPLE EMBODIMENTS
[0067] Example embodiments are described herein in the context of a system of computers, servers, controllers, memory modules, hard disk drives and software. Those of ordinary skill in the art will realize that the following description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the example embodiments as illustrated in the accompanying drawings. The same reference indicators will be used to the extent possible throughout the drawings and the following description to refer to the same or like items.
[0068] In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the
development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
[0069] In accordance with this disclosure, the components, process steps, and/or data structures described herein may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein. Where a method comprising a series of process steps is implemented by a computer or a machine and those process steps can be stored as a series of instructions readable by the machine, they may be stored on a tangible medium such as a computer memory device (e.g., ROM (Read Only Memory), PROM (Programmable Read Only Memory), EEPROM (Electrically Eraseable Programmable Read Only Memory), Flash memory, Jump Drive, and the like), magnetic storage medium (e.g., tape, magnetic disk drive, and the like), optical storage medium (e.g., CD-ROM, DVD-ROM, paper card, paper tape and the like) and other types of program memory.
[0070] The term "exemplary" where used herein is intended to mean "serving as an example, instance or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
[0071] Disclosed herein are arrangements for improving memory access rates and addressing the high disparity (15 to 1 ratio) between the read and write data throughput rates. In one arrangement, a Flash-DRAM-hybrid DIMM (FDHDIMM) with integrated Flash and DRAM is used. Methods for controlling such an arrangement are described.
[0072] In certain embodiments, the actual memory density (size or capacity) of the DIMM and/or the ratio of DRAM memory to Flash memory are configurable for optimal use with a particular application (for example, POS, inter-bank transaction, stock market transaction,
scientific computation such as fluid dynamics for automobile and ship design, weather prediction, oil and gas expeditions, medical diagnostics such as diagnostics based on the fuzzy logic, medical data processing, simple information sharing and searching such as web search, retail store website, company home page, email or information distribution and archive, security service, and entertainment such as video-on-demand).
[0073] In certain embodiments, the device contains a high density Flash memory with a low density DRAM, wherein the DRAM is used as a data buffer for read/write operation. The Flash serves as the main memory. Certain embodiments described herein overcome the needs of having a long separation period between an Activate command (may be referred to as RAS) and a corresponding read or write command (may be referred to as first CAS command).
[0074] In accordance with one embodiment, described with reference to FIGS. 3 A and 3B, a memory system 300 includes a non- volatile (for example Flash) memory subsystem 302 and a volatile (for example DRAM) memory subsystem 304. The examples of FIGS. 3A and 3B are directed to architectures of a non- volatile DIMM (NVDIMM) NVDIMM system that may use a power subsystem (not shown) that can include a battery or a capacitor as a means for energy storage to copy DRAM memory data into Flash memory when power loss occurs, is detected, or is anticipated to occur during operation. When normal power is restored, a restore NVDIMM operation is initiated and the data stored in the Flash memory is properly restored to the DRAM memory. In this architecture, the density of the Flash is about the same as the DRAM memory size or within a few multiples, although in some applications it may be higher. This type of architecture may also be used to provide non-volatile storage that is connected to the FSB (front side bus) to support RAID (Redundant Array of Independent Disks) based systems or other type of operations. An NVDIMM controller 306 receives and interprets commands from the system memory controller hub (MCH). The NVDIMM controller 306 control the NVDIMM DRAM and Flash memory operations. In FIG. 3A, the DRAM 304 communicates data with the MCH, while an internal bus 308 is used for data transfer between the DRAM and Flash memory subsystems. In FIG. 3B, the NVDIMM controller 306' of NVDIMM 300' monitors events or commands and enables data transfer to occur in a first mode between the DRAM 304' and Flash 302' or in a second mode between the DRAM and the MCH.
[0075] In accordance with one embodiment, a general architecture for a Flash and DRAM hybrid DIMM (FDHDIMM) system 400 is shown in FIG. 4A. The FDHDIMM interfaces with
an MCH (memory controller hub) to operate and behave as a high density DIMM, wherein the MCH interfaces with the non-volatile memory subsystem (for example Flash) 402 is controlled by an FDHDIMM controller 404. Although the MCH interfaces with the Flash via the
FDHDIMM controller, the FDHDIMM overall performance is governed by the Flash access time. The volatile memory subsystem (for example DRAM) 406 is primarily used as a data buffer or a temporary storage location such that data from the Flash memory 402 is transferred to the DRAM 406 at the Flash access speed, and buffered or collected into the DRAM 406, which then transfers the buffered data to the MCH based on the access time of DRAM. Similarly, when the MCH transfers data to the DRAM 406, the FDHDIMM controller 404 manages the data transfer from the DRAM 406 to the Flash 402. Since the Flash memory access speed (both read and write) is relatively slower than DRAM, (e.g. for example a few hundred microseconds for read access), the average data throughput rate of FDHDIMM 400 is limited by the Flash access speed. The DRAM 406 serves as a data buffer stage that buffers the MCH read or write data. Thus, the DRAM 406 serves as a temporary storage for the data to be transferred from/to the Flash 402. Furthermore, in accordance with one embodiment, the MCH recognizes the physical density of an FDHDIMM operating as a high density DIMM as the density of Flash alone.
[0076] In accordance with one embodiment, a read operation can be performed by the MCH by sending an activate command (may be simply referred to as RAS, or row address strobe) to the FDHDIMM 400 to conduct a pre-fetch read data operation from the Flash 402 to the DRAM 406, with the pre-fetch data size being for example a page (1KB or 2KB, or may be
programmable to any size). The MCH then sends a read command (may be simply referred to as CAS, or column address strobe) to read the data out input of the DRAM. In this embodiment, the data transfer from Flash to DRAM occurs at Flash access speed rates, while data transfer from DRAM to MCH occurs at DRAM access speed rates. In this example, data latency and throughput rates are the same as any DRAM operation as long as the read operations are executed onto the pages that were opened with the activate command previously sent to pre-fetch data from the Flash to DRAM. Thus, a longer separation time period between the RAS (e.g. Activate command) and the first CAS (column address strobe e.g. read or write command) is required to account for the time it takes to pre-fetch data from the Flash to DRAM.
[0077] An example of FDHDIMM operating as a DDR DIMM with SSD is shown in FIG. 4B, wherein the FDHDIMM 400'supports two different interface interpretations to the MCH. In the first interface interpretation, the MCH views the FDHDIMM 400' as a combination of DRAM DIMM and SSD (not illustrated). In this mode the MCH needs to manage two address spaces, one for the DRAMs 402' and one for the Flash 404'. The MCH is coupled to, and controls, both of the DRAM and Flash memory subsystems. One advantage of this mode is that the CPU does not need to be in the data path when data is moved from DRAM to Flash or from Flash to DRAM. In the second interface interpretation, the MCH views the FDHDIMM 400' as an on-DIMM Flash with the SSD in an extended memory space that is behind the DRAM space. Thus, in this mode, the MCH physically fetches data from the SSD to the DDR DRAM and then the DRAM sends the data to the MCH. Since all data movement occurs on the FDHDIMM, this mode will provide better performance than if the data were to be moved through or via the CPU.
[0078] In accordance with one embodiment and as shown in FIG. 4B, the FDHDIMM 400' receives control signals 408 from the MCH, where the control signals may include one or more control signals specifically for the DRAM 402' operation and one or more control signals specifically for the Flash 404' operation. In this embodiment, the MCH or CPU is coupled to the FDHDIMM via a single data bus interface 410 which couples the MCH to the DRAM.
[0079] FIGS. 5A and 5B are block diagrams of a memory module 500 that is couplable to a host system (not shown). The host system may be a server or any other system comprising a memory system controller or an MCH for providing and controlling the read/write access to one or more memory systems, wherein each memory system may include a plurality of memory subsystems, a plurality of memory devices, or at least one memory module. The term
"read/write access" means the ability of the MCH to interface with a memory system or subsystem in order to write data into it or read data from it, depending on the particular requirement at a particular time.
[0080] In certain embodiments, memory module 500 is a Flash-DRAM hybrid memory subsystem which may be integrated with other components of a host system. In certain embodiments, memory module 500 is a Flash-DRAM hybrid memory module that has the DIMM (dual-inline memory module) form factor, and may be referred to as a FDHDIMM, although it is to be understood that in both structure and operation it may be different from the FDHDIMM discussed above and described with reference to FIGS. 4 A and 4B. Memory
module 500 includes two on-module intermediary components: a controller and a data manager. These on-module intermediary components may be physically separate components, circuits, or modules, or they may be integrated onto a single integrated circuit or device, or integrated with other memory devices, for example in a three dimensional stack, or in any one of several other possible expedients for integration known to those skilled in the art to achieve a specific design, application, or economic goal. In the case of a DIMM, these on-module intermediary components are an on-DIMM Controller (CDC) 502 and an on-DIMM data manager (DMgr) 504. While the DIMM form factor will predominate the discussion herein, it should be understood that this is for illustrative purposes only and memory systems using other form factors are contemplated as well. CDC 502 and data manager DMgr 504 are operative to manage the interface between a non-volatile memory subsystem such as a Flash 506, a volatile memory subsystem such as a DRAM 508, and a host system represented by MCH 510.
[0081] In certain embodiments, CDC 502 controls the read/write access to/from Flash memory 506 from/to DRAM memory 508, and to/from DRAM memory from/to MCH 510. Read/write access between DRAM 508, Flash 506 and MCH 510 may be referred to herein generally as communication, wherein control and address information C/A 560 is sent from MCH 510 to CDC 502, and possible data transfers follow as indicated by Data 550, Data 555, and/or Data 556. In certain embodiments, the CDC 502 performs specific functions for memory address transformation, such as address translation, mapping, or address domain conversion, Flash access control, data error correction, manipulation of data width or data formatting or data modulation between the Flash memory and DRAM, and so on. In certain embodiments, the CDC 502 ensures that memory module 500 provides transparent operation to the MCH in accordance with certain industry standards, such as DDR, DDR2, DDR3, DDR4 protocols. In the arrangement shown in FIGS. 5A and 5B, there is no direct access from the MCH 510 to the Flash 506 memory subsystem. Thus in accordance with certain embodiments, the Flash access speed has minimal impact on the overall FDHDIMM access speed. In the schematic illustration of FIG. 5B and in accordance with one embodiment, the CDC controller 502 receives standard DDR commands from the MCH, interprets, and produces commands and/or control signals to control the operation of the Data manager (DMgr), the Flash memory and the DRAM memory. The DMgr controls the data path routing amongst DRAMs, Flash and MCH, as detailed below. The data path routing control signals are independently operated without any exclusivity.
[0082] An exemplary role of DMgr 504 is described with reference to FIG. 6. In certain embodiments and in response to communication from CDC 502, DMgr 504 provides a variety of functions to control data flow rate, data transfer size, data buffer size, data error monitoring or data error correction. For example, these functions or operations can be performed on-the-fly (while data is being transferred via the DMgr 504) or performed on buffered or stored data in DRAM or a buffer. In addition, one role of DMgr 504 is to provide interoperability among various memory subsystems or components and/or MCH 510.
[0083] In one embodiment, an exemplary host system operation begins with initialization. The CDC 502 receives a first command from the MCH 510 to initialize FDHDIMM 500 using a certain memory space. The memory space as would be controlled by MCH 510 can be configured or programmed during initialization or after initialization has completed. The MCH 510 can partition or parse the memory space in various ways that are optimized for a particular application that the host system needs to run or execute. In one embodiment, the CDC 502 maps the actual physical Flash 506 and DRAM 508 memory space using the information sent by MCH 510 via the first command. In one embodiment, the CDC 502 maps the memory address space of any one of the Flash 506 and DRAM 508 memory subsystems using memory address space information that is received from the host system, stored in a register within FDHDIMM 500, or stored in a memory location of a non- volatile memory subsystem, for example a portion of Flash 506 or a separate non- volatile memory subsystem. In one embodiment, the memory address space information corresponds to a portion of initialization information of the FDHDIMM 500.
[0084] In one embodiment, MCH 510 may send a command to restore a certain amount of data information from Flash 506 to DRAM 508. The CDC 502 provides control information to DMgr 504 to appropriately copy the necessary information from Flash 506 to the DRAM 508. This operation can provide support for various host system booting operations and/or a special host system power up operation.
[0085] In one embodiment, MCH 510 sends a command which may include various fields comprising control information regarding data transfer size, data format options, and/or startup time. CDC 502 receives and interprets the command and provides control signals to DMgr 504 to control the data traffic between the Flash 506, the DRAM 508, and the MCH 510. For example, DMgr 504 receives the data transfer size, formatting information, direction of data flow (via one or more multiplexers such as 611, 612, 621, 622 as detailed below), and the starting time of the
actual data transfer from CDC 502. DMgr 504 may also receive additional control information from the CDC 502 to establish a data flow path and/or to correctly establish the data transfer fabric. In certain embodiments, DMgr 504 also functions as a bi-directional data transfer fabric. For example, DMgr 504 may have more than 2 sets of data ports facing the Flash 506 and the DRAM 508. Multiplexers 611 and 612 provide controllable data paths from any one of the DRAMs 508(1) and 508(2) (DRAM-A and DRAM-B) to any one of the MCH 510 and the Flash 506. Similarly multiplexers 621 and 622 provide controllable data paths from any one of the MCH and the Flash memory to any one of the DRAMs 508(1) and 508(2) (DRAM-A and DRAM-B). In one embodiment, DRAM 508(1) is a segment of DRAM 508, while in other embodiments, DRAM 508(1) is a separate DRAM memory subsystem. It will be understood that each memory segment can comprise one or more memory circuits, a memory devices, and/or memory integrated circuits. Of course other configurations for DRAM 508 are possible, and other data transfer fabrics using complex data paths and suitable types of multiplexing logic are contemplated.
[0086] In accordance with one embodiment, the two sets of multiplexors 611, 612 and 621, 622 allow independent data transfer to Flash 506 from DRAM-A 508(1) and DRAM-B 508(2). For example, in response to one or more control signals or a command from CDC 502, DMgr 504 can transfer data from DRAM-A 508(1) to MCH 510, via multiplexer 611, at the same time as from DRAM-B 508(2) to the Flash 506, via multiplexer 612; or data is transferred from DRAM-B 508(2) to MCH 510, via multiplexer 611, and simultaneously data is transferred from the Flash 506 to DRAM-A 508(1), via multiplexer 621. Further, in the same way that data can be transferred to or from the DRAM in both device-wide or segment-by-segment fashion, data can be transferred to or from the flash memory in device-wide or segment-by-segment fashion, and the flash memory can be addressed and accessed accordingly.
[0087] In accordance with one embodiment the illustrated arrangement of data transfer fabric of DMgr 504 also allows the CDC 502 to control data transfer from the Flash memory to the MCH by buffering the data from the Flash 506 using a buffer 602, and matching the data rate and/or data format of MCH 510. The buffer 602 is shown in FIG. 6 as a portion of a data format module 604; however, buffer 602 may also be a distributed buffer such that one buffer is used for each one of the set of multiplexer logic elements shown as multiplexers 611, 612, 621, and 622. Various buffer arrangements may be used, such as a programmable size buffer to meet the
requirement of a given system design requirement, for example the disparity between read/write access time; or overall system performance, for example latency. In certain embodiments, the buffer 604 may introduce one or more clock cycle delays into a data communication path between MCH 510, DRAM 508, and Flash 506.
[0088] In certain embodiments, data format module 604 contains a data formatting subsystem (not shown) to enable DMgr 504 to format and perform data transfer in accordance with control information received from CDC502. Data buffer 604 of data format module 602, discussed above, also supports a wide data bus 606 coupled to the Flash memory 506 operating at a first frequency, while receiving data from DRAM 508 using a relatively smaller width data bus 608 operating at a second frequency, the second frequency being larger than the first frequency in certain embodiments. The buffer 602 is designed to match the data flow rate between the DRAM 508 and the Flash 506.
[0089] A register 690 provides the ability to register commands received from MCH 510 via C/A 560 (FIG. 5A). The register 690 may communicate these commands to CDC 502 and/or to the DRAM 508 and/or Flash 506. The register 690 communicates these registered commands to CDC 502 for processing. The register 690 may also include multiple registers (not shown), such that it can provide the ability to register multiple commands, a sequence of commands, or provide a pipeline delay stage for buffering and providing a controlled execution of certain commands received form MCH 510.
[0090] In certain embodiments, the register 690 may register commands from MCH 510 and transmit the registered commands to DRAM 508 and/or Flash 506 memory subsystems. In certain embodiments, the CDC 502 monitors commands received from MCH 510, via control and address bus C/A 560, and provides appropriate control information to DMgr 504, DRAM 508, or Flash 506 to execute these commands and perform data transfer operations between MCH 510 and FDHDIMM 500 via MCH data bus 610.
[0091] FIG. 7 illustrates a functional block diagram of the CDC 502. In certain
embodiments, the major functional blocks of the CDC 502 are a DRAM control block
DRAMCtrl 702, Flash control block FlashCtrl 704, MCH command interpreter Cmdlnt 706, DRAM-Flash interface scheduler Scheduler 708, and DMgr control block (DMgrCtrl) 710.
[0092] In accordance with one embodiment, DRAMCtrl 702 generates DRAM commands that are independent from the commands issued by the MCH 510. In accordance with one
embodiment, when the MCH 510 initiates a read/write operation from/to the same DRAM 508 that is currently executing a command from the DRAMCtrl 702, then the CDC 502 may choose to instruct DRAMCtrl 702 to abort its operation in order to execute the operation initiated by the MCH. However, the CDC 502 may also pipeline the operation so that it causes DRAMCtrl 702 to either halt or complete its current operation prior to executing that of the MCH. The CDC 502 may also instruct DRAMCtrl 702 to resume its operation once the command from MCH 510 is completed.
[0093] In accordance with one embodiment, the FlashCtrl 704 generates appropriate Flash commands for the proper read/write operations. The Cmdlnt 706 intercepts commands received from MCH 510 and generates the appropriate control information and control signals and transmit them to the appropriate FDHDIMM functional block. For example, Cmdlnt 706 issues an interrupt signal to the DRAMCtrl 702 when the MCH issues a command that collides (conflicts) with the currently executing or pending commands that DRAMCtrl 702 has initiated independently from MCH 510, thus subordinating these commands to those from the MCH. The Scheduler 708 schedules the Flash-DRAM interface operation such that there is no resource conflict in the DMgr 504. In accordance with one embodiment, the Scheduler 708 assigns time slots for the DRAMCtrl 702 and FlashCtrl 704 operation based on the current status and the pending command received or to be received from the MCH. The DMgrCtrl 710 generates and sends appropriate control information and control signals for the proper operation and control of the data transfer fabric to enable or disable data paths between Flash 506, DRAM 508, and the MCH 510.
[0094] FIG. 8A is a block diagram showing a Flash-DRAM hybrid DIMM (FDHDIMM) 801. As seen from FIG. 8 A, this Flash-DRAM hybrid DIMM requires two separate and independent address buses to separately control the address spaces: one for the Flash memory Flash 803 and the other for the DRAM memory DRAM 805. The MCH 810 treats the DRAM 805 and Flash 803 as separate memory subsystems, for example DRAM and SSD/HD memory subsystems. The memory in each address space is controlled directly by the MCH. However, the on-DIMM data path 807 between Flash 803 and DRAM 805 allows for direct data transfer to occur between the Flash 803 and the DRAM 805 in response to control information from Ctrl 830. In this embodiment, this data transfer mechanism provides direct support for executing commands from the MCH without having the MCH directly controlling the data transfer, and
thus improving data transfer performance from Flash 803 to the DRAM 805. However, the MCH needs to manage two address spaces and two different memory protocols simultaneously. Moreover, the MCH needs to map the DRAM memory space into the Flash memory space, and the data interface time suffers due to the difference in the data access time between the Flash memory and the DRAM memory.
[0095] In accordance with one embodiment, a memory space mapping of a Flash-DRAM hybrid DIMM is shown in FIG. 8B. A memory controller of a host system (not shown) controls both of the DRAM 508 address space and the Flash 506 address space using a single unified address space. The CDC 502 receives memory access commands from the MCH and generates control information for appropriate mapping and data transfer between Flash and DRAM memory subsystem to properly carry out the memory access commands. In one embodiment, the memory controller of the host system views the large Flash memory space as a DRAM memory space, and accesses this unified memory space with a standard DDR (double data rate) protocol used for accessing DRAM. The unified memory space in this case can exhibit overlapping memory address space between the Flash 506 and the DRAM 508. The overlapping memory address space may be used as a temporary storage or buffer for data transfer between the Flash 506 and the DRAM 508. For example, the DRAM memory space may hold a copy of data from the selected Flash memory space such that the MCH can access this data normally via DDR memory access commands. The CDC 502 controls the operation of the Flash 506 and DRAM 508 memory subsystems in response to commands received from a memory controller of a host system.
[0096] In one embodiment, the unified memory space corresponds to a contiguous address space comprising a first portion of the address space of the Flash 506 and a first portion of the address space of the DRAM 508. The first portion of the address space of the Flash 506 can be determined via a first programmable register holding a first value corresponding to the desired Flash memory size to be used. Similarly, the first portion of the address space of the DRAM 508 can be determined via a second programmable register holding a second value corresponding to the desired DRAM memory size to be used. In one embodiment, any one of the first portion of the address space of the Flash 506 and the first portion of the address space of the DRAM 508 is determined via a first value corresponding to a desired performance or memory size, the first
value being received by the CDC 502 via a command sent by memory controller of the host system.
[0097] In accordance with one embodiment, a flow diagram directed to the transfer of data from Flash memory to DRAM memory and vice versa in an exemplary FDHDIMM is shown in Fig. 9. In certain embodiments, data transfer from the Flash 506 to the DRAM 508 occurs in accordance with memory access commands which the CDC 502 receives from the memory controller of the host system. In certain embodiments, the CDC 502 controls the data transfer from the DRAM 508 to the Flash 506 so as to avoid conflict with any memory operation that is currently being executed. For example, when all the pages in a particular DRAM memory block are closed. The CDC 502 partitions the DRAM memory space into a number of blocks for the purpose of optimally supporting the desired application. The controller can configure memory space in the memory module based on at least one of one or more commands received from the MCH, instructions received from the MCH, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non-volatile memory subsystem, and a timing value. Furthermore, the block size can be configurable by the memory controller of the host system, such that the number pages in a block can be optimized to support a particular application or a task. Furthermore, the block size may be configured on-the-fly, e.g. CDC 502 can receive instruction regarding a desired block size from the memory controller via a memory command, or via a programmable value.
[0098] In certain embodiments, a memory controller can access the memory module using a standard access protocol, such as JEDEC's DDR DRAM, by sending a memory access command to the CDC 502 which in turn determines what type of a data transfer operation it is and the corresponding target address where the data information is stored, e.g. data information is stored in the DRAM 508 or Flash 506 memory subsystems. In response to a read operation, if the CDC 502 determines that data information, e.g. a page (or block), does not reside in the DRAM 508 but resides in Flash 506, then the CDC 502 initiates and controls all necessary data transfer operations from Flash 506 to DRAM 508 and subsequently to the memory controller. In one embodiment, once the CDC 502 completes the data transfer operation of the requested data information from the Flash 506 to the DRAM 508, the CDC 502 alerts the memory controller to retrieve the data information from the DRAM 508. In on embodiment, the memory controller
initiates the copying of data information from Flash 506 to DRAM 508 by writing, into a register in the CDC 502, the target Flash address along with a valid block size. The CDC 502 in turn, executes appropriate operations and generates control information to copy the data information to the DRAM 508. Consequently, the memory controller can access or retrieve the data information using standard memory access commands or protocol.
[0099] An exemplary flow chart is shown in FIG. 9, a starting step or power up 902, is followed by an initialization step 904, the memory controller initiates, at step 906, a data move from the Flash 506 to the DRAM 508 by writing target address and size, to a control register in the CDC 502, which then copies, at 908, data information from the Flash 506 to the DRAM 508 and erases the block in the Flash. Erasing the data information from Flash may be accomplished independently from (or concurrently with) other steps that CDC 502 performs in this flow chart, i.e. other steps can be executed concurrently with the Erase the Flash block step. Once the data information or a block of data information is thus moved to the DRAM 508, the memory controller can operate on this data block using standard memory access protocol or commands at 910. The CDC 502 checks, at 912, if any of the DRAM 508 blocks, or copied blocks, are closed. If the memory controller closed any open blocks in DRAM 508, then the CDC 502 initiate a Flash write to write the closed block from the DRAM 508 to the Flash 506, at 914. In addition, the memory controller, at 916, reopens the closed block that is currently being written into the Flash 506, then the CDC 502 stops the Flash write operation and erases the Flash block which was being written to, as shown at 918. Otherwise, the CDC 502 continues and completes the writing operation to the Flash at 920.
[00100] The dashed lines in FIG. 9 indicate independent or parallel activities that can be performed by the CDC 502. At any time the CDC 502 receives a DRAM load command from a memory controller which writes a Flash target address and/or block size information into the RC register(s) at 922, as described above, then the CDC 502 executes a load DRAM w/RC step 906 and initiates another branch (or a thread) of activities that includes steps 908 - 922. In one embodiment, the CDC 502 controls the data transfer operations between DRAM 508 and Flash 506 such that the Flash 506 is completely hidden from the memory controller. The CDC 502 monitors all memory access commands sent by the memory controller using standard DRAM protocol and appropriately configures and manipulate both Flash 506 and DRAM 508 memory subsystems to perform the requested memory access operation and thus achieve the desired
results. The memory controller does not interface directly with the Flash memory subsystem. Instead, the memory controller interfaces with the CDC 502 and/or DMgr 504 as shown in Fig. 5 and Fig. 6. Moreover, the memory controller may use one or more protocol, such as DDR, DDR2, DDR3, DDR4 protocols or the like.
[00101] In accordance with one embodiment, an example of mapping a DRAM address space to Flash memory address space is shown in FIG. 10. Two sets (1002, 1004) of address bits AD6 to AD 17, forming a 24 bit extended memory page address, are allocated for the block address. For example, assuming a Block size of 256K Bytes, then a 24-bit block address space (using the two sets of AD6 to AD 17 1002 and 1004) would enable access to 4TB of Flash memory storage space. If a memory module has 1GB of DRAM storage capacity, then it can hold approximately 4K Blocks of data in the DRAM memory, each Block comprise 256 K Bytes of data. The DRAM address space, corresponding to the 4K blocks, can be assigned to different virtual ranks and banks, where the number of virtual ranks and banks is configurable and can be manipulated to meet a specific design or performance needs. For example, if a 1G Bytes memory module is configured to comprise two ranks with eight banks per rank, then each bank would hold two hundred fifty (250) blocks or the equivalent of 62 M Bytes or 62K pages, where each page correspond to a IK Bytes. Other configurations using different page, block, banks, or ranks numbers may also be used. Furthermore, an exemplary mapping of 24-bit DDR DIMM block address to Flash memory address, using Block addressing as described above, is shown in Fig. 10. The 24-bit can be decomposed into fields, such as a logical unit number LUN address 1060 field, a Block address 1050 field, a Plane address 1040, a Page address 1030, and a group of least significant address bits A0Ai 1020. The Plane address 1040 is a sub address of the block address, and it may be used to support multiple page IO so as to improve Flash memory subsystem operation. In this example, it is understood that different number of bits may be allocated to each field of the 24-bit
[00102] The CDC 502 manages the block write-back operation by queuing the blocks that are ready to be written back to the Flash memory. As described above, if any page in a queued block for a write operation is reopened, then the CDC 502 will stop the queued block write operation, and remove the block from the queue. Once all the pages in a block are closed, then the CDC 502 restarts the write-back operation and queue the block for a write operation.
[00103] In accordance with one embodiment, an exemplary read operation from Flash 506 to DRAM 508 can be performed in approximately 400μ8, while a write operation from DRAM 508 to Flash 506 can be performed in approximately 22ms resulting in a read to write ratio of 55 to 1. Therefore, if the average time a host system's memory controller spends accessing data information in a Block of DRAM is about 22ms (that is the duration that a Block comprises one or more pages that are open), then the block write-back operation from DRAM to Flash would not impact performance and hence the disparity between read and write access may be completely hidden from the memory controller. If the block usage time is 1 1ms instead of 22ms, then the CDC 502 control the data transfer operation between DRAM 508 and Flash 506 such that there are no more than 9 closed blocks in the queue to be written-back to the Flash memory, hence approximately an average of 100ms can be maintained for a standard DDR DRAM operation. Moreover, the number of closed Blocks in the queue to be written-back to the Flash memory subsystem varies with the average block usage time and the desired performance for a specific host system or for a specific application running using the host system resources.
[00104] Consequently, the maximum number of closed Blocks to be written-back to Flash can be approximated to be
((#of blocks per bank)/(ratio of 'Flash block write time' to lash_read_time'))*( (Block usage time)/( 'Flash block write time'))
[00105] In order to maintain less than 100ms time period for queued write-back Blocks, then using a Flash memory subsystem having 22ms write access time per Block would results in a maximum number of four Blocks to be queued for write operation to Flash 506. Therefore, on average approximately 88ms (= 22ms * 4) for blocks means that each bank should not have more than four Blocks that need to be written back to the Flash 506.
[00106] The above equation also indicates that bigger DRAM memory space can support shorter block usage times. For example, 2GB of DRAM memory allows the 8 closed blocks to be written-back to Flash. The table in FIG. 11 provides an estimation of the maximum allowed closed blocks in the queue to be written back to the Flash memory for different DRAM density using various average block use time.
[00107] While embodiments and applications have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts disclosed herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.
Claims
1. A memory module couplable to a memory controller of a host system, comprising:
a non-volatile memory subsystem;
a data manager coupled to the non-volatile memory subsystem;
a volatile memory subsystem coupled to the data manager and operable to exchange data with the non-volatile memory subsystem by way of the data manager; and
a controller operable to receive commands from the memory controller and to direct (i) operation of the non-volatile memory subsystem, (ii) operation of the volatile memory subsystem, and (iii) transfer of data between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on at least one received command from the memory controller.
2. The memory module of claim 1, wherein the data manager is operable to control one or more of data flow rate, data transfer size, data buffer size, data error monitoring, and data error correction in response to receiving at least one of a control signal and control information from the controller.
3. The memory module of claim 1, wherein the data manager controls data traffic between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on instructions received from the controller.
4. The memory module of claim 3, wherein data traffic control relates to any one or more of data flow rate, data transfer size, data buffer size, data transfer bit width, formatting information, direction of data flow, and the starting time of data transfer.
5. The memory module of claim 1, wherein the controller configures at least one of a first memory address space of the volatile memory subsystem and a second memory address space of the non-volatile memory subsystem in response to at least one of a received command from the memory controller and memory address space initialization information of the memory module.
6. The memory module of claim 1 , wherein the data manager is configured as a bidirectional data transfer fabric having two or more sets of data ports coupled to any one of the volatile and non- volatile memory subsystems.
7. The memory module of claim 6, wherein at least one of the volatile and non-volatile memory subsystems comprises one or more memory segments.
8. The memory module of claim 7, wherein each memory segment comprises at least one memory circuit, memory device, or memory die.
9. The memory module of claim 1 , wherein the volatile memory subsystem comprises DRAM memory.
10. The memory module of claim 7, wherein at least one set of data ports is operated by the data manager to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or non- volatile memory subsystems.
11. The memory module of claim 6, wherein the data manager further includes a data format module configured to format data to be transferred between any two or more of the memory controller, the volatile memory subsystem, and the non-volatile memory subsystem based on control information received from the controller.
12. The memory module of 1 1 , wherein the data manager further includes a data buffer for buffering data delivered to or from the non- volatile memory subsystem.
13. A method for managing a memory module by a memory controller, the memory module including volatile and non- volatile memory subsystems, the method comprising:
receiving control information from the memory controller, wherein the control information is received using a protocol of the volatile memory subsystem;
identifying a data path to be used for transferring data to or from the memory module using the received control information; and using a data manager and a controller of the memory module to transfer data between any two or more of the memory controller, the volatile memory subsystem, and the non- volatile memory subsystem based on at least one of the received control information and the identified data path.
14. The method of claim 13, further comprising operating the data manager to control one or more of data flow rate, data transfer size, data width size, data buffer size, data error monitoring, data error correction, and the starting time of the transfer of data.
15. The method of claim 13, further comprising operating the data manager as a bidirectional data transfer fabric with two or more sets of data ports coupled to any one of the volatile and non- volatile memory subsystems.
16. The memory module of claim 13, wherein at least one of the volatile and non- volatile memory subsystems comprises one or more memory segments.
17. The method of claim 15, further comprising operating the data ports to independently and/or concurrently transfer data to or from one or more memory segments of the volatile or nonvolatile memory subsystems.
18. The method of claim 13, further comprising directing transfer of data bi-directionally between the volatile and non-volatile memory subsystems using the data manager and in response to memory access commands received by the controller from the memory controller.
19. The method of claim 18, further comprising buffering the data transferred between the memory controller and non-volatile memory subsystem using the volatile memory subsystem.
20. The method of claim 13, further comprising using the controller to perform one or more of memory address translation, memory address mapping, address domain conversion, memory access control, data error correction, and data width modulation between the volatile and nonvolatile memory subsystems.
21. The method of claim 13, further comprising using the controller to configure memory space in the memory module based on at least one of a command received from the memory controller, a programmable value written into a register, a value corresponding to a first portion of the volatile memory subsystem, a value corresponding to a first portion of the non- volatile memory subsystem, and a timing value.
22. The method of claim 21, wherein the controller configures the memory space of the memory module using at least a first portion of the volatile memory subsystem and a first portion of the non- volatile memory subsystem, and the controller presents a unified memory space to the memory controller.
23. The method of claim 21, wherein the controller configures the memory space in the memory module using partitioning instructions that are application-specific.
24. The method of claim 13, further comprising:
operating the volatile memory subsystem at a first clock frequency when the memory system is in a first mode of operation in which data is communicated between the volatile memory subsystem and the host system;
operating the non-volatile memory subsystem at a second clock frequency when the memory system is in a second mode of operation in which data is communicated between the volatile memory subsystem and the non-volatile memory subsystem; and
operating the volatile memory subsystem at a third clock frequency when the memory system is in the second mode of operation, the third clock frequency being less than the first clock frequency.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020147005608A KR20140063660A (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
CN201280047758.XA CN103890688B (en) | 2011-07-28 | 2012-07-28 | A kind of FLASH DRAM mixing memory modules |
EP12817751.6A EP2737383B1 (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
EP21200871.8A EP3985518A1 (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
EP17191878.2A EP3293638B1 (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
PL17191878T PL3293638T3 (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161512871P | 2011-07-28 | 2011-07-28 | |
US61/512,871 | 2011-07-28 | ||
US13/559,476 US8874831B2 (en) | 2007-06-01 | 2012-07-26 | Flash-DRAM hybrid memory module |
US13/559,476 | 2012-07-26 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2013016723A2 true WO2013016723A2 (en) | 2013-01-31 |
WO2013016723A3 WO2013016723A3 (en) | 2014-05-08 |
Family
ID=47601785
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2012/048750 WO2013016723A2 (en) | 2011-07-28 | 2012-07-28 | Flash-dram hybrid memory module |
Country Status (6)
Country | Link |
---|---|
US (7) | US8874831B2 (en) |
EP (3) | EP3985518A1 (en) |
KR (1) | KR20140063660A (en) |
CN (2) | CN103890688B (en) |
PL (1) | PL3293638T3 (en) |
WO (1) | WO2013016723A2 (en) |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140181364A1 (en) * | 2012-12-21 | 2014-06-26 | Dell Products L.P. | Systems And Methods For Support Of Non-Volatile Memory On A DDR Memory Channel |
US8880791B2 (en) | 2007-06-01 | 2014-11-04 | Netlist, Inc. | Isolation switching for backup of registered memory |
US8904098B2 (en) | 2007-06-01 | 2014-12-02 | Netlist, Inc. | Redundant backup using non-volatile memory |
CN104636267A (en) * | 2013-11-11 | 2015-05-20 | 群联电子股份有限公司 | Storage control method, storage storing device and storage control circuit unit |
EP2911065A1 (en) * | 2014-02-23 | 2015-08-26 | Rambus Inc. | Distributed procedure execution and file systems on a memory interface |
WO2015155103A1 (en) * | 2014-04-08 | 2015-10-15 | Fujitsu Technology Solutions Intellectual Property Gmbh | Method for improved access to a main memory of a computer system, corresponding computer system and computer program product |
US9275733B2 (en) | 2011-08-24 | 2016-03-01 | Rambus Inc. | Methods and systems for mapping a peripheral function onto a legacy memory interface |
US9367390B2 (en) | 2013-11-01 | 2016-06-14 | Phison Electronics Corp. | Memory controlling method, memory storage device and memory controlling circuit unit |
US9430344B2 (en) | 2013-10-01 | 2016-08-30 | Globalfoundries Inc. | Memory system for mirroring data |
US9720604B2 (en) | 2015-08-06 | 2017-08-01 | Sandisk Technologies Llc | Block storage protocol to RAM bypass |
US9880778B2 (en) | 2015-11-09 | 2018-01-30 | Google Inc. | Memory devices and methods |
US9996284B2 (en) | 2013-06-11 | 2018-06-12 | Netlist, Inc. | Non-volatile memory storage for multi-channel memory system |
US10031674B2 (en) | 2015-10-07 | 2018-07-24 | Samsung Electronics Co., Ltd. | DIMM SSD addressing performance techniques |
US10198350B2 (en) | 2011-07-28 | 2019-02-05 | Netlist, Inc. | Memory module having volatile and non-volatile memory subsystems and method of operation |
US10209922B2 (en) | 2011-08-24 | 2019-02-19 | Rambus Inc. | Communication via a memory interface |
US10248328B2 (en) | 2013-11-07 | 2019-04-02 | Netlist, Inc. | Direct data move between DRAM and storage on a memory module |
US10372551B2 (en) | 2013-03-15 | 2019-08-06 | Netlist, Inc. | Hybrid memory system with configurable error thresholds and failure analysis capability |
US10380022B2 (en) | 2011-07-28 | 2019-08-13 | Netlist, Inc. | Hybrid memory module and system and method of operating the same |
US10503657B2 (en) | 2015-10-07 | 2019-12-10 | Samsung Electronics Co., Ltd. | DIMM SSD Addressing performance techniques |
US10838646B2 (en) | 2011-07-28 | 2020-11-17 | Netlist, Inc. | Method and apparatus for presearching stored data |
EP3754512A1 (en) * | 2019-06-20 | 2020-12-23 | Samsung Electronics Co., Ltd. | Memory device, method of operating the memory device, memory module, and method of operating the memory module |
US11016918B2 (en) | 2007-06-01 | 2021-05-25 | Netlist, Inc. | Flash-DRAM hybrid memory module |
US11048410B2 (en) | 2011-08-24 | 2021-06-29 | Rambus Inc. | Distributed procedure execution and file systems on a memory interface |
US11222671B2 (en) | 2019-06-20 | 2022-01-11 | Samsung Electronics Co., Ltd. | Memory device, method of operating the memory device, memory module, and method of operating the memory module |
EP4036916A1 (en) * | 2021-01-29 | 2022-08-03 | Commissariat à l'Energie Atomique et aux Energies Alternatives | Device comprising a non-volatile memory circuit |
CN114902197A (en) * | 2019-12-30 | 2022-08-12 | 超威半导体公司 | Command replay for non-volatile dual in-line memory modules |
US11586266B1 (en) | 2021-07-28 | 2023-02-21 | International Business Machines Corporation | Persistent power enabled on-chip data processor |
Families Citing this family (142)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9720616B2 (en) * | 2008-06-18 | 2017-08-01 | Super Talent Technology, Corp. | Data-retention controller/driver for stand-alone or hosted card reader, solid-state-drive (SSD), or super-enhanced-endurance SSD (SEED) |
US9170744B1 (en) | 2011-04-06 | 2015-10-27 | P4tents1, LLC | Computer program product for controlling a flash/DRAM/embedded DRAM-equipped system |
US9158546B1 (en) | 2011-04-06 | 2015-10-13 | P4tents1, LLC | Computer program product for fetching from a first physical memory between an execution of a plurality of threads associated with a second physical memory |
US9176671B1 (en) | 2011-04-06 | 2015-11-03 | P4tents1, LLC | Fetching data between thread execution in a flash/DRAM/embedded DRAM-equipped system |
US8930647B1 (en) | 2011-04-06 | 2015-01-06 | P4tents1, LLC | Multiple class memory systems |
US9164679B2 (en) | 2011-04-06 | 2015-10-20 | Patents1, Llc | System, method and computer program product for multi-thread operation involving first memory of a first memory class and second memory of a second memory class |
US9417754B2 (en) | 2011-08-05 | 2016-08-16 | P4tents1, LLC | User interface system, method, and computer program product |
WO2013101201A1 (en) * | 2011-12-30 | 2013-07-04 | Intel Corporation | Home agent multi-level nvm memory architecture |
US9258276B2 (en) | 2012-05-22 | 2016-02-09 | Xockets, Inc. | Efficient packet handling, redirection, and inspection using offload processors |
US20140165196A1 (en) | 2012-05-22 | 2014-06-12 | Xockets IP, LLC | Efficient packet handling, redirection, and inspection using offload processors |
US20140089573A1 (en) * | 2012-09-24 | 2014-03-27 | Palsamy Sakthikumar | Method for accessing memory devices prior to bus training |
KR20140064546A (en) * | 2012-11-20 | 2014-05-28 | 삼성전자주식회사 | Semiconductor memory device and computer system including the same |
US10910025B2 (en) * | 2012-12-20 | 2021-02-02 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Flexible utilization of block storage in a computing system |
US9250954B2 (en) | 2013-01-17 | 2016-02-02 | Xockets, Inc. | Offload processor modules for connection to system memory, and corresponding methods and systems |
US9378161B1 (en) | 2013-01-17 | 2016-06-28 | Xockets, Inc. | Full bandwidth packet handling with server systems including offload processors |
US9727462B2 (en) * | 2013-01-30 | 2017-08-08 | Hewlett Packard Enterprise Development Lp | Runtime backup of data in a memory module |
CN103970219B (en) * | 2013-01-30 | 2018-03-20 | 鸿富锦精密电子(天津)有限公司 | Storage device and the mainboard for supporting the storage device |
KR101752583B1 (en) * | 2013-03-14 | 2017-07-11 | 마이크론 테크놀로지, 인크. | Memory systems and methods including training, data organizing, and/or shadowing |
CN104981872B (en) * | 2013-03-15 | 2018-11-06 | 英特尔公司 | Storage system |
US9858181B2 (en) * | 2013-06-20 | 2018-01-02 | Hitachi, Ltd. | Memory module having different types of memory mounted together thereon, and information processing device having memory module mounted therein |
US9921980B2 (en) | 2013-08-12 | 2018-03-20 | Micron Technology, Inc. | Apparatuses and methods for configuring I/Os of memory for hybrid memory modules |
US20150106547A1 (en) * | 2013-10-14 | 2015-04-16 | Micron Technology, Inc. | Distributed memory systems and methods |
US9152584B2 (en) * | 2013-10-29 | 2015-10-06 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Providing bus resiliency in a hybrid memory system |
EP3066570A4 (en) * | 2013-11-07 | 2017-08-02 | Netlist, Inc. | Hybrid memory module and system and method of operating the same |
US11182284B2 (en) | 2013-11-07 | 2021-11-23 | Netlist, Inc. | Memory module having volatile and non-volatile memory subsystems and method of operation |
KR102156284B1 (en) * | 2013-11-27 | 2020-09-15 | 에스케이하이닉스 주식회사 | Memory and memory module including the same |
US9547447B2 (en) * | 2014-01-03 | 2017-01-17 | Advanced Micro Devices, Inc. | Dedicated interface for coupling flash memory and dynamic random access memory |
US20150347151A1 (en) * | 2014-05-28 | 2015-12-03 | Diablo Technologies Inc. | System and method for booting from a non-volatile memory |
US9645829B2 (en) * | 2014-06-30 | 2017-05-09 | Intel Corporation | Techniques to communicate with a controller for a non-volatile dual in-line memory module |
US9753793B2 (en) * | 2014-06-30 | 2017-09-05 | Intel Corporation | Techniques for handling errors in persistent memory |
US9747200B1 (en) * | 2014-07-02 | 2017-08-29 | Microsemi Solutions (U.S.), Inc. | Memory system with high speed non-volatile memory backup using pre-aged flash memory devices |
KR20160046391A (en) * | 2014-10-20 | 2016-04-29 | 삼성전자주식회사 | Hybrid DIMM structure and Driving Method thereof |
US11775443B2 (en) * | 2014-10-23 | 2023-10-03 | Hewlett Packard Enterprise Development Lp | Supervisory memory management unit |
US9721660B2 (en) | 2014-10-24 | 2017-08-01 | Microsoft Technology Licensing, Llc | Configurable volatile memory without a dedicated power source for detecting a data save trigger condition |
JP2016091523A (en) * | 2014-11-11 | 2016-05-23 | レノボ・シンガポール・プライベート・リミテッド | Method of increasing capacity of backup module, nvdimm system, and information processing apparatus |
US9715453B2 (en) * | 2014-12-11 | 2017-07-25 | Intel Corporation | Computing method and apparatus with persistent memory |
US20160098203A1 (en) * | 2014-12-18 | 2016-04-07 | Mediatek Inc. | Heterogeneous Swap Space With Dynamic Thresholds |
US10126950B2 (en) * | 2014-12-22 | 2018-11-13 | Intel Corporation | Allocating and configuring persistent memory |
WO2016114749A1 (en) | 2015-01-12 | 2016-07-21 | Hewlett Packard Enterprise Development Lp | Handling memory errors in memory modules that include volatile and non-volatile components |
US20160232112A1 (en) * | 2015-02-06 | 2016-08-11 | Futurewei Technologies, Inc. | Unified Memory Bus and Method to Operate the Unified Memory Bus |
US20160246715A1 (en) * | 2015-02-23 | 2016-08-25 | Advanced Micro Devices, Inc. | Memory module with volatile and non-volatile storage arrays |
CN106155926B (en) * | 2015-04-09 | 2019-11-26 | 澜起科技股份有限公司 | The data interactive method of memory and memory |
EP3286654B1 (en) * | 2015-04-20 | 2021-10-27 | Netlist, Inc. | Memory module and system and method of operation |
WO2016175856A1 (en) * | 2015-04-30 | 2016-11-03 | Hewlett Packard Enterprise Development Lp | Migrating data using dual-port non-volatile dual in-line memory modules |
US10649680B2 (en) | 2015-04-30 | 2020-05-12 | Hewlett Packard Enterprise Development Lp | Dual-port non-volatile dual in-line memory modules |
WO2016175855A1 (en) | 2015-04-30 | 2016-11-03 | Hewlett Packard Enterprise Development Lp | Replicating data using dual-port non-volatile dual in-line memory modules |
KR20160131171A (en) | 2015-05-06 | 2016-11-16 | 에스케이하이닉스 주식회사 | Memory module including battery |
US11257527B2 (en) | 2015-05-06 | 2022-02-22 | SK Hynix Inc. | Memory module with battery and electronic system having the memory module |
US10025747B2 (en) * | 2015-05-07 | 2018-07-17 | Samsung Electronics Co., Ltd. | I/O channel scrambling/ECC disassociated communication protocol |
US10261697B2 (en) | 2015-06-08 | 2019-04-16 | Samsung Electronics Co., Ltd. | Storage device and operating method of storage device |
US10152413B2 (en) | 2015-06-08 | 2018-12-11 | Samsung Electronics Co. Ltd. | Nonvolatile memory module and operation method thereof |
KR102290988B1 (en) * | 2015-06-08 | 2021-08-19 | 삼성전자주식회사 | Nonvolatile memory module and operating method thereof |
US9799402B2 (en) | 2015-06-08 | 2017-10-24 | Samsung Electronics Co., Ltd. | Nonvolatile memory device and program method thereof |
US9619329B2 (en) | 2015-06-22 | 2017-04-11 | International Business Machines Corporation | Converting volatile memory module devices to flashless non-volatile memory module devices |
US9645939B2 (en) | 2015-06-26 | 2017-05-09 | Intel Corporation | Hardware apparatuses and methods for distributed durable and atomic transactions in non-volatile memory |
US9904490B2 (en) | 2015-06-26 | 2018-02-27 | Toshiba Memory Corporation | Solid-state mass storage device and method for persisting volatile data to non-volatile media |
KR102274038B1 (en) | 2015-08-03 | 2021-07-09 | 삼성전자주식회사 | Nonvolatile memory module having back-up function |
KR102427262B1 (en) | 2015-09-11 | 2022-08-01 | 삼성전자주식회사 | Storage device including random access memory devices and nonvolatile memory devices |
KR102430561B1 (en) | 2015-09-11 | 2022-08-09 | 삼성전자주식회사 | Nonvolatile memory module having dual port dram |
CN116560563A (en) | 2015-10-01 | 2023-08-08 | 拉姆伯斯公司 | Memory system with cached memory module operation |
US20170109101A1 (en) * | 2015-10-16 | 2017-04-20 | Samsung Electronics Co., Ltd. | System and method for initiating storage device tasks based upon information from the memory channel interconnect |
KR102420152B1 (en) | 2015-11-18 | 2022-07-13 | 삼성전자주식회사 | Multi-communication Device in Memory System |
KR102513913B1 (en) * | 2015-12-03 | 2023-03-28 | 삼성전자주식회사 | Nonvolatile memory module and memory system |
US10303372B2 (en) | 2015-12-01 | 2019-05-28 | Samsung Electronics Co., Ltd. | Nonvolatile memory device and operation method thereof |
KR102513903B1 (en) * | 2015-12-03 | 2023-03-28 | 삼성전자주식회사 | Nonvolatile memory module and memory system |
US10025508B2 (en) | 2015-12-02 | 2018-07-17 | International Business Machines Corporation | Concurrent upgrade and backup of non-volatile memory |
CN105575433B (en) * | 2015-12-10 | 2019-11-22 | 北京兆易创新科技股份有限公司 | Nand memory and its device for balancing the WL Voltage Establishment time |
CN105354156A (en) * | 2015-12-10 | 2016-02-24 | 浪潮电子信息产业股份有限公司 | Mainboard design method capable of supporting NVDIMM (Non-Volatile Dual In-line Memory Module) |
US10019367B2 (en) | 2015-12-14 | 2018-07-10 | Samsung Electronics Co., Ltd. | Memory module, computing system having the same, and method for testing tag error thereof |
KR102491651B1 (en) | 2015-12-14 | 2023-01-26 | 삼성전자주식회사 | Nonvolatile memory module, computing system having the same, and operating method thereof |
CN106886495B (en) * | 2015-12-15 | 2019-10-18 | 北京兆易创新科技股份有限公司 | A kind of embedded system and its control method |
US10437483B2 (en) | 2015-12-17 | 2019-10-08 | Samsung Electronics Co., Ltd. | Computing system with communication mechanism and method of operation thereof |
US9971511B2 (en) | 2016-01-06 | 2018-05-15 | Samsung Electronics Co., Ltd. | Hybrid memory module and transaction-based memory interface |
US20170206165A1 (en) * | 2016-01-14 | 2017-07-20 | Samsung Electronics Co., Ltd. | Method for accessing heterogeneous memories and memory module including heterogeneous memories |
US9891864B2 (en) * | 2016-01-19 | 2018-02-13 | Micron Technology, Inc. | Non-volatile memory module architecture to support memory error correction |
US20170212835A1 (en) * | 2016-01-22 | 2017-07-27 | Samsung Electronics Co., Ltd. | Computing system with memory management mechanism and method of operation thereof |
KR102523141B1 (en) | 2016-02-15 | 2023-04-20 | 삼성전자주식회사 | Nonvolatile memory module comprising volatile memory device and nonvolatile memory device |
US10409719B2 (en) | 2016-03-17 | 2019-09-10 | Samsung Electronics Co., Ltd. | User configurable passive background operation |
KR102567279B1 (en) * | 2016-03-28 | 2023-08-17 | 에스케이하이닉스 주식회사 | Power down interrupt of non-volatile dual in line memory system |
KR102547056B1 (en) | 2016-03-28 | 2023-06-22 | 에스케이하이닉스 주식회사 | Command-address snooping for non-volatile memory module |
KR102535738B1 (en) | 2016-03-28 | 2023-05-25 | 에스케이하이닉스 주식회사 | Non-volatile dual in line memory system, memory module and operation method of the same |
CN105938458B (en) * | 2016-04-13 | 2019-02-22 | 上海交通大学 | The isomery mixing EMS memory management process of software definition |
US10152237B2 (en) | 2016-05-05 | 2018-12-11 | Micron Technology, Inc. | Non-deterministic memory protocol |
US10089228B2 (en) * | 2016-05-09 | 2018-10-02 | Dell Products L.P. | I/O blender countermeasures |
KR20170132483A (en) | 2016-05-24 | 2017-12-04 | 삼성전자주식회사 | Method of operating memory device |
US10534540B2 (en) | 2016-06-06 | 2020-01-14 | Micron Technology, Inc. | Memory protocol |
US10747694B2 (en) | 2016-06-07 | 2020-08-18 | Ncorium | Multi-level data cache and storage on a memory bus |
US10698732B2 (en) | 2016-07-19 | 2020-06-30 | Sap Se | Page ranking in operating system virtual pages in hybrid memory systems |
US11977484B2 (en) * | 2016-07-19 | 2024-05-07 | Sap Se | Adapting in-memory database in hybrid memory systems and operating system interface |
US10783146B2 (en) | 2016-07-19 | 2020-09-22 | Sap Se | Join operations in hybrid main memory systems |
US10474557B2 (en) | 2016-07-19 | 2019-11-12 | Sap Se | Source code profiling for line-level latency and energy consumption estimation |
US10387127B2 (en) | 2016-07-19 | 2019-08-20 | Sap Se | Detecting sequential access data and random access data for placement on hybrid main memory for in-memory databases |
US10452539B2 (en) * | 2016-07-19 | 2019-10-22 | Sap Se | Simulator for enterprise-scale simulations on hybrid main memory systems |
US10540098B2 (en) | 2016-07-19 | 2020-01-21 | Sap Se | Workload-aware page management for in-memory databases in hybrid main memory systems |
US10437798B2 (en) | 2016-07-19 | 2019-10-08 | Sap Se | Full system simulator and memory-aware splay tree for in-memory databases in hybrid memory systems |
US10339050B2 (en) * | 2016-09-23 | 2019-07-02 | Arm Limited | Apparatus including a memory controller for controlling direct data transfer between first and second memory modules using direct transfer commands |
US10847196B2 (en) | 2016-10-31 | 2020-11-24 | Rambus Inc. | Hybrid memory module |
KR102649048B1 (en) | 2016-11-02 | 2024-03-18 | 삼성전자주식회사 | Memory device and memory system including the same |
US10585624B2 (en) | 2016-12-01 | 2020-03-10 | Micron Technology, Inc. | Memory protocol |
US10002086B1 (en) | 2016-12-20 | 2018-06-19 | Sandisk Technologies Llc | Multi-channel memory operations based on bit error rates |
KR20180078512A (en) * | 2016-12-30 | 2018-07-10 | 삼성전자주식회사 | Semiconductor device |
US11003602B2 (en) | 2017-01-24 | 2021-05-11 | Micron Technology, Inc. | Memory protocol with command priority |
US11397687B2 (en) * | 2017-01-25 | 2022-07-26 | Samsung Electronics Co., Ltd. | Flash-integrated high bandwidth memory appliance |
US10635613B2 (en) | 2017-04-11 | 2020-04-28 | Micron Technology, Inc. | Transaction identification |
CN108877856B (en) * | 2017-05-10 | 2021-02-19 | 慧荣科技股份有限公司 | Storage device, recording method and preloading method |
US10496584B2 (en) * | 2017-05-11 | 2019-12-03 | Samsung Electronics Co., Ltd. | Memory system for supporting internal DQ termination of data buffer |
KR102400102B1 (en) * | 2017-05-11 | 2022-05-23 | 삼성전자주식회사 | Memory system for supporting internal DQ termination of data buffer |
US11010379B2 (en) | 2017-08-15 | 2021-05-18 | Sap Se | Increasing performance of in-memory databases using re-ordered query execution plans |
US10585754B2 (en) | 2017-08-15 | 2020-03-10 | International Business Machines Corporation | Memory security protocol |
KR102353859B1 (en) * | 2017-11-01 | 2022-01-19 | 삼성전자주식회사 | Computing device and non-volatile dual in-line memory module |
US10606513B2 (en) | 2017-12-06 | 2020-03-31 | Western Digital Technologies, Inc. | Volatility management for non-volatile memory device |
US10431305B2 (en) * | 2017-12-14 | 2019-10-01 | Advanced Micro Devices, Inc. | High-performance on-module caching architectures for non-volatile dual in-line memory module (NVDIMM) |
KR102448242B1 (en) * | 2018-03-01 | 2022-09-28 | 마이크론 테크놀로지, 인크. | Simultaneous execution of operations on data blocks based on the performance rates of other operations on data blocks |
US11579770B2 (en) | 2018-03-15 | 2023-02-14 | Western Digital Technologies, Inc. | Volatility management for memory device |
CN108874684B (en) * | 2018-05-31 | 2021-05-28 | 北京领芯迅飞科技有限公司 | NVDIMM interface data read-write device for splitting CACHE CACHE |
US11157319B2 (en) | 2018-06-06 | 2021-10-26 | Western Digital Technologies, Inc. | Processor with processor memory pairs for improved process switching and methods thereof |
US10636455B2 (en) | 2018-07-12 | 2020-04-28 | International Business Machines Corporation | Enhanced NVDIMM architecture |
US11169920B2 (en) * | 2018-09-17 | 2021-11-09 | Micron Technology, Inc. | Cache operations in a hybrid dual in-line memory module |
US10949117B2 (en) * | 2018-09-24 | 2021-03-16 | Micron Technology, Inc. | Direct data transfer in memory and between devices of a memory module |
US11099779B2 (en) * | 2018-09-24 | 2021-08-24 | Micron Technology, Inc. | Addressing in memory with a read identification (RID) number |
US10732892B2 (en) * | 2018-09-24 | 2020-08-04 | Micron Technology, Inc. | Data transfer in port switch memory |
US10901657B2 (en) | 2018-11-29 | 2021-01-26 | International Business Machines Corporation | Dynamic write credit buffer management of non-volatile dual inline memory module |
US11163475B2 (en) | 2019-06-04 | 2021-11-02 | International Business Machines Corporation | Block input/output (I/O) accesses in the presence of a storage class memory |
US11526441B2 (en) | 2019-08-19 | 2022-12-13 | Truememory Technology, LLC | Hybrid memory systems with cache management |
US11055220B2 (en) | 2019-08-19 | 2021-07-06 | Truememorytechnology, LLC | Hybrid memory systems with cache management |
US11513725B2 (en) * | 2019-09-16 | 2022-11-29 | Netlist, Inc. | Hybrid memory module having a volatile memory subsystem and a module controller sourcing read strobes to accompany read data from the volatile memory subsystem |
US11531601B2 (en) | 2019-12-30 | 2022-12-20 | Advanced Micro Devices, Inc. | Error recovery for non-volatile memory modules |
US11379393B2 (en) * | 2020-02-28 | 2022-07-05 | Innogrit Technologies Co., Ltd. | Multi-frequency memory interface and methods for configurating the same |
CN112000276B (en) * | 2020-06-19 | 2023-04-11 | 浙江绍兴青逸信息科技有限责任公司 | Memory bank |
US11355214B2 (en) * | 2020-08-10 | 2022-06-07 | Micron Technology, Inc. | Debugging memory devices |
KR20220091794A (en) | 2020-12-24 | 2022-07-01 | 삼성전자주식회사 | Semiconductor device and electronic device including the same |
US11687281B2 (en) * | 2021-03-31 | 2023-06-27 | Advanced Micro Devices, Inc. | DRAM command streak efficiency management |
US11715514B2 (en) | 2021-05-06 | 2023-08-01 | Advanced Micro Devices, Inc. | Latch bit cells |
US11527270B2 (en) * | 2021-05-06 | 2022-12-13 | Advanced Micro Devices, Inc. | Hybrid library latch array |
US11494319B1 (en) * | 2021-08-17 | 2022-11-08 | Micron Technology, Inc. | Apparatuses, systems, and methods for input/output mappings |
CN113946290B (en) * | 2021-10-14 | 2023-06-06 | 西安紫光国芯半导体有限公司 | Memory device and memory system based on three-dimensional heterogeneous integration |
CN114153402B (en) * | 2022-02-09 | 2022-05-03 | 阿里云计算有限公司 | Memory and data reading and writing method thereof |
FR3138709A1 (en) * | 2022-08-04 | 2024-02-09 | STMicroelectronics (Alps) SAS | FLASH memory device |
US20240111421A1 (en) * | 2022-09-30 | 2024-04-04 | Advanced Micro Devices, Inc. | Connection Modification based on Traffic Pattern |
CN116719486B (en) * | 2023-08-10 | 2023-11-17 | 杭州智灵瞳人工智能有限公司 | Multimode storage device with built-in data automatic transmission function and control method |
CN116955241B (en) * | 2023-09-21 | 2024-01-05 | 杭州智灵瞳人工智能有限公司 | Memory chip compatible with multiple types of memory media |
CN117033267B (en) * | 2023-10-07 | 2024-01-26 | 深圳大普微电子股份有限公司 | Hybrid memory master controller and hybrid memory |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070147115A1 (en) | 2005-12-28 | 2007-06-28 | Fong-Long Lin | Unified memory and controller |
US20070255898A1 (en) | 2006-04-28 | 2007-11-01 | Kabushiki Kaisha Toshiba | Storage device using nonvolatile flash memory and control method thereof |
US20070288683A1 (en) | 2006-06-07 | 2007-12-13 | Microsoft Corporation | Hybrid memory device with single interface |
US20080291727A1 (en) | 2007-05-23 | 2008-11-27 | Samsung Electronics Co., Ltd. | Semiconductor memory system having volatile memory and non-volatile memory that share bus, and method of controlling operation of non-volatile memory |
US20110161569A1 (en) | 2009-12-25 | 2011-06-30 | Montage Technology (Shanghai) Co., Ltd. | Memory module and method for exchanging data in memory module |
Family Cites Families (156)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2043099A (en) | 1933-10-26 | 1936-06-02 | Gen Electric | Electrical protective system |
US3562555A (en) | 1967-09-01 | 1971-02-09 | Rca Corp | Memory protecting circuit |
US3916390A (en) | 1974-12-31 | 1975-10-28 | Ibm | Dynamic memory with non-volatile back-up mode |
US4234920A (en) | 1978-11-24 | 1980-11-18 | Engineered Systems, Inc. | Power failure detection and restart system |
US4420821A (en) | 1982-02-19 | 1983-12-13 | International Business Machines Corporation | Static RAM with non-volatile back-up storage and method of operation thereof |
US4449205A (en) | 1982-02-19 | 1984-05-15 | International Business Machines Corp. | Dynamic RAM with non-volatile back-up storage and method of operation thereof |
US4607332A (en) | 1983-01-14 | 1986-08-19 | At&T Bell Laboratories | Dynamic alteration of firmware programs in Read-Only Memory based systems |
US4658204A (en) | 1986-02-07 | 1987-04-14 | Prime Computer, Inc. | Anticipatory power failure detection apparatus and method |
US4884242A (en) | 1988-05-26 | 1989-11-28 | Applied Automation, Inc. | Backup power system for dynamic memory |
US4882709A (en) | 1988-08-25 | 1989-11-21 | Integrated Device Technology, Inc. | Conditional write RAM |
US4965828A (en) | 1989-04-05 | 1990-10-23 | Quadri Corporation | Non-volatile semiconductor memory with SCRAM hold cycle prior to SCRAM-to-E2 PROM backup transfer |
GB2256735B (en) | 1991-06-12 | 1995-06-21 | Intel Corp | Non-volatile disk cache |
US6230233B1 (en) | 1991-09-13 | 2001-05-08 | Sandisk Corporation | Wear leveling techniques for flash EEPROM systems |
US5490155A (en) | 1992-10-02 | 1996-02-06 | Compaq Computer Corp. | Error correction system for n bits using error correcting code designed for fewer than n bits |
US5430742A (en) | 1992-10-14 | 1995-07-04 | Ast Research, Inc. | Memory controller with ECC and data streaming control |
KR970008188B1 (en) | 1993-04-08 | 1997-05-21 | 가부시끼가이샤 히다찌세이사꾸쇼 | Control method of flash memory and information processing apparatus using the same |
JPH0729386A (en) | 1993-07-13 | 1995-01-31 | Hitachi Ltd | Flash member and microcomputer |
US5675725A (en) | 1993-07-19 | 1997-10-07 | Cheyenne Advanced Technology Limited | Computer backup system operable with open files |
KR0130873B1 (en) | 1994-01-11 | 1998-04-20 | 호리에 유키지 | Grain tank in a combine |
US5696917A (en) | 1994-06-03 | 1997-12-09 | Intel Corporation | Method and apparatus for performing burst read operations in an asynchronous nonvolatile memory |
US5577213A (en) * | 1994-06-03 | 1996-11-19 | At&T Global Information Solutions Company | Multi-device adapter card for computer |
US5519663A (en) | 1994-09-28 | 1996-05-21 | Sci Systems, Inc. | Preservation system for volatile memory with nonvolatile backup memory |
EP0710033A3 (en) | 1994-10-28 | 1999-06-09 | Matsushita Electric Industrial Co., Ltd. | MPEG video decoder having a high bandwidth memory |
JPH08278916A (en) | 1994-11-30 | 1996-10-22 | Hitachi Ltd | Multichannel memory system, transfer information synchronizing method, and signal transfer circuit |
US5563839A (en) | 1995-03-30 | 1996-10-08 | Simtek Corporation | Semiconductor memory device having a sleep mode |
US5630096A (en) | 1995-05-10 | 1997-05-13 | Microunity Systems Engineering, Inc. | Controller for a synchronous DRAM that maximizes throughput by allowing memory requests and commands to be issued out of order |
US5619644A (en) * | 1995-09-18 | 1997-04-08 | International Business Machines Corporation | Software directed microcode state save for distributed storage controller |
US5799200A (en) | 1995-09-28 | 1998-08-25 | Emc Corporation | Power failure responsive apparatus and method having a shadow dram, a flash ROM, an auxiliary battery, and a controller |
US5914906A (en) | 1995-12-20 | 1999-06-22 | International Business Machines Corporation | Field programmable memory array |
US6199142B1 (en) | 1996-07-01 | 2001-03-06 | Sun Microsystems, Inc. | Processor/memory device with integrated CPU, main memory, and full width cache and associated method |
US5813029A (en) | 1996-07-09 | 1998-09-22 | Micron Electronics, Inc. | Upgradeable cache circuit using high speed multiplexer |
US5757712A (en) | 1996-07-12 | 1998-05-26 | International Business Machines Corporation | Memory modules with voltage regulation and level translation |
US5890192A (en) | 1996-11-05 | 1999-03-30 | Sandisk Corporation | Concurrent write of multiple chunks of data into multiple subarrays of flash EEPROM |
US5870350A (en) | 1997-05-21 | 1999-02-09 | International Business Machines Corporation | High performance, high bandwidth memory bus architecture utilizing SDRAMs |
US5991885A (en) | 1997-06-11 | 1999-11-23 | Clarinet Systems, Inc. | Method and apparatus for detecting the presence of a remote device and providing power thereto |
KR100238188B1 (en) | 1997-09-12 | 2000-01-15 | 윤종용 | Method and apparatus for generating memory clock of video controller |
US6145068A (en) | 1997-09-16 | 2000-11-07 | Phoenix Technologies Ltd. | Data transfer to a non-volatile storage medium |
US5953215A (en) | 1997-12-01 | 1999-09-14 | Karabatsos; Chris | Apparatus and method for improving computer memory speed and capacity |
US6721860B2 (en) | 1998-01-29 | 2004-04-13 | Micron Technology, Inc. | Method for bus capacitance reduction |
US6158015A (en) | 1998-03-30 | 2000-12-05 | Micron Electronics, Inc. | Apparatus for swapping, adding or removing a processor in an operating computer system |
US6216247B1 (en) | 1998-05-29 | 2001-04-10 | Intel Corporation | 32-bit mode for a 64-bit ECC capable memory subsystem |
US6269382B1 (en) * | 1998-08-31 | 2001-07-31 | Microsoft Corporation | Systems and methods for migration and recall of data from local and remote storage |
US6658507B1 (en) | 1998-08-31 | 2003-12-02 | Wistron Corporation | System and method for hot insertion of computer-related add-on cards |
US6363450B1 (en) | 1999-03-17 | 2002-03-26 | Dell Usa, L.P. | Memory riser card for a computer system |
US6336176B1 (en) | 1999-04-08 | 2002-01-01 | Micron Technology, Inc. | Memory configuration data protection |
US6487623B1 (en) | 1999-04-30 | 2002-11-26 | Compaq Information Technologies Group, L.P. | Replacement, upgrade and/or addition of hot-pluggable components in a computer system |
US7827348B2 (en) | 2000-01-06 | 2010-11-02 | Super Talent Electronics, Inc. | High performance flash memory devices (FMD) |
US6336174B1 (en) | 1999-08-09 | 2002-01-01 | Maxtor Corporation | Hardware assisted memory backup system and method |
DE10052877B4 (en) | 1999-10-21 | 2008-07-03 | Samsung Electronics Co., Ltd., Suwon | microcontroller |
US6571244B1 (en) | 1999-10-28 | 2003-05-27 | Microsoft Corporation | Run formation in large scale sorting using batched replacement selection |
JP2001166993A (en) | 1999-12-13 | 2001-06-22 | Hitachi Ltd | Memory control unit and method for controlling cache memory |
US8171204B2 (en) | 2000-01-06 | 2012-05-01 | Super Talent Electronics, Inc. | Intelligent solid-state non-volatile memory device (NVMD) system with multi-level caching of multiple channels |
US6459647B1 (en) | 2000-02-08 | 2002-10-01 | Alliance Semiconductor | Split-bank architecture for high performance SDRAMs |
US6691209B1 (en) * | 2000-05-26 | 2004-02-10 | Emc Corporation | Topological data categorization and formatting for a mass storage system |
JP3871853B2 (en) * | 2000-05-26 | 2007-01-24 | 株式会社ルネサステクノロジ | Semiconductor device and operation method thereof |
JP3871184B2 (en) * | 2000-06-12 | 2007-01-24 | シャープ株式会社 | Semiconductor memory device |
DE10032236C2 (en) | 2000-07-03 | 2002-05-16 | Infineon Technologies Ag | Circuit arrangement for switching a receiver circuit, in particular in DRAM memories |
US6769081B1 (en) | 2000-08-30 | 2004-07-27 | Sun Microsystems, Inc. | Reconfigurable built-in self-test engine for testing a reconfigurable memory |
US6487102B1 (en) | 2000-09-18 | 2002-11-26 | Intel Corporation | Memory module having buffer for isolating stacked memory devices |
JP3646303B2 (en) | 2000-12-21 | 2005-05-11 | 日本電気株式会社 | Computer system, memory management method thereof, and recording medium recording memory management program |
US7107480B1 (en) | 2000-12-22 | 2006-09-12 | Simpletech, Inc. | System and method for preventing data corruption in solid-state memory devices after a power failure |
US6662281B2 (en) | 2001-01-31 | 2003-12-09 | Hewlett-Packard Development Company, L.P. | Redundant backup device |
JP4817510B2 (en) | 2001-02-23 | 2011-11-16 | キヤノン株式会社 | Memory controller and memory control device |
US6816982B2 (en) | 2001-03-13 | 2004-11-09 | Gonen Ravid | Method of and apparatus for computer hard disk drive protection and recovery |
US6675272B2 (en) * | 2001-04-24 | 2004-01-06 | Rambus Inc. | Method and apparatus for coordinating memory operations among diversely-located memory components |
US7228383B2 (en) | 2001-06-01 | 2007-06-05 | Visto Corporation | System and method for progressive and hierarchical caching |
JP4049297B2 (en) | 2001-06-11 | 2008-02-20 | 株式会社ルネサステクノロジ | Semiconductor memory device |
TWI240864B (en) | 2001-06-13 | 2005-10-01 | Hitachi Ltd | Memory device |
JP4765222B2 (en) | 2001-08-09 | 2011-09-07 | 日本電気株式会社 | DRAM device |
US6614685B2 (en) | 2001-08-09 | 2003-09-02 | Multi Level Memory Technology | Flash memory array partitioning architectures |
JP4015835B2 (en) | 2001-10-17 | 2007-11-28 | 松下電器産業株式会社 | Semiconductor memory device |
US6771553B2 (en) | 2001-10-18 | 2004-08-03 | Micron Technology, Inc. | Low power auto-refresh circuit and method for dynamic random access memories |
US6799241B2 (en) | 2002-01-03 | 2004-09-28 | Intel Corporation | Method for dynamically adjusting a memory page closing policy |
JP3756818B2 (en) * | 2002-01-09 | 2006-03-15 | 株式会社メガチップス | Memory control circuit and control system |
JP4082913B2 (en) * | 2002-02-07 | 2008-04-30 | 株式会社ルネサステクノロジ | Memory system |
US20030158995A1 (en) | 2002-02-15 | 2003-08-21 | Ming-Hsien Lee | Method for DRAM control with adjustable page size |
US7249282B2 (en) | 2002-04-29 | 2007-07-24 | Thomson Licensing | Eeprom enable |
US6707748B2 (en) | 2002-05-07 | 2004-03-16 | Ritek Corporation | Back up power embodied non-volatile memory device |
US6810513B1 (en) | 2002-06-19 | 2004-10-26 | Altera Corporation | Method and apparatus of programmable interconnect array with configurable multiplexer |
JP4159415B2 (en) | 2002-08-23 | 2008-10-01 | エルピーダメモリ株式会社 | Memory module and memory system |
JP4499982B2 (en) * | 2002-09-11 | 2010-07-14 | 株式会社日立製作所 | Memory system |
US7111142B2 (en) | 2002-09-13 | 2006-09-19 | Seagate Technology Llc | System for quickly transferring data |
US6910635B1 (en) | 2002-10-08 | 2005-06-28 | Amkor Technology, Inc. | Die down multi-media card and method of making same |
US8412879B2 (en) * | 2002-10-28 | 2013-04-02 | Sandisk Technologies Inc. | Hybrid implementation for error correction codes within a non-volatile memory system |
US6944042B2 (en) | 2002-12-31 | 2005-09-13 | Texas Instruments Incorporated | Multiple bit memory cells and methods for reading non-volatile data |
US7089412B2 (en) | 2003-01-17 | 2006-08-08 | Wintec Industries, Inc. | Adaptive memory module |
US20040163027A1 (en) | 2003-02-18 | 2004-08-19 | Maclaren John M. | Technique for implementing chipkill in a memory system with X8 memory devices |
US20040190210A1 (en) | 2003-03-26 | 2004-09-30 | Leete Brian A. | Memory back up and content preservation |
US7234099B2 (en) | 2003-04-14 | 2007-06-19 | International Business Machines Corporation | High reliability memory module with a fault tolerant address and command bus |
JP2004355351A (en) * | 2003-05-29 | 2004-12-16 | Hitachi Ltd | Server device |
US7170315B2 (en) | 2003-07-31 | 2007-01-30 | Actel Corporation | Programmable system on a chip |
US20050044302A1 (en) | 2003-08-06 | 2005-02-24 | Pauley Robert S. | Non-standard dual in-line memory modules with more than two ranks of memory per module and multiple serial-presence-detect devices to simulate multiple modules |
US7231488B2 (en) | 2003-09-15 | 2007-06-12 | Infineon Technologies Ag | Self-refresh system and method for dynamic random access memory |
KR100574951B1 (en) | 2003-10-31 | 2006-05-02 | 삼성전자주식회사 | Memory module having improved register architecture |
US9213609B2 (en) | 2003-12-16 | 2015-12-15 | Hewlett-Packard Development Company, L.P. | Persistent memory device for backup process checkpoint states |
US7281114B2 (en) | 2003-12-26 | 2007-10-09 | Tdk Corporation | Memory controller, flash memory system, and method of controlling operation for data exchange between host system and flash memory |
KR100528482B1 (en) | 2003-12-31 | 2005-11-15 | 삼성전자주식회사 | Flash memory system capable of inputting/outputting sector dara at random |
JP4428055B2 (en) | 2004-01-06 | 2010-03-10 | ソニー株式会社 | Data communication apparatus and memory management method for data communication apparatus |
KR100606242B1 (en) | 2004-01-30 | 2006-07-31 | 삼성전자주식회사 | Volatile Memory Device for buffering between non-Volatile Memory and host, Multi-chip packaged Semiconductor Device and Apparatus for processing data using the same |
WO2005076137A1 (en) | 2004-02-05 | 2005-08-18 | Research In Motion Limited | Memory controller interface |
KR101133607B1 (en) | 2004-02-25 | 2012-04-10 | 엘지전자 주식회사 | Damper pin of Drum Washing Machine |
US7916574B1 (en) | 2004-03-05 | 2011-03-29 | Netlist, Inc. | Circuit providing load isolation and memory domain translation for memory module |
US7532537B2 (en) | 2004-03-05 | 2009-05-12 | Netlist, Inc. | Memory module with a circuit providing load isolation and memory domain translation |
US20050204091A1 (en) * | 2004-03-11 | 2005-09-15 | Kilbuck Kevin M. | Non-volatile memory with synchronous DRAM interface |
JP2007536634A (en) * | 2004-05-04 | 2007-12-13 | フィッシャー−ローズマウント・システムズ・インコーポレーテッド | Service-oriented architecture for process control systems |
DE602004010239T2 (en) | 2004-05-20 | 2008-09-25 | Stmicroelectronics S.R.L., Agrate Brianza | Improved page memory for a programmable memory device |
US7535759B2 (en) | 2004-06-04 | 2009-05-19 | Micron Technology, Inc. | Memory system with user configurable density/performance option |
US20060069896A1 (en) | 2004-09-27 | 2006-03-30 | Sigmatel, Inc. | System and method for storing data |
US20060080515A1 (en) | 2004-10-12 | 2006-04-13 | Lefthand Networks, Inc. | Non-Volatile Memory Backup for Network Storage System |
US7200021B2 (en) | 2004-12-10 | 2007-04-03 | Infineon Technologies Ag | Stacked DRAM memory chip for a dual inline memory module (DIMM) |
KR100666169B1 (en) | 2004-12-17 | 2007-01-09 | 삼성전자주식회사 | Flash memory data storing device |
US7053470B1 (en) | 2005-02-19 | 2006-05-30 | Azul Systems, Inc. | Multi-chip package having repairable embedded memories on a system chip with an EEPROM chip storing repair information |
US7493441B2 (en) | 2005-03-15 | 2009-02-17 | Dot Hill Systems Corporation | Mass storage controller with apparatus and method for extending battery backup time by selectively providing battery power to volatile memory banks not storing critical data |
KR100759427B1 (en) * | 2005-03-17 | 2007-09-20 | 삼성전자주식회사 | Hard disk drive and information processing system with reduced power consumption and data input and output method thereof |
JP4724461B2 (en) | 2005-05-17 | 2011-07-13 | Okiセミコンダクタ株式会社 | System LSI |
US20080126690A1 (en) | 2006-02-09 | 2008-05-29 | Rajan Suresh N | Memory module with memory stack |
US20060294295A1 (en) | 2005-06-24 | 2006-12-28 | Yukio Fukuzo | DRAM chip device well-communicated with flash memory chip and multi-chip package comprising such a device |
US7464225B2 (en) | 2005-09-26 | 2008-12-09 | Rambus Inc. | Memory module including a plurality of integrated circuit memory devices and a plurality of buffer devices in a matrix topology |
US20070136523A1 (en) * | 2005-12-08 | 2007-06-14 | Bonella Randy M | Advanced dynamic disk memory module special operations |
US7409491B2 (en) | 2005-12-14 | 2008-08-05 | Sun Microsystems, Inc. | System memory board subsystem using DRAM with stacked dedicated high speed point to point links |
US7519754B2 (en) * | 2005-12-28 | 2009-04-14 | Silicon Storage Technology, Inc. | Hard disk drive cache memory and playback device |
KR20070076849A (en) * | 2006-01-20 | 2007-07-25 | 삼성전자주식회사 | Apparatus and method for accomplishing copy-back operation in memory card |
JP4780304B2 (en) | 2006-02-13 | 2011-09-28 | 株式会社メガチップス | Semiconductor memory and data access method |
US7421552B2 (en) | 2006-03-17 | 2008-09-02 | Emc Corporation | Techniques for managing data within a data storage system utilizing a flash-based memory vault |
US7653778B2 (en) | 2006-05-08 | 2010-01-26 | Siliconsystems, Inc. | Systems and methods for measuring the useful life of solid-state storage devices |
US7464240B2 (en) | 2006-05-23 | 2008-12-09 | Data Ram, Inc. | Hybrid solid state disk drive with controller |
US8407395B2 (en) | 2006-08-22 | 2013-03-26 | Mosaid Technologies Incorporated | Scalable memory system |
JP4437489B2 (en) | 2006-10-25 | 2010-03-24 | 株式会社日立製作所 | Storage system having volatile cache memory and nonvolatile memory |
US20080126624A1 (en) * | 2006-11-27 | 2008-05-29 | Edoardo Prete | Memory buffer and method for buffering data |
KR101533120B1 (en) | 2006-12-14 | 2015-07-01 | 램버스 인코포레이티드 | Multi-die memory device |
US7554855B2 (en) * | 2006-12-20 | 2009-06-30 | Mosaid Technologies Incorporated | Hybrid solid-state memory system having volatile and non-volatile memory |
US20080189479A1 (en) * | 2007-02-02 | 2008-08-07 | Sigmatel, Inc. | Device, system and method for controlling memory operations |
US7752373B2 (en) | 2007-02-09 | 2010-07-06 | Sigmatel, Inc. | System and method for controlling memory operations |
US8427891B2 (en) * | 2007-04-17 | 2013-04-23 | Rambus Inc. | Hybrid volatile and non-volatile memory device with a shared interface circuit |
US8904098B2 (en) | 2007-06-01 | 2014-12-02 | Netlist, Inc. | Redundant backup using non-volatile memory |
US8874831B2 (en) * | 2007-06-01 | 2014-10-28 | Netlist, Inc. | Flash-DRAM hybrid memory module |
US8301833B1 (en) | 2007-06-01 | 2012-10-30 | Netlist, Inc. | Non-volatile memory module |
US7952179B2 (en) | 2007-06-28 | 2011-05-31 | Sandisk Corporation | Semiconductor package having through holes for molding back side of package |
US8200885B2 (en) | 2007-07-25 | 2012-06-12 | Agiga Tech Inc. | Hybrid memory system with backup power source and multiple backup an restore methodology |
US7865679B2 (en) | 2007-07-25 | 2011-01-04 | AgigA Tech Inc., 12700 | Power interrupt recovery in a hybrid memory subsystem |
US8001434B1 (en) | 2008-04-14 | 2011-08-16 | Netlist, Inc. | Memory board with self-testing capability |
US20090313416A1 (en) * | 2008-06-16 | 2009-12-17 | George Wayne Nation | Computer main memory incorporating volatile and non-volatile memory |
EP2141590A1 (en) * | 2008-06-26 | 2010-01-06 | Axalto S.A. | Method of managing data in a portable electronic device having a plurality of controllers |
US8478928B2 (en) | 2009-04-23 | 2013-07-02 | Samsung Electronics Co., Ltd. | Data storage device and information processing system incorporating data storage device |
KR101606880B1 (en) | 2009-06-22 | 2016-03-28 | 삼성전자주식회사 | Data storage system and channel driving method thereof |
US8266501B2 (en) | 2009-09-29 | 2012-09-11 | Micron Technology, Inc. | Stripe based memory operation |
US8898324B2 (en) * | 2010-06-24 | 2014-11-25 | International Business Machines Corporation | Data access management in a hybrid memory server |
US8418026B2 (en) | 2010-10-27 | 2013-04-09 | Sandisk Technologies Inc. | Hybrid error correction coding to address uncorrectable errors |
US8806245B2 (en) | 2010-11-04 | 2014-08-12 | Apple Inc. | Memory read timing margin adjustment for a plurality of memory arrays according to predefined delay tables |
US8713379B2 (en) | 2011-02-08 | 2014-04-29 | Diablo Technologies Inc. | System and method of interfacing co-processors and input/output devices via a main memory system |
KR101800445B1 (en) | 2011-05-09 | 2017-12-21 | 삼성전자주식회사 | Memory controller and operating method of memory controller |
US8792273B2 (en) | 2011-06-13 | 2014-07-29 | SMART Storage Systems, Inc. | Data storage system with power cycle management and method of operation thereof |
CN102411548B (en) | 2011-10-27 | 2014-09-10 | 忆正存储技术(武汉)有限公司 | Flash memory controller and method for transmitting data among flash memories |
CN104272697B (en) * | 2012-05-02 | 2018-11-02 | 英特尔公司 | For using multiple media access controllers that data are grouped with the method, equipment and device of processing |
US20140032820A1 (en) | 2012-07-25 | 2014-01-30 | Akinori Harasawa | Data storage apparatus, memory control method and electronic device with data storage apparatus |
US9436600B2 (en) | 2013-06-11 | 2016-09-06 | Svic No. 28 New Technology Business Investment L.L.P. | Non-volatile memory storage for multi-channel memory system |
-
2012
- 2012-07-26 US US13/559,476 patent/US8874831B2/en not_active Expired - Fee Related
- 2012-07-28 EP EP21200871.8A patent/EP3985518A1/en active Pending
- 2012-07-28 EP EP17191878.2A patent/EP3293638B1/en active Active
- 2012-07-28 PL PL17191878T patent/PL3293638T3/en unknown
- 2012-07-28 CN CN201280047758.XA patent/CN103890688B/en active Active
- 2012-07-28 KR KR1020147005608A patent/KR20140063660A/en not_active Application Discontinuation
- 2012-07-28 CN CN201710824058.1A patent/CN107656700B/en not_active Expired - Fee Related
- 2012-07-28 EP EP12817751.6A patent/EP2737383B1/en active Active
- 2012-07-28 WO PCT/US2012/048750 patent/WO2013016723A2/en active Application Filing
-
2014
- 2014-09-17 US US14/489,269 patent/US9158684B2/en active Active
-
2015
- 2015-08-31 US US14/840,865 patent/US9928186B2/en active Active
-
2018
- 2018-03-23 US US15/934,416 patent/US20190004985A1/en not_active Abandoned
-
2020
- 2020-12-30 US US17/138,766 patent/US11016918B2/en active Active
-
2021
- 2021-05-24 US US17/328,019 patent/US11232054B2/en active Active
-
2022
- 2022-01-24 US US17/582,797 patent/US20220222191A1/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070147115A1 (en) | 2005-12-28 | 2007-06-28 | Fong-Long Lin | Unified memory and controller |
US20070255898A1 (en) | 2006-04-28 | 2007-11-01 | Kabushiki Kaisha Toshiba | Storage device using nonvolatile flash memory and control method thereof |
US20070288683A1 (en) | 2006-06-07 | 2007-12-13 | Microsoft Corporation | Hybrid memory device with single interface |
US20080291727A1 (en) | 2007-05-23 | 2008-11-27 | Samsung Electronics Co., Ltd. | Semiconductor memory system having volatile memory and non-volatile memory that share bus, and method of controlling operation of non-volatile memory |
US20110161569A1 (en) | 2009-12-25 | 2011-06-30 | Montage Technology (Shanghai) Co., Ltd. | Memory module and method for exchanging data in memory module |
Cited By (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9921762B2 (en) | 2007-06-01 | 2018-03-20 | Netlist, Inc. | Redundant backup using non-volatile memory |
US8880791B2 (en) | 2007-06-01 | 2014-11-04 | Netlist, Inc. | Isolation switching for backup of registered memory |
US8904098B2 (en) | 2007-06-01 | 2014-12-02 | Netlist, Inc. | Redundant backup using non-volatile memory |
US8904099B2 (en) | 2007-06-01 | 2014-12-02 | Netlist, Inc. | Isolation switching for backup memory |
US11232054B2 (en) | 2007-06-01 | 2022-01-25 | Netlist, Inc. | Flash-dram hybrid memory module |
US11016918B2 (en) | 2007-06-01 | 2021-05-25 | Netlist, Inc. | Flash-DRAM hybrid memory module |
US11561715B2 (en) | 2011-07-28 | 2023-01-24 | Netlist, Inc. | Method and apparatus for presearching stored data |
US10838646B2 (en) | 2011-07-28 | 2020-11-17 | Netlist, Inc. | Method and apparatus for presearching stored data |
US10380022B2 (en) | 2011-07-28 | 2019-08-13 | Netlist, Inc. | Hybrid memory module and system and method of operating the same |
US10198350B2 (en) | 2011-07-28 | 2019-02-05 | Netlist, Inc. | Memory module having volatile and non-volatile memory subsystems and method of operation |
US11048410B2 (en) | 2011-08-24 | 2021-06-29 | Rambus Inc. | Distributed procedure execution and file systems on a memory interface |
US10209922B2 (en) | 2011-08-24 | 2019-02-19 | Rambus Inc. | Communication via a memory interface |
US9275733B2 (en) | 2011-08-24 | 2016-03-01 | Rambus Inc. | Methods and systems for mapping a peripheral function onto a legacy memory interface |
US9921751B2 (en) | 2011-08-24 | 2018-03-20 | Rambus Inc. | Methods and systems for mapping a peripheral function onto a legacy memory interface |
US9645746B2 (en) | 2012-12-21 | 2017-05-09 | Dell Products L.P. | Systems and methods for support of non-volatile memory on a DDR memory channel |
US20140181364A1 (en) * | 2012-12-21 | 2014-06-26 | Dell Products L.P. | Systems And Methods For Support Of Non-Volatile Memory On A DDR Memory Channel |
US9280497B2 (en) * | 2012-12-21 | 2016-03-08 | Dell Products Lp | Systems and methods for support of non-volatile memory on a DDR memory channel |
US11200120B2 (en) | 2013-03-15 | 2021-12-14 | Netlist, Inc. | Hybrid memory system with configurable error thresholds and failure analysis capability |
US10372551B2 (en) | 2013-03-15 | 2019-08-06 | Netlist, Inc. | Hybrid memory system with configurable error thresholds and failure analysis capability |
US9996284B2 (en) | 2013-06-11 | 2018-06-12 | Netlist, Inc. | Non-volatile memory storage for multi-channel memory system |
US11314422B2 (en) | 2013-06-11 | 2022-04-26 | Netlist, Inc. | Non-volatile memory storage for multi-channel memory system |
US10719246B2 (en) | 2013-06-11 | 2020-07-21 | Netlist, Inc. | Non-volatile memory storage for multi-channel memory system |
US9436563B2 (en) | 2013-10-01 | 2016-09-06 | Globalfoundries Inc. | Memory system for mirroring data |
US9430344B2 (en) | 2013-10-01 | 2016-08-30 | Globalfoundries Inc. | Memory system for mirroring data |
US9367390B2 (en) | 2013-11-01 | 2016-06-14 | Phison Electronics Corp. | Memory controlling method, memory storage device and memory controlling circuit unit |
US10248328B2 (en) | 2013-11-07 | 2019-04-02 | Netlist, Inc. | Direct data move between DRAM and storage on a memory module |
CN104636267A (en) * | 2013-11-11 | 2015-05-20 | 群联电子股份有限公司 | Storage control method, storage storing device and storage control circuit unit |
CN104636267B (en) * | 2013-11-11 | 2018-01-12 | 群联电子股份有限公司 | Memory control methods, memory storage apparatus and memorizer control circuit unit |
CN105408875A (en) * | 2014-02-23 | 2016-03-16 | 拉姆伯斯公司 | Distributed procedure execution and file systems on a memory interface |
CN105408875B (en) * | 2014-02-23 | 2019-06-21 | 拉姆伯斯公司 | Distributed process on memory interface executes and file system |
EP2911065A1 (en) * | 2014-02-23 | 2015-08-26 | Rambus Inc. | Distributed procedure execution and file systems on a memory interface |
WO2015155103A1 (en) * | 2014-04-08 | 2015-10-15 | Fujitsu Technology Solutions Intellectual Property Gmbh | Method for improved access to a main memory of a computer system, corresponding computer system and computer program product |
US10248329B2 (en) | 2014-04-08 | 2019-04-02 | Fujitsu Technology Solutions Intellectual Property Gmbh | Method of improving access to a main memory of a computer system, a corresponding computer system and a computer program product |
US9720604B2 (en) | 2015-08-06 | 2017-08-01 | Sandisk Technologies Llc | Block storage protocol to RAM bypass |
US10031674B2 (en) | 2015-10-07 | 2018-07-24 | Samsung Electronics Co., Ltd. | DIMM SSD addressing performance techniques |
US10503657B2 (en) | 2015-10-07 | 2019-12-10 | Samsung Electronics Co., Ltd. | DIMM SSD Addressing performance techniques |
US9880778B2 (en) | 2015-11-09 | 2018-01-30 | Google Inc. | Memory devices and methods |
US11222671B2 (en) | 2019-06-20 | 2022-01-11 | Samsung Electronics Co., Ltd. | Memory device, method of operating the memory device, memory module, and method of operating the memory module |
EP3754512A1 (en) * | 2019-06-20 | 2020-12-23 | Samsung Electronics Co., Ltd. | Memory device, method of operating the memory device, memory module, and method of operating the memory module |
US11694730B2 (en) | 2019-06-20 | 2023-07-04 | Samsung Electronics Co., Ltd. | Memory device, method of operating the memory device, memory module, and method of operating the memory module |
CN114902197A (en) * | 2019-12-30 | 2022-08-12 | 超威半导体公司 | Command replay for non-volatile dual in-line memory modules |
CN114902197B (en) * | 2019-12-30 | 2023-06-13 | 超威半导体公司 | Command replay for non-volatile dual inline memory modules |
EP4036916A1 (en) * | 2021-01-29 | 2022-08-03 | Commissariat à l'Energie Atomique et aux Energies Alternatives | Device comprising a non-volatile memory circuit |
FR3119483A1 (en) * | 2021-01-29 | 2022-08-05 | Commissariat A L'energie Atomique Et Aux Energies Alternatives | Device comprising a non-volatile memory circuit |
US11875848B2 (en) | 2021-01-29 | 2024-01-16 | Commissariat à l'Energie Atomique et aux Energies Alternatives | Buffer memory adapted to implment calculations having operands as data |
US11586266B1 (en) | 2021-07-28 | 2023-02-21 | International Business Machines Corporation | Persistent power enabled on-chip data processor |
Also Published As
Publication number | Publication date |
---|---|
EP2737383B1 (en) | 2017-09-20 |
EP3293638B1 (en) | 2021-10-06 |
US20190004985A1 (en) | 2019-01-03 |
CN107656700A (en) | 2018-02-02 |
EP3985518A1 (en) | 2022-04-20 |
US20130086309A1 (en) | 2013-04-04 |
CN103890688A (en) | 2014-06-25 |
US8874831B2 (en) | 2014-10-28 |
US20210124701A1 (en) | 2021-04-29 |
US20220222191A1 (en) | 2022-07-14 |
US11232054B2 (en) | 2022-01-25 |
US11016918B2 (en) | 2021-05-25 |
US9928186B2 (en) | 2018-03-27 |
US20210279194A1 (en) | 2021-09-09 |
PL3293638T3 (en) | 2022-03-28 |
EP3293638A1 (en) | 2018-03-14 |
CN103890688B (en) | 2017-10-13 |
CN107656700B (en) | 2020-09-01 |
EP2737383A2 (en) | 2014-06-04 |
US20160196223A1 (en) | 2016-07-07 |
KR20140063660A (en) | 2014-05-27 |
US20150242313A1 (en) | 2015-08-27 |
WO2013016723A3 (en) | 2014-05-08 |
US9158684B2 (en) | 2015-10-13 |
EP2737383A4 (en) | 2015-07-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9928186B2 (en) | Flash-DRAM hybrid memory module | |
CN109508152B (en) | Multi-level scheme for logical storage management | |
CN115362436A (en) | Quasi-volatile system-level memory | |
US20170147233A1 (en) | Interface architecture for storage devices | |
JP7036925B2 (en) | Memory controller considering cache control | |
WO2020227294A1 (en) | Timed data transfer between a host system and a memory sub-system | |
CN111684432B (en) | Synchronous memory bus access to storage media | |
EP2911065B1 (en) | Distributed procedure execution and file systems on a memory interface | |
WO2020242750A1 (en) | Predictive data transfer based on availability of media units in memory sub-systems | |
KR20120104954A (en) | Hybrid system architecture for random access memory | |
US8683161B2 (en) | Method and apparatus for increasing file copy performance on solid state mass storage devices | |
CN117296033A (en) | Adjustable timer assembly for semiconductor device | |
EP4375840A1 (en) | Memory controller, electronic system including the same and method of controlling memory access | |
EP4379524A1 (en) | Storage device and storage system for direct storage | |
US11995327B2 (en) | Data storage device and method for adaptive host memory buffer allocation based on virtual function prioritization | |
WO2024091764A1 (en) | Data storage device and method for reducing flush latency | |
KR20240076574A (en) | Memory controller, electronic system including the same and method of controlling memory access |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12817751 Country of ref document: EP Kind code of ref document: A2 |
|
ENP | Entry into the national phase |
Ref document number: 20147005608 Country of ref document: KR Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2012817751 Country of ref document: EP |