It is common knowledge that Dynamic Random Access Memory (“DRAM”) modules are comprised of capacitive electrical cells that leak their charge out over time. As a result, DRAM cells must be recharged, or “refreshed”, thousands of times per second or they lose their data. Reading from or writing to a DRAM cell refreshes its charge, so a common way of refreshing a DRAM is to read periodically from each cell. This is typically accomplished by only activating each row using Row Address Strobe or RAS. In addition, a DRAM cell controller takes care of scheduling the refresh cycles and making sure that they don't interfere with regular reads and writes. So to keep the data in DRAM module from leaking away, the cell controller periodically sweeps through all of the rows by cycling RAS repeatedly and placing a series of row addresses on the address bus.
Even though the cell controller handles all the refreshes and tries to schedule them for maximum performance, having to go through and refresh each row every few milliseconds can interfere with the performance of reads and writes and thus have a serious negative impact on the performance of the DRAM modules. Clearly, it is beneficial to overall system performance to reduce the amount of time spent refreshing DRAM cells. As used herein, “system performance” takes into account factors including, but not limited to, data bandwidth, latency, overall system power consumption, acoustic noise, and others.
The number of refresh cycles required to refresh an entire DRAM module depends on the number of rows of DRAM cells in that module; the more rows, the greater the number of cycles required to refresh the entire module. Therefore, one manner in which to reduce the amount of time spent refreshing DRAM modules is to reduce the number of rows in the module.
Another manner in which to reduce the amount of time spent refreshing DRAM modules is to adjust the refresh rate; that is, the frequency with which the modules are refreshed. Commonly, there is a feature in the Basic I/O System (“BIOS”) of a computer system that allows a user to set the refresh rate of the DRAM modules. In one embodiment, BIOS supports three different refresh rate settings, as well as an “AUTO” option. If the AUTO option is selected, the BIOS queries the DRAM modules and uses the lowest setting found for maximum compatibility. Optimizing the refresh rate is important, yet difficult. Refreshing too often negatively impacts system performance, as indicated above. In contrast, refreshing too infrequently can result in lost data due to an increase in errors, some of which may be of such a magnitude as to be uncorrectable.
Other system adjustments that can lessen the frequency or magnitude of DRAM errors include increasing the fan speed and migrating data from one memory module to another. Each adjustment, while positively impacting DRAM performance, has a corresponding negative effect on overall system performance. Accordingly, it would be beneficial only to make such adjustments when absolutely necessary.
In One embodiment, a method of correcting errors in a memory subsystem in a computer system is disclosed. Occurrences of correctable memory errors are monitored and a determination is made whether a risk of the occurrence of an uncorrectable memory error is less than a tolerable risk. If the risk of an occurrence of an uncorrectable memory error is not less than the tolerable risk, at least one system level parameter is adjusted to decrease the occurrence of correctable memory errors.
In the drawings, like or similar elements are designated with identical reference numerals throughout the several views thereof, and the various elements depicted are not necessarily drawn to scale.
It will be recognized that memory errors can be measured in terms of how often they occur (i.e, frequency) and in terms of the number of bits in error (i.e., magnitude). One embodiment recognizes that the likelihood of the occurrence of an uncorrectable error increases as the frequency and/or magnitude of correctable errors increase.
As such, in an embodiment described hereinbelow, the frequency and/or magnitude of correctable errors are monitored over a given window of time and, based on the results of the monitoring, system level adjustments are made to maintain the likelihood of the occurrence of an uncorrectable error below an acceptable threshold. Examples of such system level adjustments and the corresponding negative impact(s) on overall system performance of each include:
As illustrated above, each system level adjustment carries with it some undesirable cost; therefore, it is prudent to make such adjustments only when absolutely necessary. An embodiment described herein facilitates that goal.
The system 100 further comprises a system management unit (“SMU”) 106 for receiving from the chipset 102 data regarding correctable errors experienced by the memory subsystem 104. As will be described in greater detail with reference to
The term “tolerable risk” is defined as the amount of risk that will be tolerated before system level adjustments will be made by the SMU 106. In block 200, the tolerable risk is set to some level determined to result in optimum system performance while minimizing the probability that an uncorrectable error will occur. It will be recognized that the level of risk that is tolerable will be dependent upon the particulars of a given system and the environment in which the system is used.
In block 202, the SMU 106 calculates the risk of occurrence of an uncorrectable memory error for a time window of interest based on the correctable error data received from the chipset 102. For example, assuming ΔW represents the size of the window of interest, Δt represents the size of a time shift, and t0 represents an initial point in time, at a time tn=t0+nΔt, the SMU 106 will calculate the risk R for a time window Wn extending from time tn to time tn+ΔW. This concept is illustrated in FIG. 3, where ΔW is equal to 4Δt and a time window W0 extends from time t0 to time t4, a time window W1 extends from time t1 to time t5, a time window W2 extends from time t2 to time t6, and so on.
In block 204, a determination is made whether the risk calculated in block 202 is less than the tolerable risk. If not, execution proceeds to block 206, in which the SMU 106 instructs the system level control unit 108 to adjust one or more of various system operating parameters to decrease the risk. Examples of parameters that could be adjusted include fan speed, refresh rate, clock frequency, power consumption, transaction mix, and migration of data to other memory modules, to name a few. It will be recognized that any number of combinations of system parameter adjustments may be performed in order to decrease the magnitude and/or frequency of correctable memory (e.g., DRAM) errors and thereby decrease the risk that an uncorrectable error will occur. Upon completion of the adjustments in block 206, execution proceeds to block 208. If a positive determination is made in block 204, execution proceeds directly to block 208. In block 208, the time window of interest is shifted by Δt and execution returns to block 202.
Those skilled in the art should appreciate the embodiments described herein capitalize on the realization that uncorrectable errors become more likely as the frequency of correctable errors increases. As such, the exemplary embodiments provide for monitoring of the rate at which correctable errors occur and, based on this information, system level adjustments may be made which keep the likelihood of uncorrectable errors within acceptable ranges. Furthermore, this loop of measurements and corrections may be carried out continuously for each system in order to maintain continuous optimal operation.
It will be noted that an embodiment as described with reference to
It will be further noted that monitoring of the magnitude and frequency of correctable errors directly, as opposed to indirect monitoring thereof through monitoring of system conditions that may result in such errors, will decrease the likelihood that unnecessary system level adjustments, with their attendant negative consequences, will be made.
It will also be recognized that although the chipset 102 and SMU 106 are illustrated as comprising separate elements, the functionality thereof could be implemented as a single element. Moreover, the functionality of the chipset 102 and SMU 106 could be implemented as more than two elements where desired.
An implementation of the invention described herein thus provides method and system for performing system-level correction of memory, in particular, DRAM, errors in a computer system. Not only is the performance of a computer system under normal operations ensured to be optimized, the teachings set forth herein allow the system level adjustments to be made to the computer system only when necessary to reduce the risk of occurrence of an incorrectable memory error. Accordingly, the embodiments of the present patent application help avoid the high costs associated with over-design of environmental infrastructure associated with a computer system.
The embodiments shown and described have been characterized as being illustrative only; it should therefore be readily understood that various changes and modifications could be made therein without departing from the scope of the present invention as set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4638427 | Martin | Jan 1987 | A |
5058115 | Blake et al. | Oct 1991 | A |
5228046 | Blake et al. | Jul 1993 | A |
5313625 | Hess et al. | May 1994 | A |
5412799 | Papadopoulos | May 1995 | A |
5533036 | Blake et al. | Jul 1996 | A |
5682394 | Blake et al. | Oct 1997 | A |
6481974 | Horng et al. | Nov 2002 | B2 |
6489912 | Lamb et al. | Dec 2002 | B2 |
6515917 | Lamb et al. | Feb 2003 | B2 |
6662136 | Lamb et al. | Dec 2003 | B2 |
6702665 | Tai | Mar 2004 | B1 |
6757857 | Lamb et al. | Jun 2004 | B2 |
6874108 | Abramovici et al. | Mar 2005 | B1 |
6985940 | Jenkin | Jan 2006 | B1 |
7058782 | Henderson et al. | Jun 2006 | B2 |
7085993 | Goodnow et al. | Aug 2006 | B2 |
7100004 | Chen Johnson et al. | Aug 2006 | B2 |
7222266 | Wu et al. | May 2007 | B2 |
20020099521 | Yang et al. | Jul 2002 | A1 |
20020110457 | Horng et al. | Aug 2002 | A1 |
20020145919 | Lamb et al. | Oct 2002 | A1 |
20020147564 | Lamb et al. | Oct 2002 | A1 |
20020147949 | Lamb et al. | Oct 2002 | A1 |
20020149972 | Lamb et al. | Oct 2002 | A1 |
20030037266 | Karpel et al. | Feb 2003 | A1 |
20030173830 | Smith et al. | Sep 2003 | A1 |
20040019844 | Goodnow et al. | Jan 2004 | A1 |
20050022065 | Dixon et al. | Jan 2005 | A1 |
20050107997 | Watts et al. | May 2005 | A1 |
20050160323 | Wu et al. | Jul 2005 | A1 |
20060010352 | Mukherjee et al. | Jan 2006 | A1 |
20060195755 | Brown | Aug 2006 | A1 |
20070101238 | Resnick et al. | May 2007 | A1 |
Number | Date | Country | |
---|---|---|---|
20060236162 A1 | Oct 2006 | US |