Various embodiments described herein relate to apparatus, systems, and methods associated with semiconductor memories.
A number of configurations in computer memory exist to protect data against errors or failure of memory devices. Error Check and Correcting (ECC) configurations such as Chipkill™ exist that protect computer memory systems from any single memory chip failure as well as multi-bit errors from any portion of a single memory chip. In Chipkill™, bits of multiple ECC words are scattered across multiple memory chips, such that the failure of any one memory chip will affect each ECC value looking like multiple correctable errors. This allows memory contents to be reconstructed despite the complete failure of one chip. ECC implementations more complex than Chipkill™ are seldom done with most current high density memory integrated circuits because of the additional memory and chip area required. Simpler detection/correction schemes such as parity check or single bit correction are often implemented.
In computer hard drive memory, Redundant Arrays of Inexpensive Disks (RAID) configurations allow backup of data when multiple drives are arranged in parallel, where n+1 drives are used to store data. The extra memory of the “1” drive of n+1 in a RAID 4 or RAID 5 configuration is used to store the ECC data. However, RAID configurations are often relatively slow during write operations because each write requires updating of the ECC data, such that two writes are required for every operation (one for the data being written, and another for the updated ECC being written). Performance of a RAID 5 configuration when writing is approximately one half the performance of reading. Other operations of a parallel RAID configuration, such as data recovery, can be much slower than half the speed of a read operation.
The inventor has realized that improved memory configurations with error recovery are desired that reduce the amount of memory needed to store error recover data (e.g., ECC data) for cases where recovery from failures of memory components is required. The inventor has further realized that improved memory configurations with error recovery are desired that reduce any impact to operating speed during error recovery, data write operations, etc. The inventor has further realized that memory configurations are desired that allow ECC to be included or left out without needing differing kinds of components, or adding expense if ECC is not required.
In the following detailed description of the invention, reference is made to the accompanying drawings that form a part hereof and in which are shown, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and structural, logical, and electrical changes may be made.
In one example, error recovery data in the ECC device 122 is formed as the sum of the data written to the same address of all the other data units in the group. For example the address (100) in the ECC device 122 is written with A(100)+B(100)+C(100) . . . for as many memory devices (A, B, C, etc.) as there are in the chain. Thus ECC(n)=A(n)+B(n)+ . . . +M(n) for any number of memory devices A through M and for each data address within the memory devices. A common example of summing to form error recovery data includes performing an exclusive or (XOR) operation on incoming data. Individual error recovery data from each memory device 120 can be combined to form error recovery data in the ECC device 122. In the event of a failure in any given memory device 120, data can be reconstructed using the error recovery data in the ECC device 122 at the end of the chain.
The memory devices 120 of the memory system 110 are shown serially coupled together in the chain. The serial connection includes a request path 102 (which can also be referred to as an outgoing path) from the host 100, and a response path 104 (which can also be called a return path). In one embodiment, memory requests are sent from the host 100 down the request path 102. In one example the memory request is in packet form, and may include both data, and address and control information to indicate a particular memory device 120 and a location within the particular memory device 120.
In one embodiment, a request travels down the request path 102 until it reaches the ECC device 122, then it returns on the response path 104. For example, a write request travels down the request path 102 including the data to be written, along with address information. As the data is written in the particular memory device 120, an ECC update operation is sent to the ECC device 122 and a completion signal is returned to the host on the response path 104. If a read operation is requested, the data is returned on the response path.
Although
In one example when new data is to be written to a given memory device 120 in the chain, corresponding error recovery data is updated. In one example, all memory devices 120 in the chain closer to the host controller than the addressed device merely pass the write request down the chain. Once the given memory device in the chain is reached, old data that is currently at the location to be written in the given memory device 120 is subtracted from the new data to be written at the location in the given memory device 120. The data to be written is then written into the location in the given memory device 120.
The difference is then passed down the remaining devices, if any, to the ECC device 122. In one example the ECC device then adds the difference that has been passed down, to the ECC data for the location to be written. In this way, the ECC data is updated to reflect the write operation. Because the error recovery data includes information from each memory device 120 in the chain, the data in any one failing memory device 120 can be reconstructed using the error recovery data.
In one embodiment the memory device 120 includes local storage coupled to the first and/or second logic blocks 210, 220. Embodiments with local storage capacity allow error recovery data operations to take place independently within the memory device 120, without otherwise impacting other read or write operations or their timing. One configuration for local storage includes a register or similar memory capability within the first and/or second logic blocks 210, 220.
In one example, a specially configured ECC unit is installed in the chain of memory devices 120 as the ECC device 122. In another example, all memory devices 120 including the ECC device 122 have identical hardware, and the ECC device 122 is put into a mode that indicates that it is the ECC device 122. Embodiments using identical hardware for all memory devices 120 are more efficient for manufacturing purposes.
The embodiment illustrated in
In operation 320, new error recovery data is calculated as the new data passes along the chain using data currently in the memory devices in the chain and the new data. In one example, old data is read at the selected device, and an ECC data update is calculated within the selected memory device by subtracting the old data from the new data. In one example, calculating new error recovery data includes an XOR operation. In one example, only the selected memory device in the chain performs the ECC data calculation, while other memory devices in the chain merely pass the request along the chain. One of ordinary skill in the art, having the benefit of the present disclosure will recognize that ECC operations other than XOR are also within the scope of the invention.
In operation 330, the new data is written in the selected memory device along the chain, and in operation 340, the new error recovery data is passed down the chain of memory devices to the ECC device at the end of the chain. In one embodiment, the new data is written at the same time that the new error recovery data is passed down the chain. Once the new error recovery data reaches the ECC device, in operation 350, the old error recovery data stored in the ECC device is modified by adding the new recovery data to the ECC data at the same address, generally the addition is a boolean XOR operation. Using the error recovery data and data from non-failing memory devices, data from any single failing memory device can be reconstructed.
In one example, if a device determines it has an unrecoverable data error, that device responds to the host or chain controller which then starts a recovery sequence.
In operation 430, after the recovery request reaches the ECC device at the end of the chain, the requested error recovery data is returned back up the chain. In operation 440 the data is combined from the local logic blocks as described in operation 420 in each memory device, except the failing device, with the error recovery data to reconstruct the data from the failing device. In one example, combining the data from the local logic blocks includes an XOR operation. After the individual XOR operations at each memory device, when the data finishes traveling back up the chain, the data from the failing memory device is recovered.
Using the methods and serially interconnected devices as described in examples above, the extra read and write operations that are burdensome in a parallel configuration happen automatically and without any effort or time taken by a memory controller at a host. Because extra operations in the described serial configurations take place further down the chain from a write operation, the extra operations are largely hidden from a performance standpoint. Further, using the serial methods and devices described in examples above, a memory controller does not have to generate multiple read requests in a recovery operation as is needed in a parallel configuration.
A number of types of memory devices are possible for use in methods and device configurations described above. Some examples include, but are not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), flash memory such as NAND or NOR, etc.
The illustrated stacked chip memory device embodiment aggregates control logic that is normally located on each individual memory array die. The memory vaults 506 shown in the illustrated example share common control logic. The memory vault architecture strategically partitions memory control logic to increase energy efficiency while providing a finer granularity of powered-on memory banks. Embodiments shown also enable a standardized host processor to memory system interface. The standardized interface may reduce re-design cycle times as memory technology evolves.
The apparatus and systems of various embodiments may be useful in applications other than a high-density, multi-link, high-throughput semiconductor memory subsystem. Thus, various embodiments of the invention are not to be so limited. The illustrations of the stacked chip memory device 500 are intended to provide a general understanding of the structure of various embodiments. They are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein.
The novel apparatus and systems of various embodiments may comprise or be incorporated into electronic circuitry used in computers, communication and signal processing circuitry, single-processor or multi-processor modules, single or multiple embedded processors, multi-core processors, data switches, and other information handling systems.
Examples of such systems, include, but are not limited to supercomputers, televisions, cellular telephones, personal data assistants (PDAs), personal computers (e.g., laptop computers, desktop computers, handheld computers, tablet computers, etc.), workstations, radios, video players, audio players (e.g., MP3 (Motion Picture Experts Group, Audio Layer 3) players), vehicles, medical devices (e.g., heart monitor, blood pressure monitor, etc.), set top boxes, and others.
While a number of embodiments of the invention are described, the above lists are not intended to be exhaustive. Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiment shown. This application is intended to cover any adaptations or variations of the present invention. It is to be understood that the above description is intended to be illustrative and not restrictive. Combinations of the above embodiments, and other embodiments, will be apparent to those of skill in the art upon studying the above description.
This application is a continuation of U.S. application Ser. No. 12/479,530, filed Jun. 5, 2009 now U.S. Pat. No. 8,046,628, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5928343 | Farmwald et al. | Jul 1999 | A |
6683372 | Wong et al. | Jan 2004 | B1 |
7000062 | Perego et al. | Feb 2006 | B2 |
7206962 | Deegan et al. | Apr 2007 | B2 |
7363533 | Gower et al. | Apr 2008 | B2 |
7484161 | Dell et al. | Jan 2009 | B2 |
7676729 | Cheng et al. | Mar 2010 | B2 |
7701251 | Rahman et al. | Apr 2010 | B1 |
7746095 | Pax et al. | Jun 2010 | B2 |
7779292 | Fields et al. | Aug 2010 | B2 |
7840860 | Alves et al. | Nov 2010 | B2 |
8046628 | Resnick | Oct 2011 | B2 |
20050105350 | Zimmerman | May 2005 | A1 |
20050162882 | Reeves et al. | Jul 2005 | A1 |
20060146637 | Vogt | Jul 2006 | A1 |
20060179362 | Alves et al. | Aug 2006 | A1 |
20060271720 | James et al. | Nov 2006 | A1 |
20070136537 | Doblar et al. | Jun 2007 | A1 |
20080101104 | Ikeda | May 2008 | A1 |
20080307252 | Bartley et al. | Dec 2008 | A1 |
20080307253 | Bartley et al. | Dec 2008 | A1 |
20090006886 | O'Connor et al. | Jan 2009 | A1 |
20090049365 | Kim et al. | Feb 2009 | A1 |
20090237971 | Chung et al. | Sep 2009 | A1 |
20100042889 | Hargan | Feb 2010 | A1 |
20100217915 | O'Connor et al. | Aug 2010 | A1 |
20100240205 | Son et al. | Sep 2010 | A1 |
20100299576 | Baysah et al. | Nov 2010 | A1 |
20100313067 | Resnick | Dec 2010 | A1 |
20110231735 | Park et al. | Sep 2011 | A1 |
Number | Date | Country | |
---|---|---|---|
20120042201 A1 | Feb 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12479530 | Jun 2009 | US |
Child | 13279926 | US |