The present disclosure relates generally to computer systems and information handling systems, and, more particularly, to a system and method for creating a map of memory which governs its use by the computer system or information handling system.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to these users is an information handling system. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may vary with respect to the type of information handled; the methods for handling the information; the methods for processing, storing or communicating the information; the amount of information processed, stored, or communicated; and the speed and efficiency with which the information is processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include or comprise a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
A computing system will typically include some type of temporary information storage medium, such as random access memory. In recent computers, the amount of memory comprised by the information handling system may be on the order of gigabytes. As memory size increases, the likelihood that part of the memory will either be manufactured defective or become defective over time increases. If left unmanaged, the presence of defective memory cells, regardless of their size, can cause the information handling system to fail. Such failure can initiate an abrupt end to the current operation of the information handling system, resulting in the loss of critical data. In addition, the presence of defective memory can prevent the information handling system from starting up altogether.
As computing systems continue to evolve and computer technology advances, the operational relationship between the CPU and memory becomes more significant. Many attributes of modern systems (specifically the introduction of multi-core processors and virtualization in general) are forcing an ever-growing memory footprint. Consequently, not only is system memory growing to be a much more substantial percentage of the overall solution cost, but the impact of erroneous behavior in the memory can have a much more adverse effect on the life cycle expenses associated with the computing system.
In accordance with the present disclosure, a method for storing a memory defect map is disclosed whereby a memory component is tested for defects at the time of manufacture and any memory defects detected are stored in a memory defect map and used to optimize the system performance. The memory defect map is updated and the system's remapping resources optimized as new memory defects are detected during operation.
A technical advantage of the present invention is that it significantly reduces the cost of an information handling system by allowing the use of memory components with known memory defects without jeopardizing the system performance. Availability of a non-volatile memory defect map allows an information handling system to utilize the memory component without “crashing.” Moreover, because the memory defect map is coupled to the memory component, the memory component can be moved from one system to another while retaining any defect information. The importance of this improvement is magnified as the system memory is growing to represent a substantial portion of the overall solution cost.
Another technical advantage of the present invention is that it allows the system to maintain normal operations despite minor deficiencies in the system memory. By minimizing the impact of erroneous memory behavior a system and method in accordance with the present invention can significantly reduce the life cycle expenses associated with an information handling system. Yet another technical advantage of the present disclosure is that it reduces the need for any significant testing and characterization prior to conveying memory defect information to the information handling system. Other technical advantages will be apparent to those of ordinary skill in the art in view of the following specification, claims, and drawings.
A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communication with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
Shown in
Each memory component is tested during or subsequent to being manufactured and any memory defect information is stored in a nonvolatile storage. In one embodiment, the nonvolatile storage is on the memory component itself. In the exemplary embodiment depicted in
The memory defect map need not be stored in the on-chip EEPROM 404 used for SPD. Rather, any form of non-volatile storage could be utilized to store the map. A standard EEPROM 404 has the advantages of already being widely implemented and at least partially available for storage of the map. It is desirable that the memory map be stored on the DIMM itself, since it is advantageous for the map to remain with the DIMM it maps when, for example, the DIMM is moved from one system to another. Once the DIMM or other memory component is mated to a specific system, the memory defect information which is stored on the DIMM itself can be retrieved and used by the system as part of its memory allocation scheme.
The memory defect information or memory defect map is a map where each entry corresponds to a region of physical address on the memory component. For example, where the memory component is a DIMM, these regions are defined by the DIMM capacity amortized across the number of entries in the map. The size of a memory block designated as defective is thus equal to the DIMM capacity divided by the number of bits in the defect map. As would be appreciated by those of ordinary skill in the art, with the benefit of this disclosure, the memory defect map is not limited to the information stored on the memory component during the manufacture process as disclosed here. For example, defect information may be obtained by an exhaustive software based memory test or an external test mechanism. The stored memory defect map can be used to optimize the system performance in a variety of ways.
In one exemplary embodiment, the memory defect map may be used as a means for avoiding disruption of subsequent memory tests. Memory test are commonly carried out by an information handling system. For example, the BIOS may run an onboard test of the memory components. Typically, the memory test will also analyze the areas in the memory components where defects are already known to exist. Depending on the severity of the defect in the defective region, the analysis of the defective region may disrupt the test and potentially erode the behavior of the test. In one exemplary embodiment the stored memory defect map may be used to avoid redundant testing of regions already known to be defective.
If the target address is not in the memory defect map, then at step 506 a memory test is conducted to determine whether the target address nevertheless contains defective memory locations. As would be appreciated by those of ordinary skill in the art, with the benefit of this disclosure, a number of different tests may be conducted to determine whether the target location is a defective memory space.
At step 508 the result of the memory test is used to decide whether the target address corresponds to a defective memory location. If the target address is not defective then the process will continue to step 510 where it is determined whether there are more memory locations to be tested. If not the process terminates at 512 and if there are more memory locations to be tested, then the next address to be tested as retrieved at 514. In contrast, if the target address is defective then the memory defect map is updated at step 516 and the target address is added to the list of addresses corresponding to defective memory locations before searching for additional locations to be tested.
The first available target address that is not listed in the memory defect map is then subjected to a memory test at 608. Next, at step 610 it is determined whether the test indicated that the retrieved target address corresponded to a defective memory location. If yes, then the target address is added to the memory defect map at step 612. The process then continues to step 614 where it is determined whether there are any more memory locations that should be subjected to the memory test. If yes, then the next target address is retrieved at step 616 and the process is repeated. The process will finally terminate at step 618 once there are no more memory locations remaining to be tested.
Turning now to
Additionally, at step 806 the defective memory map is updated and the particular defective memory location giving rise to the memory defect event is added to the existing memory defect map. Following a system reset 808 the spare memory is cleared at 810 and the process returns to step 800 with the address remapping unit 704 mapping out any defective memory locations as indicated by the existing memory defect map. Thus, the memory defect map is continuously updated as new memory defect events occur. Because the defective memory information is mapped out, the system ignores any memory locations that are known to be defective. Consequently, the remapping resources that are dedicated to remapping a memory location known to be defective are no longer at risk and can be released and returned to use in the event a new error emerges. Because the memory defect map is continuously updated and any emerging memory defect locations are continuously added to the memory defect map, the demand on the system's remapping resources will be minimized.
Number | Name | Date | Kind |
---|---|---|---|
4209846 | Seppa | Jun 1980 | A |
4240143 | Besemer et al. | Dec 1980 | A |
4426688 | Moxley | Jan 1984 | A |
4479214 | Ryan | Oct 1984 | A |
5450576 | Kennedy | Sep 1995 | A |
5539697 | Kim et al. | Jul 1996 | A |
5588112 | Dearth et al. | Dec 1996 | A |
5666482 | McClure | Sep 1997 | A |
5671229 | Harari et al. | Sep 1997 | A |
5751641 | Petrosino | May 1998 | A |
5758056 | Barr | May 1998 | A |
5764878 | Kablanian et al. | Jun 1998 | A |
5774647 | Raynham et al. | Jun 1998 | A |
5862314 | Jeddeloh | Jan 1999 | A |
5867702 | Lee | Feb 1999 | A |
5905858 | Jeddeloh | May 1999 | A |
5986950 | Joseph | Nov 1999 | A |
5996096 | Dell et al. | Nov 1999 | A |
6035432 | Jeddeloh | Mar 2000 | A |
6052798 | Jeddeloh | Apr 2000 | A |
6125392 | Labatte et al. | Sep 2000 | A |
6154851 | Sher et al. | Nov 2000 | A |
6158025 | Brisse et al. | Dec 2000 | A |
6173382 | Dell et al. | Jan 2001 | B1 |
6237110 | Lin et al. | May 2001 | B1 |
6260127 | Olarig et al. | Jul 2001 | B1 |
6285607 | Sinclair | Sep 2001 | B1 |
6304989 | Kraus et al. | Oct 2001 | B1 |
6324657 | Fister et al. | Nov 2001 | B1 |
6460152 | Demidov et al. | Oct 2002 | B1 |
6499117 | Tanaka | Dec 2002 | B1 |
6499120 | Sommer | Dec 2002 | B1 |
6536005 | Augarten | Mar 2003 | B1 |
6600614 | Lenny et al. | Jul 2003 | B2 |
6601183 | Larson et al. | Jul 2003 | B1 |
6622269 | Ngo et al. | Sep 2003 | B1 |
6728907 | Wang et al. | Apr 2004 | B1 |
6820224 | Lin et al. | Nov 2004 | B1 |
6889305 | Adelmann | May 2005 | B2 |
7065630 | Ledebohm et al. | Jun 2006 | B1 |
7123051 | Lee et al. | Oct 2006 | B1 |
7246269 | Hamilton | Jul 2007 | B1 |
7251744 | Housty | Jul 2007 | B1 |
7269765 | Charlton et al. | Sep 2007 | B1 |
7272758 | Roohparvar | Sep 2007 | B2 |
7346755 | Pomaranski et al. | Mar 2008 | B2 |
7478285 | Fouquet-Lapar | Jan 2009 | B2 |
20010042225 | Cepulis et al. | Nov 2001 | A1 |
20020073353 | Fish et al. | Jun 2002 | A1 |
20020120826 | Venkatraman et al. | Aug 2002 | A1 |
20020108072 | Beng Sim et al. | Sep 2002 | A1 |
20020157048 | Roohparvar | Oct 2002 | A1 |
20020184445 | Cherabuddi | Dec 2002 | A1 |
20030005367 | Lam | Jan 2003 | A1 |
20030058711 | Benedix et al. | Mar 2003 | A1 |
20030095455 | Dono et al. | May 2003 | A1 |
20030145250 | Chin | Jul 2003 | A1 |
20030208654 | Krontz et al. | Nov 2003 | A1 |
20040034825 | Jeddeloh | Feb 2004 | A1 |
20040042293 | Ogino | Mar 2004 | A1 |
20040088614 | Wu | May 2004 | A1 |
20050022066 | Herbst | Jan 2005 | A1 |
20050120270 | Anand et al. | Jun 2005 | A1 |
20050149687 | Adelmann | Jul 2005 | A1 |
20060004942 | Hetherington et al. | Jan 2006 | A1 |
20060059383 | Roohparvar | Mar 2006 | A1 |
20060236165 | Cepulis et al. | Oct 2006 | A1 |
20070061637 | Ward et al. | Mar 2007 | A1 |
20070101238 | Resnick et al. | May 2007 | A1 |
20070136385 | Abrashkevich et al. | Jun 2007 | A1 |
20070136625 | Niijima et al. | Jun 2007 | A1 |
20070150777 | Sasaki | Jun 2007 | A1 |
20070174718 | Fouquet-Lapar | Jul 2007 | A1 |
20070217559 | Stott et al. | Sep 2007 | A1 |
20080229143 | Muraki | Sep 2008 | A1 |
20080247243 | Kang et al. | Oct 2008 | A1 |
Number | Date | Country |
---|---|---|
0704854 | Apr 1996 | EP |
2005-234744 | Sep 2005 | JP |
WO9802816 | Jan 1998 | WO |
9905599 | Feb 1999 | WO |
WO9905599 | Apr 1999 | WO |
9950748 | Oct 1999 | WO |
Number | Date | Country | |
---|---|---|---|
20090049351 A1 | Feb 2009 | US |