Computing devices may include memory devices having memory space designated for storing copies of data already being stored in the memory device. Allowing the memory space to be used for redundant purposes allows data to be recovered if the primary storage space for the data in the memory device experiences a memory error.
The invention described herein is illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.
While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific exemplary embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
In the following description, numerous specific details such as types and interrelationships of system components and logic partitioning/integration choices are set forth in order to provide a more thorough understanding of the present disclosure. It will be appreciated, however, by one skilled in the art that embodiments of the disclosure may be practiced without such specific details. In other instances, control structures, gate level circuits and full software instruction sequences have not been shown in detail in order not to obscure the invention. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.
References in the specification to “one embodiment”, “an embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Embodiments of the invention may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the invention may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; and others.
Referring now to
Each of the processors 102, 104 are communicatively coupled to the chipset 106 via a number of signal paths 110. Signal paths 110 may be embodied as any type of signal paths capable of facilitating communication between the processors 102, 104 and the chipset 106. For example, the signal paths 110 may be embodied as any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The chipset 106 includes a memory controller hub (MCH) or northbridge 112, an input/output controller hub (ICH) or southbridge 114, and a firmware device 116. The firmware device 116 is communicatively coupled to the input/output controller hub 114 via a number of signal paths 118. Similar to the signal paths 110, the signal paths 118 may be embodied as any type of signal paths capable of facilitating communication between the input/output controller hub 114 and the firmware device 116 such as, for example, any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The firmware device 116 is illustratively embodied as a memory storage device for storing Basic Input/Output System (BIOS) data/programs and/or instructions and/or other information.
The MCH 112 is communicatively coupled to a memory device 120 via a number of signal paths 122. Again, similar to the signal paths 110, 118 described above, the signal paths 122 may be embodied as any type of signal paths capable of facilitating communication between the MCH 112 and the memory device 120 such as, for example, any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The memory device 120 may be embodied as dynamic random access memory devices (DRAM), synchronous dynamic random access memory devices (SDRAM), double-data rate dynamic random access memory device (DDR SDRAM), and/or other volatile memory devices. Additionally, although a single memory device is illustrated in
The chipset 110 is also communicatively coupled to a number of peripherals 108 via a number of signal paths 124. Again, similar to the signal paths 118, 122, the signal paths 124 may be embodied as any type of signal paths capable of facilitating communication between the chipset 106 and the peripherals 108 such as, for example, any number of wires, printed circuit board traces, via, bus, intervening devices, and/or the like. The peripherals 108 may include any number of peripheral devices including data storage devices, interfaces, and output devices. For example, as illustrated in
In one embodiment, the memory device 120 may be used for “memory mirroring,” which allows data to be stored in the memory device 120, as well as a copy of the stored data. Thus, if an error occurs with the stored data, the copy may be used so that no data is lost. However, in typical systems implementing “memory mirroring,” the memory is bifurcated such that half is used for storing data and the second half is automatically used for mirroring the first half.
Referring now to
During operation, the MCH 112 controls the flow of data to and from the DIMMs for data storage and retrieval. When memory mirroring is implemented, bank 2 may be used to mirror, e.g., copy and store, data stored in bank 1. When selective memory mirroring is implemented, selected portions of data stored in the DIMMs of bank 1 may be copied and stored in the DIMMs of bank 2. In one embodiment, data stored at a particular address (designated as A0-An in
The configuration of
At block 146, an amount of memory space is selected for memory mirroring from the amount of memory space determined to be available at block 144. In one embodiment, the selection of memory to be used for memory mirroring may be selected based upon powers of two allowing the MCH 112 to control the memory space selected accordingly. The selection of memory space to be used for memory mirroring may also be performed in various manners. For example, during an initial boot of a system, a system user may enter a setup mode of the system, such as I/O Device 131 of the computing device to provide a system user the ability to input the amount of memory to be used for memory mirroring. The input of the system user may be processed for control of the MCH 112 in order to control the appropriate memory for mirroring.
Referring now to
At block 160, the OS may request an amount of mirrored memory from the visible memory. In one embodiment, this request may be made by the OS via an application programming interface. At block 162, the BIOS programs may set up mirroring for the amount of memory requested by the OS. In one embodiment, this may be performed during runtime via a system management interrupt. In another embodiment, this may be performed during runtime.
At block 164, the BIOS programs may add memory to the operating memory, e.g., memory not used for mirroring but available during normal operation. At block 166, the OS may continue operation with critical areas protected through memory mirroring.
It should be appreciated that the routine of the flowchart 142 may be configured such that only a portion of available memory space is made available for mirroring to the OS, the non-available portion being included in non-mirrored memory space. If the OS requests more memory space that that made available, memory space may be removed from the non-mirrored memory space, a “hot remove,” and added to the portion of memory space made available for memory mirroring to the OS.
Referring now to
While the disclosure has been illustrated and described in detail in the drawings and foregoing description, such an illustration and description is to be considered as exemplary and not restrictive in character, it being understood that only illustrative embodiments have been shown and described and that all changes and modifications that come within the spirit of the disclosure are desired to be protected.
This application is a continuation of U.S. patent application Ser. No. 11/966,313, filed Dec. 28, 2007, now U.S. Pat. No. 7,949,850 the content of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4044333 | Auspurg et al. | Aug 1977 | A |
5488716 | Schneider et al. | Jan 1996 | A |
6000023 | Jeon | Dec 1999 | A |
6006307 | Cherukuri | Dec 1999 | A |
6175904 | Gunderson | Jan 2001 | B1 |
6591352 | Lambino et al. | Jul 2003 | B2 |
6701421 | Elnozahy et al. | Mar 2004 | B1 |
6820182 | Bauman et al. | Nov 2004 | B1 |
6848039 | Aaron et al. | Jan 2005 | B1 |
7036007 | Schelling et al. | Apr 2006 | B2 |
7062628 | Amano | Jun 2006 | B2 |
7107405 | Lovelace | Sep 2006 | B2 |
7213152 | Gafken et al. | May 2007 | B1 |
7302526 | Cartmell et al. | Nov 2007 | B1 |
7305668 | Kennedy et al. | Dec 2007 | B2 |
20020169987 | Meushaw et al. | Nov 2002 | A1 |
20020178352 | Lambino et al. | Nov 2002 | A1 |
20050138465 | Depew et al. | Jun 2005 | A1 |
20050210180 | Rothman et al. | Sep 2005 | A1 |
20060184740 | Ishikawa et al. | Aug 2006 | A1 |
20060206661 | Gaither | Sep 2006 | A1 |
20080005551 | Swanson et al. | Jan 2008 | A1 |
20080271054 | Allison et al. | Oct 2008 | A1 |
20090064274 | Zimmer et al. | Mar 2009 | A1 |
Entry |
---|
Tyson, Jeff, and Dave Coustan. “How RAM Works” Aug. 25, 2000. HowStuffWorks.com. <http://www.howstuffworks.com/ram.htm> Retrieved Jul. 25, 2013. |
Aiken et al. “Microsoft Computer Dictionary”. Microsoft Press 2002. Chapter 14: ‘M’, p. 423. <http://academic.safaribooksonline.com/book/communications/0735614954/m/ch14> Retrieved Jul. 25, 2013. |
Rothman, Michael A., et al., U.S. Appl. No. 11/771,994, filed Jun. 29, 2007, entitled “Method and Apparatus for Improved Memory Reliability, Availability and Serviceability”. |
Number | Date | Country | |
---|---|---|---|
20110173385 A1 | Jul 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11966313 | Dec 2007 | US |
Child | 13049094 | US |