US 9,436,600 B2Grant
Non-volatile memory storage for multi-channel memory system
Issue Date:2016-09-06
•25 Claims
•6 Drawing Sheets
Abstract
A memory system that has a multi-channel volatile memory subsystem is coupled to a non-volatile memory subsystem to provide independent, configurable backup of data. The volatile memory subsystem has one or more main memory modules that use a form of volatile memory such as DRAM memory, for which the NV subsystem provides selective persistent backup. The main memory modules are dual in-line memory modules or DIMMs using DDR SDRAM memory devices. The non-volatile memory subsystem (NV backup) includes an NV controller and non-volatile memory NVM. The NV backup can also include a memory cache to aid with handling and storage of data. In certain embodiments, the NV controller and the non-volatile memory are coupled to the one or more DIMM channels of the main memory via associated signal lines. Such signal lines can be, for example, traces on a motherboard, and may include one or more signal buses for conveying data, address, and/or control signals. The NV controller and the non-volatile memory can be mounted on the motherboard.
Metadata
Assignee
- SVIC No. 28 New Technology Business Investment L.L.P.
Inventor
- Hyun Lee
Application Information
Application Number:US 14/302,292
Filing Date:2014-06-11
Priority Date:2013-06-11
Art Unit:2138
Classifications
IPC:
G06F12/02G06F12/08
Field of Search:
G06F 12/0246G06F 12/0868G06F 2212/213
Patent Drawings (6 sheets)
Description
PRIORITY CLAIM
[0001] Applicants hereby claim the benefit of U.S. provisional patent application Ser. No. 61/833,848 filed Jun. 11, 2013, the disclosure of which is hereby incorporated herein by reference as if set forth fully herein.
TECHNICAL FIELD
[0002] 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 volatile and non-volatile memories.
BACKGROUND
[0003] Memory devices used for computer data storage can be classified into two categories: volatile memory and non-volatile memory. For volatile memory, such as DRAM, maintaining device states and preserving stored information requires a constant supply of power. Any interruption of power will result in loss of stored information. Preventing such loss requires the use of back up batteries or other energy storage devices, which may be expensive, bulky and difficult to maintain.
[0004] Non-volatile memory, by comparison, does not need power to maintain its information content. However, non-volatile memory may not be as economical or efficient or fast as volatile memory, and has accordingly not replaced volatile memory as a viable data storage alternative. Nevertheless, in certain circumstances, it can be useful to back up volatile memory with non-volatile memory, for example to avoid catastrophic data loss in the event of power outage. Data thus backed up in non-volatile memory is preserved despite power disruptions, and can be copied back into the volatile memory when normal operation resumes.
[0005] It may be inefficient or impractical to back up all volatile memory data all the time using non-volatile memory. More practical approaches rely on selective storage, for example of critical data only; or on detecting a potential power loss in advance and then backing up any critical data, or data that is intermediate to a currently-executing process, while some power still remains, or while a small, economical amount of power can be provided.
[0006] There are many types of non-volatile memory. One common type is termed “flash” memory, and relies on charge storage in gates of floating-gate transistors. The charge storage is persistent and interruptions in power have no short term impact on the information content, endowing the memory with its non-volatile character. Individual flash memory cells, comprised of one or more floating-gate transistors, can be configured to store a single binary value (single-level cells, or SLCs), or multiple binary values (multi-level cells, or MLCs). The flash memory chip can comprise millions, or billions, of such cells, and is currently available in numerous formats, such as 2 gigabit (Gb), 4 Gb, 8 Gb, and so on. The chips themselves can be combined in various architectures in a memory module, to be accessed by way of a flash memory controller that selectively issues memory accesses commands using control and address signals to the flash memory chips for retrieval or storage of data based on the needs of the host device.
Overview
[0007] A memory system that has a volatile memory subsystem is coupled to a non-volatile memory subsystem (or “non-volatile memory subsystem” or “NV backup” or “NV backup subsystem”) to provide independent, configurable backup or storage of data. In certain embodiments, the volatile memory subsystem has one or more main memory modules that may be in the form of volatile memory such as DRAM memory, for which the NV backup subsystem provides selective persistent backup. In one embodiment, the main memory modules are dual in-line memory modules or DIMMs using DDR SDRAM memory devices. The NV backup subsystem includes an NV controller and non-volatile memory NVM (e.g., FLASH). In certain embodiments, the NV backup also includes a memory cache, such a DRAM, to aid with handling and storage of data. In certain embodiments, the NV controller and the non-volatile memory are not mounted on any of the one or more DIMM physical slots or locations, but are instead coupled to the one or more DIMM channels of the main memory via associated signal lines. Such signal lines can be, for example, traces on a motherboard, and may include one or more signal buses for conveying data, address, and/or control signals. The NV controller and the non-volatile memory can be mounted on the motherboard.
[0008] Described herein is a method for performing memory access operations in a computer system having a memory controller includes coupling the memory controller to a first memory channel via a first set of data, address and control signal lines, coupling the memory controller to a second memory channel via a second set of data, address and control signal lines, wherein the computer system is operable to have independent access to the first memory channel and the second memory channel via the memory controller, coupling a nonvolatile memory subsystem to the first memory channel and to the second memory channel, the nonvolatile memory subsystem including an NV (non-volatile) controller and at least one nonvolatile memory element, using the NV controller to monitor each of the first and second memory channels to detect one or more memory access operations to at least one predetermined address range, and capturing a copy of data associated with the one or more memory access operations.
[0009] Also described herein is a method for performing memory access operations in a computer system having first and second volatile memory modules, the computer system including a memory controller configured to independently access the first and second volatile memory modules via respective first and second memory channels, the first volatile memory module being coupled to the first memory channel via a first set of data, address and control signal lines, the second volatile memory module being coupled to the second memory channel via a second set of data, address and control signal lines. The method includes monitoring, using at least one NV (non-volatile) controller, the first and second memory channels to detect memory access operations, capturing a copy of data associated with a first memory access operation to a first address range using a first one of the at least one NV controller upon detection of the first memory access operation, wherein the first memory access operation allows data to be communicated between the memory controller and the first volatile memory module using the first memory channel, and capturing a copy of data associated with a second memory access operation to a second address range using a second one of the at least one NV controller upon detection of the second memory access operation, wherein the second memory access operation allows data to be communicated between the memory controller and the second volatile memory module using the second memory channel.
[0010] Also described herein is a method for operating a nonvolatile memory subsystem having an NV (non-volatile) controller and one or more nonvolatile memory modules, The method includes using at least two memory channels to couple a host computer system to a volatile memory subsystem, wherein the at least two memory channels are independently accessible by the host computer system, coupling the NV controller to the one or more nonvolatile memory modules, coupling the NV controller to the at least two memory channels, wherein each one of the at least two memory channels includes address, data and control signals, monitoring each one of the at least two memory channels for the occurrence of one or more memory access operations to the volatile memory subsystem, and capturing a copy of data associated with a first memory access operation of the one or more memory access operations.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] 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.
[0012] In the drawings:
[0013] FIG. 1 is a block diagram of a memory system in which a memory control module is coupled to a single-channel volatile memory subsystem;
[0014] FIG. 2 is a block diagram of a memory system in which a memory control module is coupled to a volatile memory subsystem in a multi-channel arrangement and in which an NV memory subsystem includes a plurality of NV controllers each coupled to a respective memory module channel using a separate respective signal bus;
[0015] FIG. 3 is a block diagram of a memory system in which a memory control module is coupled to a volatile memory subsystem in a multi-channel arrangement, and in which an NV memory subsystem includes an NV controller coupled to one or more channels of the memory module channels using a common signal bus;
[0016] FIG. 4 is a block diagram of a memory system in which the memory control module is coupled to the volatile memory subsystem in a multi-channel arrangement, and in which an NV chip select signal line NV-CS is used to communicate an NV chip select signal between the memory control module and an NV controller; and
[0017] FIG. 5 is a block diagram of a memory system in which the memory control module is coupled to the volatile memory subsystem in a multi-channel arrangement and in which the NV memory subsystem includes an NV controller coupled to one or more channels of the memory module using one or more cache memories.
DESCRIPTION OF EXAMPLE EMBODIMENTS
[0018] Example embodiments are described herein in the context of non-volatile memory storage for a multichannel memory system. 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.
[0019] 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.
[0020] 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.
[0021] FIG. 1 illustrates a memory system 100 in which a memory control module 102 is coupled to a single-channel volatile memory subsystem 103 via a single memory channel chs 109. The coupling is effected by way of a main interface 111 for delivery of the data, address and/or control signals. In certain embodiments, the interface 111 can be one or more of an electrical connector, printed circuit board with a plurality of conduits or copper traces, controller, microprocessor, logic device, integrated circuit, programmable logic device, register, switch, or load reducing circuit, or combinations thereof. The volatile memory subsystem 103 can have one or more volatile memory modules 107, for example DIMMs (dual in-line memory modules), connected on the single channel chs 109 for communication of data, address and control signals between memory control module 102 and the one or more memory modules 107. Memory control module 102 may be a CPU, a processor, a memory control system, or a memory controller and may be part of a host computer system (not shown). The interface 111 can be integrated within the memory control module 102. For example the interface 111 can be a portion of a memory controller or a CPU of a computer system.
[0022] Memory system 100 also includes a NV memory subsystem 105 according to one embodiment. As shown in FIG. 1 , the NV subsystem 105 has at least one NV controller 104, non-volatile memory NVM (e.g., a FLASH memory device or a memory module including flash memory devices) 108, and a common signal bus 106 that is coupled to the interface 111. In one embodiment, the common signal bus 106 is external to the NV memory subsystem 105 and is used to couple the NV memory subsystem 105 to the memory control module 102 or to the one or more memory modules 107. In one embodiment, the NV controller 104 communicates data, address, and/or control signals via the interface 111 between the NVM 108 and any memory module of the one or more memory modules 107, and the memory control module 102. In one embodiment, the one or more memory modules 107 populate one or more DIMM sockets on a motherboard (not shown), and the common signal bus 106 comprises board traces in one or more conductive layers of a motherboard (not shown). In certain embodiments, the NVM 108 comprises one or more of a non-volatile memory array, at least one non-volatile memory element or die, at least one packaged non-volatile memory device, at least one module comprising non-volatile memory, or combinations thereof. Types of non-volatile memory compatible with NVM 108 include, but are not limited to, flash memory elements such as multi-level cell (MLC), NOR, ONE-NAND, and NAND flash memory.
[0023] FIG. 2 illustrates a memory system 200 in which a memory control module 202 is coupled to a volatile memory subsystem 203 in a multi-channel arrangement ch1-chn 209. Each of the channels ch1-chn 209 can be coupled to one or more volatile memory modules, for example DIMMs, connected in the manner of FIG. 1 above and not shown in FIG. 2 for clarity. Each of the channels ch1-chn 209 is independently and individually-addressable by the memory control module 202, and is used to communicate data, address and control signals between the memory control module 202 and the one or more memory modules (DIMMs) of the volatile memory subsystem 203.
[0024] Also shown coupled to the memory control module 202 is NV memory subsystem 205 according to one embodiment. NV memory subsystem 205 includes a plurality of NV controllers 2041 through 204n each coupled to a respective memory module channel ch1-chn 209 via an interface 211 using a separate respective signal bus 2061 through 206n. The NV bakup subsystem 205 also includes nonvolatile memory NVM 2081 through 208n, each coupled to a respective NV controller 2041 through 204n. In one embodiment, each separate signal bus 2061-206n is external to the NV memory subsystem 205 and is used to communicate data, address, and/or control signals between the NV controller 204 and a respective memory module coupled to any memory module channel of the memory module channel ch1-chn 209. In one embodiment, the coupling between the memory control module 202, the volatile memory subsystem 203, and the NV memory subsystem 205 is effected by way of the interface 211 for delivery of data, address and/or control signals via a respective memory channel of the memory module channel ch1-chn 209 and a respective one or more signal bus of the signal bus 2061-206n.
[0025] In certain embodiments, each of NVM 2081 through 208n comprises one or more of a non-volatile memory array, at least one non-volatile memory element or die, at least one packaged non-volatile memory device, at least one module comprising non-volatile memory, a FLASH memory device, or a memory module including one or more flash memory devices, or a combination thereof. Types of non-volatile memory compatible with each of NVM 2081 through 208n include, but are not limited to, flash memory elements such as multi-level cell (MLC), NOR, ONE-NAND, and NAND flash memory.
[0026] In certain embodiments, the interface 211 can be one or more of an electrical connector, a printed circuit board with a plurality of conduits or copper traces, controller, microprocessor, logic device, integrated circuit, programmable logic device, register, switch, and load reducing circuit. In one embodiment, each separate signal bus 2061-206n comprises board traces in one or more conductive layers of a motherboard (not shown). In certain embodiments, memory control module 202 comprises a CPU, a processor, a memory control subsystem, or a memory controller. In certain embodiments, memory control module 202 may be part of a host computer system (not shown). In certain embodiments, the interface 211 can be integrated with the memory control module 202, a CPU, or a memory controller to form a single component, an integrated circuit, or a memory system for example the interface 211 can be a portion of a memory controller or a CPU of a computer system.
[0027] In certain embodiments, the interface 211 includes logic (i) to generate, process, or format one or more of data signals, address signals and control signals, and (ii) to selectively transmit data signals, address signals and/or control signals between two or more of the memory control module 202, the volatile memory subsystem 203, and the NV memory subsystem 205 using one or more channels of the memory module channels ch1-chn 209 and a respective one or more signal bus of the signal bus 2061-206n. In certain embodiments, the interface 211 is integrated with the memory control module 202, a CPU, or a memory controller to form a single component, an integrated circuit, or a memory system.
[0028] In certain embodiments, the interface 211 snoops a first set of data, address, and control signals from one or more of channels ch1-chn 209, and transmits a second set of data, address, and control signals via one or more of the signal buses 2061-206n. The second set of data, address, and control signals is generated based on the first set of data, address, and control signals. In one embodiment, the second set of data, address, and control signals is a copy of the first set of data, address, and control signals. In one embodiment, one or more of data signals, address signals, and control signals of the first set of data, address, and control signals are processed by interface 211 before being transmitted as part of the second set of data, address, and control signals. For example, the interface 211 can include a serializer/deserializer (or SERDES) (not shown) in order to receive, process, format, and transmit data signals, address signals, or control signals using a serial interface or a parallel interface. In certain embodiments, the memory module channels ch1-chn 209 include a parallel interface, while the signal bus 2061-206n include one or more of a serial interface and a parallel interface. In certain embodiments, the interface 211 is operable to process, replicate, regenerate, modify, delay, format, compress, error check, or generate one or more of data signals, address signals, and control signals of the second set of data, address, and control signals based on one or more of data signals, address signals, and control signals of the first set of data, address, and control signals. In certain embodiments, the interface 211 is coupled to the NV controller 204 via a single common signal bus instead of the separated signal bus 2061-206n, wherein the interface 211 manages and control communication of data, address, and/or control signals from/to the NV memory subsystem 205 to/from at least one of the memory control module 205 and one or more memory modules that are coupled to one or more of channels ch1-chn 209.
[0029] FIG. 3 illustrates a memory system 300 in which the memory control module 202 is coupled to the volatile memory subsystem 203 in the multi-channel arrangement ch1-chn 209 via the interface 211 as shown in FIG. 2 and as described above. Also shown coupled to the memory control module 202 is NV memory subsystem 305 according to one embodiment. The NV memory subsystem 305 includes NV controller 304 coupled to one or more channels of the memory module channels ch1-chn 209 via the interface 211 using a common signal bus 306. The NV memory subsystem 305 also includes nonvolatile memory NVM 308 which is coupled to the NV controller 304. In certain embodiments, the NV controller 304 comprises a plurality of NV controllers each of which may be used to independently control data communication between the NVM 308 and at least one of the memory control module 202 and the volatile memory subsystem 203.
[0030] In certain embodiments, the NVM 308 comprises one or more of a non-volatile memory array, at least one non-volatile memory element or die, at least one packaged non-volatile memory device, at least one module comprising non-volatile memory, a FLASH memory device, or a memory module including one or more flash memory devices, or combinations thereof. Types of non-volatile memory compatible with NVM 308 include, but are not limited to, flash memory elements such as multi-level cell (MLC), NOR, ONE-NAND, and NAND flash memory.
[0031] In one embodiment, the common signal bus 306 is external to the NV memory subsystem 305 and is used to communicate data, address, and/or control signals between the NV controller 304 and a memory module coupled to any memory module channel of the memory module channel ch1-chn 209. In one embodiment, the coupling between the memory control module 202, the volatile memory subsystem 203, and the NV memory subsystem 305 is effected by way of the interface 211 for delivery of data, address and/or control signals via a respective memory channel of the memory module channel ch1-chn 209, or via the common signal bus 306.
[0032] In one embodiment, the common signal bus 306 comprises separate signal bus 3061-306n (not shown) and each such signal bus of the signal bus 3061-306n is operable to deliver data, address, and control signals between a respective channel of the memory module channel ch1-chn 209 and the NV controller 304, in a similar manner as shown in FIG. 2 and as described above. The NV controller 304 is operable to receive and separately control each signal bus of the signal bus 3061-306n. The NV controller 304 in turn controls the transfer or storage of data from/to the NVM 308. In one embodiment, each of the signal buses 3061-306n is individually-addressable by the memory control module 202 or the NV controller 304, and is independently used to communicate data, address and control signals between the NV controller 304 and at least one of the memory control module 202 and one or more memory modules (DIMMs) (not shown) of the volatile memory subsystem 203.
[0033] In certain embodiments, the interface 211 is operable (i) to communicates one or more of data signals, address signals and control signals with the memory control module 202, (ii) to generate, process, or format one or more of data signals, address signals and control signals based at least in part on received data signals, address signals or control signals from the memory control module 202, the volatile memory subsystem 203, or the NV subsystem 305, and (iii) to selectively transmit one or more of data signals, address signals, and control signals to one or more of the memory control module 202, the volatile memory subsystem 203, and the NV subsystem 305 using at least one of a channel of the memory module channel ch1-chn 209, the common signal bus 306, and a signal bus of the signal bus 3061-306n. In certain embodiments, the interface 211 is integrated with the memory control module 202, a CPU, or a memory controller to form a single component, an integrated circuit, or a memory system.
[0034] In certain embodiments, the interface 211 snoops at least one of data signals, address signals, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits the at least one of data signals, address signals, and control signals to the NV controller 304 via the common signal bus 306. In certain embodiment, the interface 211 generates at least one of data signals, address signals, and control signals in response to at least one of data signals, address signals, and control signals received from any one of the memory control module 202, the volatile memory subsystem 203, or the NV subsystem 305. The interface 211 transmits the generated at least one of data signals, address signals, and control signals to the NV controller 304 via the common signal bus 306.
[0035] In certain embodiments, the interface 211 snoops a first set of data, address, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits a second set of data, address, and control signals via the common signal bus 306. The second set of data, address, and control signals is generated based on the first set of data, address, and control signals. In one embodiment, the second set of data, address, and control signals correspond to a copy of the first set of data, address, and control signals. In one embodiment, one or more of data signals, address signals, and control signals of the first set of data, address, and control signals are processed by interface 211 before being transmitted as part of the second set of data, address, and control signals. For example, the interface 211 includes a serializer and a deserializer (or SERDES) in order to receive, process, format, and transmit data signals, address signals, or control signals using a serial interface or a parallel interface. In certain embodiments, the memory module channel ch1-chn 209 include a parallel interface, while the common signal bus 306 includes at least one serial interface or at least one parallel interface. In certain embodiments, the interface 211 is operable to process, replicate, regenerate, modify, delay, format, compress, error check, or generate one or more of data signals, address signals, and control signals of the second set of data, address, and control signals based on one or more of data signals, address signals, and control signals of the first set of data, address, and control signals. In certain embodiments, the interface 211 manages and control communication of data, address, and/or control signals from/to the NV memory subsystem 305 to/from at least one of the memory control module 202 and one or more memory modules that are coupled to one or more channels of the memory module channel ch1-chn 209.
[0036] FIG. 4 illustrates a memory system 400 in which the memory control module 202 is coupled to the volatile memory subsystem 203 in the multi-channel arrangement ch1-chn 209 via the interface 211 as shown in FIG. 2 and as described above. Also shown coupled to the memory control module 202 is NV memory subsystem 405 according to one embodiment. The NV memory subsystem 405 includes NV controller 404 coupled to one or more channel of the memory module channel ch1-chn 209 via the interface 211 using the common signal bus 306, as shown in FIG. 3 and described above. The NV memory subsystem 405 includes a cache memory 410 coupled to the NV controller 404 and to a nonvolatile memory NVM 408. The cache memory 410 comprises volatile memory, for example one or more DRAM devices. In certain embodiments, the NV controller 404 comprises a plurality of NV controllers each of which may be used to independently control data communication between the NVM 408 and at least one of the memory control module 202 and the volatile memory subsystem 203. The coupling between the cache memory 410 and the NVM 408 is effected by a cache memory interface 410a and an NV memory interface 408a, both of which are controlled by NV controller 404 using an interface signal bus Is. The NV controller 404 can communicate one or more of data, status, test, errors, system operation, health and diagnostics information, and control information with at least one of the cache memory 410 and NVM 408.
[0037] In certain embodiments, the NVM 408 comprises one or more of non-volatile memory array, at least one non-volatile memory element or die, at least one packaged non-volatile memory device, at least one module comprising non-volatile memory, a FLASH memory device, or a memory module including one or more flash memory devices. Types of non-volatile memory compatible with NVM 408 include, but are not limited to, flash memory elements such as multi-level cell (MLC), NOR, ONE-NAND, and NAND flash memory.
[0038] In one embodiment, the common signal bus 306 is external to the NV memory subsystem 405 and is used to communicate data, address, and/or control signals between the NV controller 404 and a memory module coupled to any memory module channel of the memory module channel ch1-chn 209. In one embodiment, the coupling between the memory control module 202, the volatile memory subsystem 203, and the NV memory subsystem 405 is effected by way of the interface 211 for delivery of data, address and/or control signals via a respective memory channel of the memory module channel ch1-chn 209, or via the common signal bus 306.
[0039] In one embodiment, the common signal bus 306 comprises separate signal bus 3061-306n (not shown) and each signal bus of the signal bus 3061-306n is operable to deliver data, address, and control signals between a respective channel of the memory module channel ch1-chn 209 and the NV controller 404, in a similar manner as shown in FIG. 2 and as described above. The NV controller 404 is operable to receive and separately control each signal bus of the signal bus 3061-306n. The NV controller 404 in turn controls the transfer or storage of data directly from/to the NVM 408 or using the cache memory 410. In one embodiment, each of the signal bus 3061-306n is individually-addressable by the memory control module 202 or the NV controller 404, and is independently used to communicate data, address and control signals between the NV controller 404 and at least one of the memory control module 202 and one or more memory modules (DIMMs) (not shown) of the volatile memory subsystem 203.
[0040] In certain embodiments, the interface 211 is operable (i) to communicates one or more of data signals, address signals and control signals with the memory control module 202, (ii) to generate, process, or format one or more of data signals, address signals and control signals based at least in part on received data signals, address signals or control signals from the memory control module 202, the volatile memory subsystem 203, or the NV subsystem 405, and (iii) to selectively transmit one or more of data signals, address signals, and control signals to one or more of the memory control module 202, the volatile memory subsystem 203, and the NV subsystem 405 using one or more of at least a channel of the memory module channel ch1-chn 209, the common signal bus 306, a signal bus of the signal bus 3061-306n, and a cache memory 410. In certain embodiments, the interface 211 is integrated with the memory control module 202, a CPU, or a memory controller to form a single component, an integrated circuit, or a memory system.
[0041] In certain embodiments, the interface 211 snoops at least one of data signals, address signals, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits the at least one of data signals, address signals, and control signals to the NV controller 404. In certain embodiment, the interface 211 generates at least one of data signals, address signals, and control signals in response to at least one of data signals, address signals, and control signals received from any one of the memory control module 202, the volatile memory subsystem 203, or the NV memory subsystem 405. The interface 211 transmits the generated at least one of data signals, address signals, and control signals to the NV controller 504 via the common signal bus 306.
[0042] In certain embodiments, the interface 211 snoops a first set of data, address, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits a second set of data, address, and control signals via the common signal bus 306 to the NV controller 504. The second set of data, address, and control signals is generated based on the first set of data, address, and control signals. In one embodiment, the second set of data, address, and control signals correspond to a copy of the first set of data, address, and control signals. In one embodiment, one or more of data signals, address signals, and control signals of the first set of data, address, and control signals are processed by interface 211 before being transmitted as part of the second set of data, address, and control signals. For example, the interface 211 includes a serializer and a deserializer (or SERDES) in order to receive, process, format, and transmit data signals, address signals, or control signals using a serial interface or a parallel interface. In certain embodiments, the memory module channel ch1-chn 209 include a parallel interface, while the common signal bus 306 includes at least one serial interface or at least one parallel interface. In certain embodiments, each signal bus of the signal bus 3061-306n includes at least one SERDES that is used to couple the interface 211 to the NV controller 404. In certain embodiments, the interface 211 is operable to process, replicate, regenerate, modify, delay, format, compress, error check, or generate one or more of data signals, address signals, and control signals of the second set of data, address, and control signals based on one or more of data signals, address signals, and control signals of the first set of data, address, and control signals. In certain embodiments, the interface 211 manages and control communication of data, address, and/or control signals from/to the NV memory subsystem 405 to/from at least one of the memory control module 202 and one or more memory modules that are coupled to one or more channels of the memory module channel ch1-chn 209.
[0043] In certain embodiments, at least one NV chip select signal line NV-CS 450 (only one, CS1, is shown using a dashed line) is used to communicate at least one NV chip select signal between memory control module 202 and the at least one NV controller 404. The at least one NV chip select signal line NV-CS 450 may be similar to chip select signal lines communicating chip select signals from the memory control module 202 along each channel of the memory module channel ch1-chn for selection of associated volatile memories of memory modules (DIMMs) coupled to the memory module channel ch1-chn. The memory control module 202 uses the chip select signal lines to manage read/write operations from/to each of the volatile memory modules in the channels ch1-chn. In a similar manner, in one embodiment, the at least one NV chip select signal line NV-CS 450 may be used to couple a chip select signal to the NV controller 404, so that the chip select signal can be used by the memory control module 202 to manage read or write operations from/to the at least one NV memory 408 during, for example, backup and restore operations, as well as read or write operations from/to the volatile memory subsystem 203 via the one or more channels ch1-chn. The at least one NV chip select signal line NV-CS 450 may additionally or alternatively be used to couple other control or command signals from the memory control module 202 to the NV controller 404. Thus, other control or command signals can be used by the memory control module 202 to manage read or write operation from/to the at least one NV memory 408 in conjunction with read or write operations from/to the volatile memory subsystem 203 via the one or more channels ch1-chn.
[0044] In certain embodiments, the NV controller 404 is coupled directly to the memory control module 202 via at least one chip select line (NV-CS 450 shown as dashed lines). In certain embodiments, the NV controller 404 is coupled directly to interface 211 via at least one chip select line (not shown). In certain embodiments, the NV controller 404 receives at least one NV chip select signal NV-CS directly from the memory control module 202. In certain embodiments, the NV controller 404 receives the at least one NV chip select signal NV-CS directly from the interface 211. In certain embodiments, the interface 211 generates and transmits at least one NV chip select signal NV-CS to the NV controller 404. In certain embodiments, the interface 211 generates the at least one NV chip select signal NV-CS in response to data, address, or control signals from the memory control module 202 or the volatile memory system 203. In certain embodiments, the NV controller 404 receives at least one NV chip select signal NV-CS from the memory control module 202 via the interface 211 using the common signal bus 306 or via each of the signal bus 3061-306n.
[0045] FIG. 5 illustrates a memory system 500 in which the memory control module 202 is coupled to the volatile memory subsystem 203 in the multi-channel arrangement ch1-chn 209 via the interface 211 as shown in FIG. 2 and as described above. Also shown coupled to the memory control module 202 is NV memory subsystem 505 according to one embodiment. The NV memory subsystem 505 includes NV controller 504 coupled to one or more channels of the memory module channel ch1-chn 209 using one or more cache memory 5101-510n, (collectively cache memory 510), and the interface 211. The NV controller 504 is coupled to a nonvolatile memory NVM 508. The cache memory 510 comprises volatile memory, for example one or more DRAM devices. The cache memory 510 is coupled to the interface 211 using a common signal bus 306. In one embodiment, the one or more cache memories 510 are used to buffer and manage data transfer between the NV controller 504 and one or more memory module coupled to one or more channel of memory module channels ch1-chn 209. In one embodiment the NV controller 504 manages data backup and restore operations (e.g. write or read operations) to or from the NVM 508 and the volatile memory subsystem 203.
[0046] In one embodiment, the common signal bus 306 is external to the NV memory subsystem 505 and is used to communicate data, address, and/or control signals between the NV controller 304—via the cache memory 510 or bypassing the cache memory 510—and a memory module coupled to any memory module channel of the memory module channel ch1-chn 209. In one embodiment, the coupling between the memory control module 202, the volatile memory subsystem 203, and the NV memory subsystem 305 is effected by way of the interface 211 for delivery of data, address and/or control signals via a respective memory channel of the memory module channel ch1-chn 209, or via the common signal bus 306.
[0047] In one embodiment, the common signal bus 306 comprises separate signal bus 3061-306n (not shown) and each signal bus of the signal bus 3061-306n is operable to deliver data, address, and control signals between a respective channel of the memory module channel ch1-chn 209 and a respective cache memory 5101-510n. Various embodiments described above for the use of common signal bus 306 in FIG. 3 and FIG. 4 are applicable to embodiments and use as shown in FIG. 5 . The NV controller 504 is operable to separately control each signal bus of the signal bus 3061-306n for data communication with the volatile memory subsystem 203 and the memory control module 202. The NV controller 504 is operable to manage and control the transfer or storage of data from/to the NVM 308. In one embodiment, each of the signal bus 3061-306n is individually-addressable by the memory control module 202 or the NV controller 504, and is independently used to communicate data, address and control signals between the NV controller 504 and at least one of the memory control module 202 and one or more memory modules (DIMMs) (not shown) of the volatile memory subsystem 203.
[0048] In certain embodiments, the NV controller 504 comprises a plurality of NV controllers each of which may be used to independently control data communication between the NVM 508 and at least one of the memory control module 202 and the volatile memory subsystem 203. In one embodiment, the cache memory 510 includes a cache memory interface controlled by the NV controller 510 in order to manage data communication and signal interface with the NV controller 504 or the interface 211. The NV controller 504 can communicate one or more of data, status, test, errors, system operation, health and diagnostics information, and control information with at least one of the cache memory 510 and NVM 508.
[0049] In certain embodiments, the NVM 308 comprises one or more of non-volatile memory array, at least one non-volatile memory element or die, at least one packaged non-volatile memory device, at least one module comprising non-volatile memory, a FLASH memory device, or a memory module including one or more flash memory devices. Types of non-volatile memory compatible with NVM 308 include, but are not limited to, flash memory elements such as multi-level cell (MLC), NOR, ONE-NAND, and NAND flash memory.
[0050] In certain embodiments, the interface 211 is operable (i) to communicates one or more of data signals, address signals and control signals with the memory control module 202, (ii) to generate, process, or format one or more of data signals, address signals and control signals based at least in part on received data signals, address signals or control signals from the memory control module 202, the volatile memory subsystem 203, or the NV subsystem 505, and (iii) to selectively transmit one or more of data signals, address signals, and control signals to one or more of the memory control module 202, the volatile memory subsystem 203, and the NV subsystem 505 using one or more of at least a channel of the memory module channel ch1-chn 209, the common signal bus 306, a signal bus of the signal bus 3061-306n, and a cache memory of the cache memory 5101-510n. In certain embodiments, the interface 211 is integrated with the memory control module 202, a CPU, or a memory controller to form a single component, an integrated circuit, or a memory system.
[0051] In certain embodiments, the interface 211 snoops at least one of data signals, address signals, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits the at least one of data signals, address signals, and control signals to the NV controller 504 using at least one cache memory of the cache memory 5101-510n. In certain embodiment, the interface 211 generates at least one of data signals, address signals, and control signals in response to at least one of data signals, address signals, and control signals received from any one of the memory control module 202, the volatile memory subsystem 203, the cache memory 510, or the NV subsystem 505. The interface 211 transmits the generated at least one of data signals, address signals, and control signals to the NV controller 504 via the common signal bus 306.
[0052] In certain embodiments, the interface 211 snoops a first set of data, address, and control signals from one or more channel of the memory module channel ch1-chn 209, and transmits a second set of data, address, and control signals via the common signal bus 306 to the cache memory 510 or the NV controller 504. The second set of data, address, and control signals is generated based on the first set of data, address, and control signals. In one embodiment, the second set of data, address, and control signals correspond to a copy of the first set of data, address, and control signals. In one embodiment, one or more of data signals, address signals, and control signals of the first set of data, address, and control signals are processed by interface 211 before being transmitted as part of the second set of data, address, and control signals. For example, the interface 211 includes a serializer and a deserializer (or SERDES) in order to receive, process, format, and transmit data signals, address signals, or control signals using a serial interface or a parallel interface. In certain embodiments, the memory module channel ch1-chn 209 include a parallel interface, while the common signal bus 306 includes at least one serial interface or at least one parallel interface. In certain embodiments, each signal bus of the signal bus 3061-306n includes at least one SERDES that is used to couple the interface 211 to each of the cache memory 5101-510n. In certain embodiments, the interface 211 is operable to process, replicate, regenerate, modify, delay, format, compress, error check, or generate one or more of data signals, address signals, and control signals of the second set of data, address, and control signals based on one or more of data signals, address signals, and control signals of the first set of data, address, and control signals. In certain embodiments, the interface 211 manages and control communication of data, address, and/or control signals from/to the NV memory subsystem 505 to/from at least one of the memory control module 202 and one or more memory modules that are coupled to one or more channels of the memory module channel ch1-chn 209.
[0053] In certain embodiments, at least one NV chip select signal line NV-CS 550 (only one, CS1, is shown using a dashed line) is used to communicate at least one NV chip select signal between memory control module 202 and the at least one NV controller 504. The at least one NV chip select signal line NV-CS 550 may be similar to chip select signal lines communicating chip select signals from the memory control module 202 along each channel of the memory module channel ch1-chn for selection of associated volatile memories of memory modules (DIMMs) coupled to the memory module channel ch1-chn. The memory control module 202 uses the chip select signal lines to manage read/write operations from/to each of the volatile memory modules in the channels ch1-chn. In a similar manner, in one embodiment, the at least one NV chip select signal line NV-CS 550 may be used to couple a chip select signal to the NV controller 504, so that the chip select signal can be used by the memory control module 202 to manage read or write operations from/to the at least one NV memory 508 during, for example, backup and restore operations, as well as read or write operations from/to the volatile memory subsystem 203 via the one or more channels ch1-chn. The at least one NV chip select signal line NV-CS 550 may additionally or alternatively be used to couple other control or command signals from the memory control module 202 to the NV controller 504. Thus, other control or command signals can be used by the memory control module 202 to manage read or write operation from/to the at least one NV memory 508 during, for example, backup and restore operations, in conjunction with read or write operations from/to the volatile memory subsystem 203 via the one or more channels ch1-chn.
[0054] In certain embodiments, the NV controller 504 is coupled directly to the memory control module 202 via at least one chip select line (NV-CS 550 and NV-CS 550-1 shown as dashed lines). In certain embodiments, the NV controller 504 is coupled directly to interface 211 via at least one chip select line (NV-CS 550 and NV-CS 550-2 shown as dashed lines). In certain embodiments, the NV controller 504 receives at least one NV chip select signal NV-CS directly from the memory control module 202. In certain embodiments, the NV controller 504 receives the at least one NV chip select signal NV-CS directly from the interface 211. In certain embodiments, the interface 211 generates and transmits at least one NV chip select signal NV-CS to the NV controller 504. In certain embodiments, the interface 211 generates the at least one NV chip select signal NV-CS in response to data, address, or control signals from the memory control module 202 or the volatile memory system 203. In certain embodiments, the NV controller 504 receives the at least one NV chip select signal NV-CS from the memory control module 202 via the interface 211 using the common signal bus 306 or via each of the signal bus 3061-306n.
[0055] In certain embodiments, the memory controller 102-202 corresponds to a processor in a host computer system, a memory controller or a controller in other memory subsystems that can be used with the NV subsystem. In certain embodiments, the at least one NV controller 104-504 and the at least one non-volatile memory module 108-508 are mounted on the motherboard (not shown) or are coupled to the motherboard via an electrical interface. The electrical interface (not shown) can include at least one of an electrical connector, logic device, integrated circuit, programmable logic device, register, switch, and load reducing circuit. The electrical interface may include industry standard based components or custom designed components. The electrical interface can be integrated with the at least one NV controller 104-504 and/or with the at least one non-volatile memory NVM 108-508 to provide enhanced performance and lower cost.
[0056] Persons of ordinary skill in the art should recognize that the above examples of various arrangements of different components in the NV subsystem 105-505 are not exhaustive. Other variations are also possible to allow the NV subsystem to perform some or all of the operations described herein.
[0057] The NV subsystem 105-505 according to certain embodiments is usable with one or more DIMM channels that comprise standard DIMMs (e.g., RDIMM, HCDIMM, or LRDIMM) or proprietary DIMMs or other memory modules. The NV subsystem according to certain embodiments allows flexible sizing of the density of the non-volatile memory with respect to overall memory system requirements, as it is independent of the density of any of the one or more DIMMs or the overall density of the volatile memory subsystem 103-203. Read, write, backup and restore operations can be made from any of the one or more DIMMs to the non-volatile memory 108-508, or from the non-volatile memory to any of the one or more DIMMs, or between the memory control module 102-202 and the non-volatile memory 108-508. The NV subsystem 105-505 according to certain embodiments has complete control of a backup-and-restore memory space. Further, since the NV controller 104-504 and the non-volatile memory 108-508 are external to the DIMMs, there is no need for a dedicated back-up power (e.g., battery or special capacitor mounted on a DIMM) for the NV subsystem, as any battery or other type of regular or backup power source that may be powering the motherboard can support the operation of the NV subsystem according to certain embodiments.
[0058] In addition to backing up data during triggered events (e.g. actual or predicted power loss, or backup request), the NV subsystem 105-505 of certain embodiments can also operate independently to manage backup of data during normal system operation without support from memory controller 102-202. Such independent operation may be programmed into the NV subsystem upon initialization or in accordance with certain user defined parameters.
[0059] In the power loss data backup operation, the NV subsystem 105-505 according to certain embodiments pre-configures the NV controller 104-504 to copy data from specific main memory locations of volatile memory subsystem 103-203 to the non-volatile memory 108-508. The data in the main memory is not deleted as long as auxiliary power or back-up power (e.g. a battery or capacitor) is still available.
[0060] The NV controller 104-504 according to certain embodiments can be programmed to interrupt the backup operation if power is restored prior to completion of the backup process. In this case, the NV controller according to certain embodiments may not attempt to restore the data back to the main memory from the non-volatile memory since the data in the main memory should not have been lost.
[0061] When a power loss duration is long enough for the NV controller 104-504 to complete the data copy from the main memory to non-volatile memory, the NV controller according to certain embodiments restores the data back to the main memory from non-volatile memory as the system power is restored.
[0062] In the data backup during normal operation mode, the system described herein can pre-program the NV controller 104-504 with specific main memory addresses (or multiple ranges of address spaces). The NV controller can continuously monitor (write) data transactions by snooping main memory access activities, and if any write address is within the pre-programmed address spaces, the NV controller can write the snooped data into the non-volatile memory 108-508. This operation does not require any memory control module involvement as the NV controller automatically updates the non-volatile memory 108-508 as the data is updated in the preprogrammed main memory addresses. However, since this operation may require frequent write operation to non-volatile memory, it may cause accelerated NVM aging even with wear-leveling. Therefore, one or more caches, such as memory caches 410-710 shown respectively in FIGS. 4-5 , can be used to collect the updates prior to updating the non-volatile memory. In certain embodiments, the interface 211 may be used to monitor main memory access activities, and if any write address is within the pre-programmed address spaces, the interface 211 communicates data, address, and control signals corresponding to the main memory access activities to the NV controller 104-504, wherein the NV controller 104-504 is operable to manage and control writing the snooped data into the non-volatile memory 108-508. In certain embodiments, the interface 211 alerts the NV controller 104-504 using a least one chip select signal prior to communicating the snooped data to the NV controller 104-504.
[0063] In the embodiments shown in FIGS. 4-5 , the NV memory subsystem 405-505 can operate in an operation mode in which the memory caches 410-510 can be used to support fast capture of snooped data, to increase access performance of the non-volatile memory 408-508, and to minimize non-volatile memory write accesses so as to prolong the life of non-volatile memory 408-508.
[0064] In FIG. 4 , the memory caches 410 are located between the NV controller and the non-volatile memory, allowing the NV subsystem to have a unified cache to support all main volatile memory channels ch1-chn. While flow rate control may be more complicated due to the fact that there is a single data path from four main memory channels to one cache memory 410, placing the at least one cache between the NV controller 404 and the non-volatile memory 408 provides easier cache and non-volatile memory interface control. This arrangement also provides the flexibility of assigning different amounts of memory cache space for each memory channel, and the amount can be dynamically configured by the system or via programmable registers.
[0065] FIG. 5 shows at least one memory cache 510 per main memory channel, such that each memory channel ch1-chn is supported by at least one individual cache. Compared to the arrangements in FIG. 4 , the arrangements in FIG. 5 allow simpler control between the main memory channels ch1-chn and the memory caches 510, and from the memory caches to the NV memory 508. The cache size per main memory channel, however, may have to be predefined.
[0066] The configurations in FIGS. 4 and 5 , where at least one NV-CS signal is coupled to the NV controller 404 and 405, allow the memory system to have dynamic control on when data should be saved into the non-volatile memory 408, and 508. As shown in FIGS. 4 and 5 , the memory control module 202 can activate the NV-CS (NV chip select) signal whenever it decides to store a particular data transaction. The NV controller 404, 504, as it receives the NV-CS signal via the NV-CS signal line, can capture the data and address, and manage the operation of storing data in the associated address of the NV memory 408, 508. Furthermore, the NV controller or the interface can be programmed to monitor main memory control signals of each of the channels (e.g. the NV-CS signal line(s) or any other single control signal or a group of control signals forming a memory command) and automatically initiate backup data operation. Moreover, in the NV systems shown in FIGS. 4 and 5 , the NV controller can be preconfigured to automatically backup data that is written with specific memory addresses, while the memory control module can activate the NV controller via the NV-CS signal(s) to implement dynamic backup.
[0067] In certain embodiments, backup operations are triggered by one or more trigger conditions. Examples of the trigger conditions include power interruption, power failure, power reduction, system hang-up, a request by the host computer system, the host computer system voltage dropping below a certain threshold voltage, the host computer system voltage rising above a certain threshold voltage, the host computer system voltage being below a first threshold voltage and above a second threshold voltage, and a reboot condition.
[0068] Thus, a system according to certain embodiments herein is capable of providing configurable system level data persistence and can be used in many storage applications including, but not limited to, indexing for SSD (solid state device) or HDD (hard disk device), fast access of Hot data, preservation of transient data in network servers, preservation of not fully-committed transactions in transaction servers, persistent RAM Disks, preservation of state and interim results for backup and resume in computer servers.
[0069] For example, in the applications of indexing for SSD or HDD, the system according to certain embodiments allows NV storage of indexes of SSD or HDD data or content for fast data moves.
[0070] In the application of preservation of transient data in network servers, the system according to certain embodiments allows a memory system to configure the NV controller with main memory spaces (address ranges) that need to be stored into non-volatile for backup & restore operation (or for power loss protection) so as to preserve state and interim results for backup, restore, and resume
[0071] In the application of persistent RAM Disks, the NV system according to certain embodiments allows a memory system to program the NV controller to snoop data write operations from the main memory channels without intervention by memory control module 202. The NV controller can automatically make mirror images of certain address spaces of the main memory in nonvolatile memory while the main memory modules (e.g. DIMMs) perform write operations as issued by the memory control module 202.
[0072] The system according to certain embodiments offers various advantages over conventional DIMM with NV backup. For example, while a conventional DIMM with NV backup would have increased physical size and/or reduced DIMM volatile memory density to make space for an on-DIMM NV backup subsystem, the NV backup subsystem according to certain embodiments would provide backup for a memory system that has its DIMM sockets populated by high density standard DIMMs (RDIMM, HCDIMM, or LRDIMM). In addition, by having the NV backup subsystem mounted independently from the actual DIMMs in the presently-disclosed manner, the NV backup subsystem according to certain embodiments provides additional flexibility to control and manage the size or density of the non-volatile memory required for optimal cost and performance of the host computer system—irrespective of the number of independent memory channels (e.g. ch1-chn), the number of DIMMs per memory channel, and the actual density of each DIMM being used.
[0073] Furthermore, the NV backup subsystem according to certain embodiments provides the capability to control and manage backup from any one of the DIMMs, regardless which memory channel is being used, to the non-volatile memory, resulting in additional cost and/or performance advantages. This also provides maximum flexibility for the system to control the backup and restore memory space either directly or by offloading the backup and restore operations to an intelligent programmable NV backup subsystem. The host computer system can program the NV backup subsystem to automatically initiate backup or restore based on programmable user preferences or parameters. Furthermore, because the NV backup subsystem is not mounted on the DIMMs and can be integrated onto a motherboard of a host computer system, the motherboard's dedicated backup power source, e.g. battery or large capacitors, can be used to support the NV backup subsystem operations. Therefore, a host computer system level NV backup subsystem implementation provides whole system persistence with much less cost and more flexibility to configure, manage, and control the read and write operations from/to the non-volatile memory subsystem, e.g. backup and restore operations.
[0074] 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
What is claimed is:
1. A method for monitoring memory access operations in a computer system having a memory controller, the method comprising:
coupling the memory controller of the computer system to an interface via a set of data lines and a set of address and control signal lines;
coupling the interface to a first memory channel via a first set of data lines and a first set of address and control signal lines, wherein a first volatile memory subsystem is coupled to the interface via the first memory channel, the first volatile memory subsystem communicates data with the memory controller of the computer system via the interface using the first set of data lines;
coupling the interface to a second memory channel via a second set of data lines and a second set of address and control signal lines, wherein a second volatile memory subsystem is coupled to the interface via the second memory channel, the second volatile memory subsystem communicates data with the memory controller of the computer system via the interface using the second set of data lines;
coupling the interface to a nonvolatile memory subsystem, the nonvolatile memory subsystem including an NV (non-volatile) controller and at least one nonvolatile memory element;
monitoring each of the first and second memory channels to detect one or more memory access operations from the memory controller of the computer system to at least one predetermined address range of the first or second volatile memory subsystems; and
capturing a copy of data associated with the one or more memory access operations.
2. The method of claim 1, further comprising:
storing the captured copy of data associated with the one or more memory access operations in the at least one nonvolatile memory element.
3. The method of claim 1, wherein the one or more memory access operations include one or more data write operations performed by the memory controller of the computer system to one or more of the first or second volatile memory subsystems.
4. The method of claim 1, wherein (i) the first memory channel includes a first volatile memory module comprising the first volatile memory subsystem, (ii) the second memory channel includes a second volatile memory module comprising the second volatile memory subsystem, and (iii) the one or more memory access operations include one or more memory access operations performed by the memory controller to one or more of the first or second memory modules.
5. The method of claim 1, wherein the capturing a copy of data associated with the one or more memory access operations further comprising:
generating a trigger signal; and
capturing a copy of data associated with the one or more memory access operations in response to the trigger signal.
6. The method of claim 5, wherein the generating a trigger signal further comprises:
generating a trigger signal upon detecting the occurrence of one or more of a power interruption, a power failure, a power reduction, a system hang-up, a request by the host computer system, the host computer system voltage going below a certain threshold voltage, the host computer system voltage going above a certain threshold voltage, the host computer system voltage being below a first threshold voltage and above a second threshold voltage, and a reboot condition.
7. A method for performing memory access operations in a computer system having first and second volatile memory modules, the computer system including a memory controller configured to independently access the first and second volatile memory modules via respective first and second memory channels, the first volatile memory module being coupled to the first memory channel via a first set of data, address and control signal lines, the second volatile memory module being coupled to the second memory channel via a second set of data, address and control signal lines, the method comprising:
monitoring, using at least one NV (non-volatile) controller, the first and second memory channels to detect memory access operations;
capturing a copy of data associated with a first memory access operation to a first address range using a first one of the at least one NV controller upon detection of the first memory access operation, wherein the first memory access operation allows data to be communicated between the memory controller and the first volatile memory module using the first memory channel; and
capturing a copy of data associated with a second memory access operation to a second address range using a second one of the at least one NV controller upon detection of the second memory access operation, wherein the second memory access operation allows data to be communicated between the memory controller and the second volatile memory module using the second memory channel.
8. The method of claim 7, further comprising: storing the copy of data associated with the first memory access operation and the copy of data associated with the second memory access operation in a nonvolatile memory subsystem.
9. The method of claim 7, wherein the first address range is associated with the memory address space of the first volatile memory module, and the second address range is associated with the memory address space of the second volatile memory module.
10. The method of claim 8, further comprising:
detecting a trigger condition; and
restoring data from the nonvolatile memory subsystem to at least one of the first and second volatile memory modules in response to the trigger condition.
11. The method of claim 8, wherein the nonvolatile memory subsystem comprises one or more cache memory coupled to the NV controller and the first and second memory channels; and wherein storing the copy of data associated with the first or second memory access operation comprises storing the copy of data associated with the first or second memory access operation into the one or more cache memory.
12. The method of claim 11, further comprising: using the NV controller to manage data communication between the one or more cache memory and the nonvolatile memory subsystem.
13. The method of claim 7, further comprising: storing the copy of data associated with the first or second memory access operation into one or more cache memory coupled to the NV controller.
14. The method of claim 13, further comprising: using the NV controller to manage data communication between the one or more cache memory and the nonvolatile memory subsystem.
15. A method for operating a nonvolatile memory subsystem having an NV (non-volatile) controller and one or more nonvolatile memory modules, the method comprising:
using at least two memory channels to couple a host computer system to a volatile memory subsystem, wherein the at least two memory channels are independently accessible by the host computer system;
coupling the NV controller to the one or more nonvolatile memory modules;
coupling the NV controller to the at least two memory channels, wherein each one of the at least two memory channels includes address, data and control signals;
monitoring each one of the at least two memory channels for the occurrence of one or more memory access operations to the volatile memory subsystem; and
capturing a copy of data associated with a first memory access operation of the one or more memory access operations.
16. The method of claim 15, further comprising:
storing the copy of data associated with the first memory access operation into the one or more nonvolatile memory modules.
17. The method of claim 15, wherein the one or more memory access operations include one or more data write operations that allow data to be communicated between the host computer system and the volatile memory subsystem using any one of the at least two memory channels.
18. The method of claim 15, wherein the coupling of the NV controller to the at least two memory channels comprises:
using an interface to couple the NV controller to the at least two memory channels, wherein the interface comprises at least one of an electrical connector, logic device, integrated circuit, programmable logic device, register, switch, and load reducing circuit.
19. The method of claim 18, wherein the interface is operable to provide a plurality of conduits for data, address, and control signals between the NV controller and the host computer system, and wherein the interface is operable to couple data, address and control signals of the at least two memory channels to the NV controller.
20. The method of claim 15, further comprising:
generating a trigger signal; and
using the NV controller to store a copy of data associated with the first memory access operation into the one or more nonvolatile memory modules in response to the trigger signal.
21. The method of claim 20, wherein the generating a trigger signal further comprises:
generating a trigger signal upon detecting occurrence of a trigger condition, wherein the trigger condition is one or more of a power interruption, a power failure, a power reduction, a system hang-up, a request by the host computer system, the memory system detects that the host computer system voltage is below a certain threshold voltage, the memory system detects that the host computer system voltage is above a certain threshold voltage, the memory system detects that the host computer system voltage is below a first threshold voltage or above a second threshold voltage, and a reboot condition.
22. The method of claim 20, wherein the generating a trigger signal further comprises:
detecting a first address of the first memory access operation; and
generating a trigger signal if the first address is within a predetermined address range of the volatile memory subsystem.
23. The method of claim 15, further comprising:
generating a trigger signal; and
restoring data from the nonvolatile memory subsystem to at least one of first or second volatile memory modules in response to the trigger signal, wherein the first volatile memory module is coupled to one memory channel of the at least two memory channels, and the second volatile memory module is coupled to another memory channel of the at least two memory channels.
24. The method of claim 16, further comprising:
coupling one or more cache memory to the nonvolatile memory subsystem; and
storing the copy of data associated with the first memory access operation into the one or more cache memory.
25. The method of claim 24, further comprising:
using the NV controller to manage data communication between at least two of the cache memory, the nonvolatile memory subsystem, and the volatile memory subsystem.
Patent Citations (111)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2043099(A) | 1936-02-01 | Hanna | Applicant |
| US3562555(A) | 1971-02-01 | Ahrons | Applicant |
| US3916390(A) | 1975-10-01 | Chang et al. | Applicant |
| US4234920(A) | 1980-11-01 | Van Ness et al. | Applicant |
| US4420821(A) | 1983-12-01 | Hoffman | Applicant |
| US4449205(A) | 1984-05-01 | Hoffman | Applicant |
| US4965828(A) | 1990-10-01 | Ergott, Jr. et al. | Applicant |
| US5430742(A) | 1995-07-01 | Jeddeloh et al. | Applicant |
| US5519663(A) | 1996-05-01 | Harper, Jr. et al. | Applicant |
| US5519831(A) | 1996-05-01 | Holzhammer | Applicant |
| US5563839(A) | 1996-10-01 | Herdt et al. | Applicant |
| US5577213(A) | 1996-11-01 | Avery et al. | Applicant |
| US5619644(A) | 1997-04-01 | Crockett et al. | Applicant |
| US5675725(A) | 1997-10-01 | Malcolm | Applicant |
| US5870350(A) | 1999-02-01 | Bertin et al. | Applicant |
| US5874995(A) | 1999-02-01 | Naimpally et al. | Applicant |
| US5890192(A) | 1999-03-01 | Lee et al. | Applicant |
| US5953215(A) | 1999-09-01 | Karabatsos | Applicant |
| US6023421(A) | 2000-02-01 | Clinton et al. | Applicant |
| US6112310(A) | 2000-08-01 | Jun et al. | Applicant |
| US6145068(A) | 2000-11-01 | Lewis | Applicant |
| US6158015(A) | 2000-12-01 | Klein | Applicant |
| US6199142(B1) | 2001-03-01 | Saulsbury et al. | Applicant |
| US6216247(B1) | 2001-04-01 | Creta et al. | Applicant |
| US6269382(B1) | 2001-07-01 | Cabrera et al. | Applicant |
| US6336174(B1) | 2002-01-01 | Li et al. | Applicant |
| US6336176(B1) | 2002-01-01 | Leyda et al. | Applicant |
| US6421279(B1) | 2002-07-01 | Tobita et al. | Applicant |
| US6459647(B1) | 2002-10-01 | Kengeri | Applicant |
| US6487102(B1) | 2002-11-01 | Halbert et al. | Applicant |
| US6487623(B1) | 2002-11-01 | Emerson et al. | Applicant |
| US6658507(B1) | 2003-12-01 | Chan | Applicant |
| US6691209(B1) | 2004-02-01 | O'Connell | Applicant |
| US6721860(B2) | 2004-04-01 | Klein | Applicant |
| US6769081(B1) | 2004-07-01 | Parulkar | Applicant |
| US6799241(B2) | 2004-09-01 | Kahn et al. | Applicant |
| US6799244(B2) | 2004-09-01 | Tanaka et al. | Applicant |
| US6816982(B2) | 2004-11-01 | Ravid | Applicant |
| US6944042(B2) | 2005-09-01 | Komatsuzaki | Applicant |
| US6948029(B2) | 2005-09-01 | Yano | Applicant |
| US6952368(B2) | 2005-10-01 | Miura et al. | Applicant |
| US7053470(B1) | 2006-05-01 | Sellers et al. | Applicant |
| US7062618(B2) | 2006-06-01 | Tsunoda et al. | Applicant |
| US7089412(B2) | 2006-08-01 | Chen | Applicant |
| US7102391(B1) | 2006-09-01 | Sun et al. | Applicant |
| US7111142(B2) | 2006-09-01 | Spencer et al. | Applicant |
| US7155627(B2) | 2006-12-01 | Matsui | Applicant |
| US7200021(B2) | 2007-04-01 | Raghuram | Applicant |
| US7234099(B2) | 2007-06-01 | Gower et al. | Applicant |
| US7353325(B2) | 2008-04-01 | Lofgren et al. | Applicant |
| US7409491(B2) | 2008-08-01 | Doblar et al. | Applicant |
| US7409590(B2) | 2008-08-01 | Moshayedi et al. | Applicant |
| US7411859(B2) | 2008-08-01 | Sohn et al. | Applicant |
| US7421552(B2) | 2008-09-01 | Long | Applicant |
| US7467251(B2) | 2008-12-01 | Park et al. | Applicant |
| US7600142(B2) | 2009-10-01 | Ichikawa | Applicant |
| US7716411(B2) | 2010-05-01 | Panabaker et al. | Applicant |
| US7818488(B2) | 2010-10-01 | Park et al. | Applicant |
| US8086955(B2) | 2011-12-01 | Zhou et al. | Applicant |
| US8102614(B2) | 2012-01-01 | Song et al. | Applicant |
| US8233303(B2) | 2012-07-01 | Best et al. | Applicant |
| US8301833(B1) | 2012-10-01 | Chen et al. | Applicant |
| US8407395(B2) | 2013-03-01 | Kim et al. | Applicant |
| US8412879(B2) | 2013-04-01 | Chang et al. | Applicant |
| US8516187(B2) | 2013-08-01 | Chen et al. | Applicant |
| US8671243(B2) | 2014-03-01 | Chen et al. | Applicant |
| US8677060(B2) | 2014-03-01 | Chen et al. | Applicant |
| US8874831(B2) | 2014-10-01 | Lee et al. | Applicant |
| US8880791(B2) | 2014-11-01 | Chen et al. | Applicant |
| US8904098(B2) | 2014-12-01 | Amidi et al. | Applicant |
| US8904099(B2) | 2014-12-01 | Chen et al. | Applicant |
| US9043677(B2) | 2015-05-01 | Kong | Examiner |
| US2002/0083368(A1) | 2002-06-01 | Abe et al. | Applicant |
| US2002/0199061(A1) | 2002-12-01 | Friedman et al. | Applicant |
| US2003/0158995(A1) | 2003-08-01 | Lee et al. | Applicant |
| US2004/0088508(A1) | 2004-05-01 | Ballard et al. | Applicant |
| US2004/0163027(A1) | 2004-08-01 | MacLaren et al. | Applicant |
| US2004/0190210(A1) | 2004-09-01 | Leete | Applicant |
| US2005/0044302(A1) | 2005-02-01 | Pauley et al. | Applicant |
| US2005/0060488(A1) | 2005-03-01 | Poechmueller | Applicant |
| US2005/0132250(A1) | 2005-06-01 | Hansen et al. | Applicant |
| US2005/0141273(A1) | 2005-06-01 | Park et al. | Applicant |
| US2006/0039197(A1) | 2006-02-01 | Khouri et al. | Applicant |
| US2006/0069896(A1) | 2006-03-01 | Sanders | Applicant |
| US2006/0080515(A1) | 2006-04-01 | Spiers et al. | Applicant |
| US2006/0294295(A1) | 2006-12-01 | Fukuzo | Applicant |
| US2007/0136523(A1) | 2007-06-01 | Bonella et al. | Applicant |
| US2007/0192627(A1) | 2007-08-01 | Oshikiri | Applicant |
| US2008/0104344(A1) | 2008-05-01 | Shimozono et al. | Applicant |
| US2008/0147968(A1) | 2008-06-01 | Lee | Examiner |
| US2008/0195806(A1) | 2008-08-01 | Cope | Applicant |
| US2008/0235443(A1) | 2008-09-01 | Chow | Examiner |
| US2009/0031099(A1) | 2009-01-01 | Sartore | Applicant |
| US2010/0274953(A1) | 2010-10-01 | Lee et al. | Applicant |
| US2010/0322020(A1) | 2010-12-01 | Kim | Examiner |
| US2011/0078496(A1) | 2011-03-01 | Jeddeloh | Examiner |
| US2011/0320804(A1) | 2011-12-01 | Chan et al. | Applicant |
| US2012/0204079(A1) | 2012-08-01 | Takefman et al. | Applicant |
| US2012/0271990(A1) | 2012-10-01 | Chen et al. | Applicant |
| US2012/0317433(A1) | 2012-12-01 | Ellis | Examiner |
| US2013/0019076(A1) | 2013-01-01 | Amidi et al. | Applicant |
| US2013/0086309(A1) | 2013-04-01 | Lee et al. | Applicant |
| US2013/0254456(A1) | 2013-09-01 | Chen et al. | Applicant |
| US2013/0254497(A1) | 2013-09-01 | Chen et al. | Applicant |
| US2014/0032820(A1) | 2014-01-01 | Harasawa | Examiner |
| US2014/0059170(A1) | 2014-02-01 | Gasparakis et al. | Applicant |
| US2014/0156919(A1) | 2014-06-01 | Chen et al. | Applicant |
| US2014/0156920(A1) | 2014-06-01 | Chen et al. | Applicant |
| US2015/0058701(A1) | 2015-02-01 | Examiner | |
| EP2737383(A2) | 2014-06-01 | Applicant | |
| WO2013016723(A3) | 2013-01-01 | Applicant |
Non-Patent Literature (38)
- Office Action in U.S. Appl. No. 12/240,916, mailed Jul. 29, 2011.Applicant
- Office Action in U.S. Appl. No. 12/240,916, mailed Feb. 1, 2012.Applicant
- Advisory Action in U.S. Appl. No. 12/240,916, mailed Mar. 13, 2012.Applicant
- Office Action in U.S. Appl. No. 12/240,916, mailed Apr. 3, 2012.Applicant
- Office Action in U.S. Appl. No. 13/536,173, mailed Apr. 15, 2013.Applicant
- Office Action in U.S. Appl. No. 13/905,048, mailed Aug. 1, 2013.Applicant
- Notice of Allowance in U.S. Appl. No. 13/559,476, mailed May 6, 2014.Applicant
- International Search Report and Written Opinion in PCT/US12/48750, dated Oct. 10, 2012.Applicant
- International Preliminary Report on Patentability in PCT/US12/48750, mailed Apr. 3, 2014.Applicant
- Office Action in U.S. Appl. No. 13/625,563, mailed Aug. 5, 2013.Applicant
- Office Action in U.S. Appl. No. 13/625,563, mailed May 9, 2014.Applicant
- Office Action in U.S. Appl. No. 13/905,053, mailed Aug. 1, 2013.Applicant
- Office Action in U.S. Appl. No. 14/173,219, mailed Mar. 13, 2014.Applicant
- Office Action in U.S. Appl. No. 14/173,242, mailed Mar. 14, 2014.Applicant
- JEDEC Standard 21—C, “Configurations for Solid State Memories,” pp. 4.5.5-1 to 4.5.5-18.Applicant
- Diablo Technologies, Inc.'s Invalidity Contentions, Case No. 13-CV-05889 YGR, dated Jun. 6, 2014.Applicant
- Smart Storage Systems, Inc's Invalidity Contentions, Case No. 4:13-cv-05889-YGR, dated Jun. 6, 2014.Applicant
- JEDEC Standard, “Configurations for Solid State Memories”, JEDEC Standard 21—C, Release 9, Aug. 1999, 114 pages.Applicant
- Wong, A. “The Bios Optimization Guide”, Adrian's Rojak Pot, Rev. 6.2, 1998-2001, 67 pages.Applicant
- American National Standard Dictionary of Electrical and Electrical Terms, IEEE, Fourth Edition, Revised, ANS/IEEE Std 100-1988, Institute of Electrical Engineers, Nov. 3, 1988, pp. 215, 722, 964 and 1103.Applicant
- Webster's II New College Dictionary, Houghton Mifflin Company, Boston, MA, 2001, pp. 259, 1115.Applicant
- Bruce, J., “Synchronous DRAM Architectures, Organizations, and Alternate Technologies”, Electrical and Computer Engineering Dept., Univ. of Maryland, Dec. 10, 2002, 22 pages.Applicant
- David, H. et al., “Fully Buffered DIMM (FB-DIMM) Design Considerations”, Intel Developer Forum, Intel Corp., Feb. 18, 2004, 36 pages.Applicant
- Horowitz, P. et al., “The Art of Electronics”, Cambridge University Press 2nd Ed. 1989, pp. 471, 495-496.Applicant
- Innis, J., “MPC8560 PowerQUICC III Compact Flash Interface Design”, Freescale Semiconductor, Inc., 2004-2006, pp. 1-23.Applicant
- Jacob, B., “Memory Systems Cache, DRAM, Disk”, Morgan Kaufman Publishers, Burlington, MA, 2008, Preface and Ch. 7 pp. 315-322.Applicant
- Jandhyala, S. et al., “Design-For-Test Analysis of a Buffered SDRAM DIMM”, Semiconductor Group, Texas Instruments, Proceedings of International Workshop in Memory Technology, Design and Testing, Singapore, Aug. 13014, 1996, 15 pages.Applicant
- JEDEC Standard, Double Data Rate (DDR): SDRAM Specification: JESD79C (Revision JESD79B), Mar. 2003, pp. 1-75.Applicant
- JEDEC Standard, FBDIMM Specification: DDR2 SDRAM Fully Buffered DIMM (FBDIMM) Design Specification: JESD205, JEDEC Solid State Tech. Assoc., Mar. 2007, pp. 1-129.Applicant
- Mutnuary, B. et al., “Analysis of Fully Buffered DIMM Interface in High-speed Server Applications”, IBM Corp, xSeries eServer Development, 2006 Electronic Components and Technology Conference, pp. 203-208.Applicant
- Petition for Inter Partes Review of U.S. Pat. No. 8,516,187 (on behalf of SanDisk, Corp.), filed Jun. 19, 2014.Applicant
- Petition for Inter Partes Review of U.S. Pat. No. 8,301,833 (on behalf of SanDisk, Corp.), filed Jun. 20, 2014.Applicant
- “Using Two Chip Selects to Enable Quad Rank”, an IP.com Prior Art Database Technical Disclosure, IP.com Electronic Publication: Dec. 17, 2005, 2 pages.Applicant
- Petition for Inter Partes Review of U.S. Pat. No. 8,516,187 (on behalf of SMART Modular Technologies, Inc.), filed Aug. 22, 2014.Applicant
- Petition for Inter Partes Review of U.S. Pat. No. 8,301,833 (on behalf of SMART Modular Technologies, Inc.), filed Aug. 22, 2014.Applicant
- “Out of Stealth Mode, Start-Up MetaRAM Unveils New Technology That Quadruples DRAM Capacity”, Press Release edited by Storage Newsletter on Feb. 28, 2008 at StorageNewsLetter.com, 8 pages.Applicant
- “MetaRAM Develops New Technology That Quadruples Memory Capacity of Servers and Workstations; Reduces Price by Up to 90 Percent”, Press Release provided by MetaRAM and published on MarketWired.com, Feb. 25, 2008, 3 pages.Applicant
- “240pin DDR2 MetaSDRAM Registered DIMM based on 1 GB version C”, Hynix Semiconductor, Product Description Rev. 0.2, Sep. 2008, 32 pages.Applicant