Patent Grant
8255645
This invention relates generally to computer systems, and more particularly, to improving the performance of computer systems by using non-volatile memory in conjunction with a long-term storage unit.
Certain storage devices are used on computer systems in order to provide persistent memory for the functioning of the computer system. For example, a magnetic hard disk drive assembly is well known in the art. However, such persistent memory has some drawbacks. It is time consuming to prepare the magnetic hard drive for reading or writing data. In order to do so, in most cases, it is necessary to physically initiate spinning of the disk, and to position a read/write head over the proper location.
The preparation for reading or writing from the storage devices is time- and power-consuming. Additionally, noise may be generated by such a magnetic hard drive memory and its components. Thus, there is a need for an improved memory for computer systems which will remedy some of these drawbacks.
New compositions and configurations of persistent storage devices may provide some improvements in performance related to the storage. However, simply using traditional techniques for accessing persistent storage will not provide the full benefit of such new compositions or configurations. Generally, an operating system is used to control the operations of the computer system. The operating system also mediates between other applications in the computer system and the hard disk. Thus, there is a need for methods such as application programming interfaces (APIs) to provide enhanced performance. Similarly, there is a need for systems which create new configurations and new control techniques for storage for use by a computer systems.
A persistent storage device in which one or more long-term storage media are included along with a non-volatile memory is used with an operating system providing or responsive to application program interfaces, commands, and interrupts which allow the operating system or an application program to effectively use the non-volatile memory in order to increase performance time and efficiency. While it is contemplated that the non-volatile memory be included physically with the long-term storage medium, it is also possible for the non-volatile memory to be separate from the long-term storage medium but to function along with it to provide persistent storage.
In one embodiment, application program interfaces (APIs) are exposed which allow for a request that the long-term storage medium be spun up or spun down. Other APIs allow for requests that the non-volatile memory be flushed or populated with data from specified addresses of the long-term storage medium. Still others allow data to be written directly to the long-term storage medium, allow data to be written as an atomic write, or allow data written to the non-volatile memory cache to be ignored rather than saved for writing to the long-term storage medium. Additionally, a request to find and give details about existing non-volatile memory available for such storage is provided for.
In one embodiment, the non-volatile memory can be used in one of two ways. In a first way, a cache is provided in non-volatile memory. This cache is used as a read cache for data read from the long-term storage medium and also as a write buffer for data being written to the long-term storage medium. In this way, reads and writes to the long-term storage medium, instead of occurring sporadically, may be clustered together, requiring fewer reads from, writes to, and preparations of the long-term storage medium.
A portion of the non-volatile memory can be owned by the operating system or another application directly. Certain logical sector addresses (LSAs) from the long-term storage medium are mapped to the non-volatile memory, and reads from or writes to these LSAs will be performed in the non-volatile memory. This mapping can occur alongside the caching in a non-volatile memory portion described above.
Other features of the invention are described below.
The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings example constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:
In the description that follows, the term “NV memory” will be used to refer to solid state non-volatile memory. NV memory means any type of memory that retains its data when power is removed and that can be erased and reprogrammed with new data. The NV memory may include battery-backed up memory. The NV memory may be located in a computer as a separate component of the computer such as a personal computer slot card or as a component in system memory. Alternatively, it could be a component of a persistent storage device such as a hard drive, in a docking station of a notebook device and the like. On mobile systems, the track buffer memory the disk drives have can be used (i.e., the invention can also be implemented using the track buffer memory).
Future disks for mobile systems may draw from battery power to keep its memory alive without actually drawing power to keep the disk spinning. The NV memory may store file data, file metadata, as well as known disk sectors such as the boot sector and partition tables. During power down or entry into a hibernate mode, the computer system determines the static and dynamic configuration data to be stored in NV memory based on a history of prior uses. Data is also stored in the NV memory during system operation to reduce the number of times the disk drive is spun up. For mobile PCs and the like, reducing the number of times the disk drive is spun up improves user experience because power is reduced, thereby allowing smaller and lighter mobile PCs and the like that last longer on a given battery capacity. It also reduces the need to run noisy, high speed fans that are loud and annoying to the user.
Turning to the drawings, wherein like reference numerals refer to like elements, the invention is illustrated as being implemented in a suitable computing environment. Although not required, the invention will be described in the general context of computer-executable instructions, such as program modules, being executed by a personal computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multi-processor systems, microprocessor based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
With reference to
Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the personal computer 110, although only a memory storage device 181 has been illustrated in
When used in a LAN networking environment, the personal computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the personal computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
In the description that follows, the invention will be described with reference to acts and symbolic representations of operations that are performed by one or more computers, unless indicated otherwise. As such, it will be understood that such acts and operations, which are at times referred to as being computer-executed, include the manipulation by the processing unit of the computer of electrical signals representing data in a structured form. This manipulation transforms the data or maintains it at locations in the memory system of the computer, which reconfigures or otherwise alters the operation of the computer in a manner well understood by those skilled in the art. The data structures where data is maintained are physical locations of the memory that have particular properties defined by the format of the data. However, while the invention is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that various of the acts and operation described hereinafter may also be implemented in hardware.
Inclusion of NV Memory in the Computer 110
Turning now to
Turning now to
Operating System and Host Application Use of NV Memory
With reference again to
First a detection interface is provided. OS 134 can detect whether there is an NV memory 200, and the size of the NV memory. This functionality is exposed as an interface which the application programs 135, and other program modules 136 can use in order to determine if NV memory 200 exists in the computer 110. Additionally, OS components, such as file systems or other object stores, can use the detection interface to determine the existence and size of NV memory 200 on the computer 110. Other information regarding the NV memory 200 may also be provided such as usage information or type information. This information may be useful because certain NV memories have limited lifespans, and this may affect the usage of the NV memory 200 in certain situations.
In order to read from or write to a disk 304 in disk assembly 302, the disk must be spun up, and the read/write head 306 must be moved to the appropriate location by spindle/armature assembly. This preparatory action takes time and causes a delay before data can be read from or written to disk assembly 302. The preparatory action in writing to the disk 304 will be referred to as spinning up the disk, even though it encompasses moving the read/write head 306 as well. Indeed, while the disk is pictured as a rotating media, it is contemplated that in a persistent storage device 300, a NV memory 200 may be included along with another form of the long-term storage medium (other than disk assembly 302) which requires preparatory action before data can be written to or from the memory. Any preparatory action for the use of the long-term storage medium on the persistent storage device 300 will be known as “spin up” or “spinning up” the memory, even though it is contemplated that there may be additional preparatory actions, or even that an actual spinning of a rotating medium may not be involved. Because an application or the operating system 134 itself may recognize in advance of a write to the persistent storage device 300, that a significant probability exists that such a write requiring a spin up of the long-term storage medium on that device 300 will occur, delays causes by the need to wait for the spin up of long-term storage medium can be obviated through the use of an interface which allows an application or the operating system 134 to request a spin up of the long-term storage medium.
Similarly, a spin down interface is also provided. In order to save power consumption, if no writes are being made to the disk assembly 302 of persistent storage device 300, then the spinning of the disk 304 may be halted. Again, while the persistent storage device 300 is shown as including a rotating medium, where an actual spin down will reduce power consumption, other forms of long-term storage media on the persistent storage device 300 aside from NV memory 200 are contemplated, and such long-term storage media may have actions analogous to the spin down of the disk assembly 302, in which some benefit is gained by ceasing the action which allows immediate or relatively swift reads and writes to that memory. Such cessation of an action may not actually include a physical spinning down of a rotating medium, however, such cessations are contemplated by the “spin down” or “spinning down” referred to herein.
The spin down and spin up actions may be performed at less than their maximum speeds. Performing such operations at slower speeds can lessen the acoustic noise associated with these actions and lessen any associated spikes in power consumption. Because the spin up and spin down (or other preparatory actions for the long term storage medium) can be performed in advance of an absolute need for such actions, these advantages may be obtained without a performance impact. When a disk is spun up slowly, rather than quickly, the disk will be available when it is fully spun up, but the effects on the user and the rest of the system are minimized.
Some or all of the NV memory 200 may be used as a write cache for the disk assembly 302 of a persistent storage device 300. In such a case, an interface is provided for the situation in which an application or the operating system 134 may determine that for performance reasons, the NV memory 200 should be flushed to the other memory in the persistent storage device 300. This interface flushes the NV memory 200 to the long-term storage medium.
Different portions of NV memory 200 may be marked with different priorities. For example, an area of NV memory 200 may be “pinned” or marked with a high priority should be maintained in NV memory 200 rather than being flushed to long-term storage medium preferably to other areas of NV memory 200 which are not pinned or marked in this way. One embodiment of the invention allows one of a number of priorities to be assigned to areas in NV memory 200. For example, there may be three priorities, a highest priority (or “pinned’ memory or “priority 1” memory), a second priority (“priority 2”) and a lowest priority (or “priority 3”). Where space is needed in the NV memory 200, the lowest priority memory is flushed to long-term storage medium before higher priority memory areas will be flushed. Thus, according to one embodiment of the invention, several interfaces options for flushing the NV memory 200 cache may be presented—e.g., one which flushes the entire cache, one which flushes only lower-priority areas of the cache, or one which flushes all areas of the cache with a priority equal to or less than a priority specified in call to the interface.
As another performance improvement, because data written to the NV memory 200 may later be deleted, an interface is presented which allows the OS 134 or an application to signal to the NV memory 200 that certain data written to the NV memory 200 is no longer required, and can be discarded from the NV memory 200 write cache. In this way, when the memory is flushed, the discarded areas will not be written to the long-term storage medium, and when a read is performed on the discarded area, an error or random data may be returned.
This interface can be used, for example, in order to manage transactions. Often transaction logs contain intermediate data which is not required to be stored long term. For example, in one case, when a transaction occurs, meta-data about the transaction is first committed to the log. If this log is stored in NV memory 200, the write will not require a spinning up of the disk. When the transaction is completed and the changes committed, the stored meta-data about the transaction is changed or deleted to reflect the completed transaction. If, however, the transaction is interrupted before it can be completed and committed, the data in the NV memory 200 will persist and thus can be used to determine what transaction was occurring and solve problems regarding such interrupted transactions.
In another example, this interface can be used to avoid flushing to disk any data or metadata related to temporary files. Initially, these files and their metadata get created in the NV memory 200. When the files are deleted, the OS 134 or an application may signal NV memory 200 that the file data and metadata written to the NV memory 200 is no longer required, and can be discarded from the NV memory 200 write cache.
A NVM circumvention interface is also provided. In certain situations, use of the NV memory may not be efficient for read or write operations. With reference again to
In one embodiment, an interrupt is sent from the persistent storage device 300 to the host computer 110 when the disk controller in the persistent storage device 300 is preparing to or actually spinning up the disk assembly 302. This interrupt may be transmitted to the operating system 134 or its components or to an application. Upon receipt of such an interrupt, a recipient which is properly programmed to act opportunistically can ensure that data is moved from the NV memory 200 to the long-term storage medium or from the long-term storage medium to the NV memory 200, as the long-term storage medium is soon to be spun up and ready for such movements. This reduces the number of long-term storage medium spin-ups and therefore reduces disk drive power consumption. Additionally on receipt of the interrupt indicating that the memory is spinning or spun up, the OS can use the NVM circumvention interface to flush any non-persistent write buffers or caches directly to the long-term storage medium.
Additionally, OS components and applications may use an atomic write interface which allows a write to the persistent storage device 300 to be treated as atomic. All data to be written atomically is stored in the NV memory 200. When this is completed, the persistent storage device ensures that all data to be written atomically is written to long-term storage medium. If a failure occurs before all of the data to be written atomically is stored in the NV memory 200, an error is returned, and the data which has been received is discarded. If, after the storage on the NV memory 200 is completed, the atomic write fails due to a system or power failure, the failure is detected when the system restarts, and the atomic set of data stored in the NV memory is rewritten to the long-term storage medium. This allows improved performance in applications and settings where atomic writes of large data are preferable, e.g. in database applications, since it does not require these applications to deal with the problem known in the art as “torn writes”.
In one embodiment, the operating system 134, its components, or applications use the NV memory 200 to store specific files or objects that are used regularly. Thus more expensive writes/reads from long-term storage medium are avoided. For example, database transaction logs, file system metadata, and other metadata are stored in NV memory 200. Where a priority scheme is being used for assigning different priority to areas in NV memory 200 storing data, in one embodiment, such frequently-accessed files are accorded a high priority, which further helps to avoid expensive writes/reads to/from the long-term storage medium.
Partitioning of the NV Memory
In one embodiment, the NV memory 200 includes a partition which allows a portion of the NV memory 200 to be used exclusively by the operating system. One implementation of this is to allow the operating system 134 to partition the NV memory 200, and to have an OS partition of the NV memory 200 which is controlled directly by the disk controller firmware with input from the operating system.
Thus, through the disk controller, the OS 134 requests the population of the NV memory 200 cache with specific sectors that it are likely to be needed next. For example, these sectors are the sectors which are needed or are thought likely to be needed at the time of the next boot, or when the system resumes from hibernation. As a further example, these sectors are sectors that the OS 134 predicts it will need in the near future.
Thus, in such an embodiment, each time the long-term storage medium is spun up the OS can repopulate the OS partition of the read cache in the NV memory 200 by sending a list of logical sector addresses (LSAs) to the disk drive controller. This list can include priority information to be used according to a priority scheme as described above to indicate how readily the disk drive controller will overwrite the read cache data with write buffering data.
Within the OS 134, a mechanism is provided to map a specific set of LSAs to the NV memory 200. This allows a section of the NV memory 200 to be directly under the OS 134's control. Reads and writes to these LSAs will then always access the NV memory 200. The data in these LSAs will not be flushed to the storage unit unless the NV memory is reconfigured by the operating system. In one embodiment, in this section of NV memory 200, the OS 134 stores “black box recorder information,” i.e. a recent history of operations that is used to diagnose system failures. The OS 134 stores the boot recovery console and files required for safe boot so that the system can still boot and diagnose mechanical disk failures. It may also store a possibly compressed package of files required for the next boot to be used in place of or in addition to the regular representation of system files.
The interfaces and commands as described above are set forth in the following Table 1:
Copy-on-Write Functionality
Databases and database products, among other applications and products, may use copy-on-write functionality in order to reduce the consumption of resources such as time and memory. Copy-on-write allows previous versions of data to be made available. This is useful because, in addition to a current version of the information stored in, for example, a database, previous versions of the information may be useful to a user.
Without copy-on-write, one way to provide information on previous versions of data is to make a complete copy of the database at a point in time which may be of interest to a user. When this occurs, all files associated with the database are stored. However, this technique is space intensive, because for a database which is stored in a certain amount of storage space, each copy will also require that amount of storage space. This approach may also be time consuming, as the copy itself involves movement of lots of data.
Thus, instead, changes from the original version may be stored. Where NV memory 200 is available, it can be used for performing copy-on-write activities. In a first implementation of copy-on-write, the original data which is to be changed is stored in the system memory 130. Before it is updated, then, a copy must be written to stable storage, in order to have the unchanged version of the data available. Where NV memory 200 is available, such storage may be to the NV memory 200. This allows the storage of the unchanged copy to be performed quickly. As described above, this copy may be moved to the disk storage at a later point. Database systems using block-oriented caching can use this to reduce time due to memory writes.
In a second copy-on-write implementation, the original version may be stored in a long-term storage medium. In such a case, if the data is located in the NV memory 200, an additional copy may be made in NV memory 200 before the write occurs. If the data is not stored in the NV memory, then the original stored copy may be treated as the archive copy—the copy which stores the unchanged version. The NV memory 200 stores the changed version. When this version is flushed from NV memory 200 or otherwise moved to the disk, the version will be written to a new location in memory 200, since the original stored copy on disk is now the archive copy of the data before changes.
Defragmentation Using NV Memory
Large data stores, e.g. file systems and databases, through constant storage and deletion of data may exhibit a condition known as fragmentation. This occurs when large ranges of free memory on a storage device become more and more sparse, and may lead to performance degradation. In order to correct this, defragmentation is used. Defragmentation processes reunite files in successive address spaces. In order to perform defragmentation, data files are moved within physical memory locations on the disk to create contiguously stored files. Thus, temporary storage locations are used; as the space occupied by a first file is used by a second file, the first file must be stored in some location so it is not lost.
In one embodiment, NV memory is used as a temporary storage location during defragmentation. Data is written to the NV memory. The location of other data is changed in order to increase the contiguousness of the storage of the other data. Then the data from the NV memory is written to the storage device being defragmented. When the data which has been temporarily stored is restored to the storage device (such as the hard disk of a computer system) the temporary copy is removed from NV memory. Thus defragmentation can occur without requiring the use of the long-term storage medium and the associated costs of such use for storing temporary data.
Control over the Persistent Storage Device
As shown in
In order to begin use of the persistent storage device 300, the operating system 134 queries the storage unit configuration, as described above, to determine whether a NV memory 200 is available and, if so, size and other parameters of the NV memory 200, such as type, utilization history, etc. Then a determination is made regarding how the NV memory 200 will be utilized.
Utilization of the NV memory 200 may be controlled in two ways. First, some portions of NV memory 200 may be under the control of the storage unit. Second, some portions of the NV memory 200 may be under the direct control of the OS 134. As discussed above, when a portion of the NV memory 200 is under direct control of the OS, that portion is used to map a specific set of LSAs. Reads and writes to these LSAs will then always access the NV memory 200 at the mapped portions. The data in these LSAs will not be flushed to the storage unit unless the NV memory is reconfigured by the operating system.
The portion of the NV memory 200 which is not under direct operating system control is used as a cache. This cache portion serves double duty as a read cache and as a write buffer. When the write buffer is flushed to the disk the OS opportunistically re-populates the NV memory 200 with data from the disk to serve as a read cache. This cache data is overwritten with write buffer data. Eventually the read cache is completely overwritten by the write buffer data, at which time the buffer is full, the storage unit controller spins up the disk, flushes the buffer data to the disk, repopulates the read cache, and spins down the disk.
The use of an NV memory with both a cache portion and a mapped portion is shown in
The mapped portion 510 is mapped to specific LSAs. Thus, as shown by arrow 550, when these LSAs are read from or written to, these reads and writes are directly from the mapped portion 510. Data in the mapped portion 510 does not get flushed to the long-term storage medium 430, nor does long-term storage medium 430 provide data to the mapped portion. The only exception to this is upon remapping. As shown by arrow 560, when a new mapping is created, data from the former mapping is copied to the long-term storage medium 430 and data from the disk for the new LSAs mapped is copied to the NV memory 200 (specifically, to the mapped portion 510.)
Control of Cache Portion 500
The control of the cache portion is defined by the state diagram shown in
The disk drive controller firmware 440 reduces power consumption and improves reliability and performance by using the NV memory 200 in certain cases rather than using the slower disk 430. The disk drive controller 440 receives commands from the OS 136 to populate the cache portion 500 of the NV memory 200 with data from a specified list of logical sector addresses (LSAs). The list of LSAs also includes a prioritization of the sectors where highest priority sectors are least likely to be removed from the cache and lowest priority sectors are most likely to be removed. Once the cache 500 is populated, the disk 430 is spun down and the cache 500 is used as a write buffer. Sectors cached for read are overwritten as the buffer fills up according to their priority. The disk is only spun-up when there is a read cache miss, when the write buffer is full, or when an explicit spin-up command is received from the OS 134. In this way the disk 430 will remain off for long periods of time relative to the time it is turned on, thus reducing power and improving reliability. The highest priority LSAs are permanently pinned in the NV memory 200 cache until told otherwise by the OS 134.
The operations in the boot state 600 are shown in
After this state is complete, the running state 610 is entered, and the OS sends a command to flush and repopulate the cache with specified LSAs. The operations of the running state 610 are shown in
When a command is received to shut down, the shutdown state 620 is entered. The operations of the shut-down state 620 are shown in
Other forms of shut-down or analogous pauses in functioning (for example, stand by and hibernate) also function according to the methods shown in
Again, as described above, the OS 134 and applications (via the OS 134) may give other hints to the device controller 440 to help it determine when to spin up or spin down the disk, and conversely, if the controller FW must spin the disk up for any reason, it sends an interrupt to the OS 134 indicating the disk is spinning up. The operating system and applications can then take advantage of this situation to write non-critical data that has been cached in volatile working memory to the storage unit.
In one embodiment, the controller 440 firmware also utilizes the benefits realized from NV memory 200 to lower acoustic noise in hard drive storage units. By setting the write buffer threshold low enough, the controller 440 is able to spin up more slowly and take longer to flush the write buffer to the disk 430, reducing acoustic noise from the spindle and the heads to seek servos. This technique also reduces the peak current draw from the power supply. The controller 440 firmware also takes advantage of relatively large amounts of data in the buffer to place data on the disk in contiguous blocks and avoid fragmentation when flushing the data to disk.
The exact state of the cache 500 is known only by the controller 440. The operating system can get a snapshot of it by querying the controller 440. At any point in time the operating system 134 may choose to flush the cache 500 and start with a fresh set of sectors it believes will be required in the near future by sending a command (transition 613 in
In one embodiment, in the absence of a specific command from the OS 134 to populate the cache portion 500 with files by presenting a list of LSAs (e.g. those required to boot or resume from hibernate on transition 615, or generally those given upon a transition from boot state 600 or in running state 610) the controller could do its own prefetching from disk to NV memory 200 by monitoring disk IOs immediately after boot or S4 resume. These IOs represent the most likely data to be required on the next boot or S4 resume. Once this data is collected by the controller 440 it is stored in a table in NV memory 200. On next shutdown or hibernate, the controller 440 uses this data to populate the NV memory 200 from disk before shutting down or hibernating.
Control of Mapped Portion 510
The operating system directly controls the mapped portion 510 of NV memory 200. For this portion, the operating system defines specific logical sector addresses that must map to the mapped portion 510. This gives the operating system direct control of the data stored in the NV memory 200. Such control, in one embodiment, may also be given to other applications.
One way in which this can be accomplished is where operating system 134 creates a portion of NV memory 200 that maps or shadows a specific but not necessarily contiguous set of LSAs. To create this portion the OS sends a command to the disk controller to flush the entire NV memory 200 which moves all modified data in the write buffer and in a previous mapping to the long-term storage medium 430. It then sends a command to map a list of LSAs to the mapped portion 510 of the NV memory 200. The controller 440 copies sectors from the disk to the NV memory 200 and maintains them there until told otherwise by the operating system 136. If the logical sector addresses sent to the persistent storage device 300 for mapping extend beyond the current address space of the disk 430 then these are appended to the end of the disk's address space. When a remapping occurs the OS 134 will need to copy the data in these extended addresses to locations in the disk's address space to avoid losing data. The operating system is in direct control of these mapped sectors in NV memory 200
The OS 134 may periodically flush the mapped portion 510 to disk 430 and map a new set of LSAs to the mapped portion 510. This occurs as shown in
As an alternative to this mapping, the NV memory may also be configured as a separate partition or logical volume of the persistent storage device 300. Continuous logical sectors are then under direct control of the operating system 136 as described above.
Self-Descriptive Memory Portion for the Persistent Storage Device 300
In addition to a cache portion 500 and a mapped portion 510 as shown in
In one embodiment, such descriptive information includes label information, the number of bad sectors in the long-term storage medium 430, statistical data regarding the number of sectors written to or from in a certain amount of time, the number of spin ups or spin downs of the disk in a certain amount of time, and the number of hours the long-term storage medium has run.
In one embodiment, this self-descriptive memory portion is read by specific interfaces which allow OS components or an application to access the memory. In another embodiment, the persistent storage device 300 includes a display. For example, an LCD display may be included in the persistent storage device 300. When a certain query is made to the persistent storage device 300, either via the computer 110 or directly (e.g. by pressing a button on the persistent storage device 300), data from the self-descriptive memory portion is displayed.
In one embodiment, the OS or an application use the information stored in the self-descriptive memory to determine when the storage device 300 is nearing its life expectancy and the data stored on said storage device 300 needs to be transferred to a new storage device.
Information may also be stored which allows the NV memory 200 to be used as a “black box” recorder, which stores data concerning the operation of the computer. In case of a failure, such as an abnormal shut-down, information regarding the operation of the computer is stored and can be retrieved in order to analyze the failure. Such information may include process information regarding processes running in said computer system; thread information regarding threads running in said computer system; data accesses; and device accesses. Similarly to a black box recorder in an airplane, a limited amount of space may be allotted to this operational information, and when more information is collected than can fit in that space, previously-stored operational information is overwritten with newer information.
Wear Leveling
Certain NV memory technologies suffer from wear-out after too many erase cycles. In order to delay the onset of such wear-out, the controller 440, in one embodiment, balances the erasure of all areas of the NV memory 200 in order to ensure that approximately equal use is made of each area. The controller 440 changes the physical locations used within the NV memory to avoid wearing out NV memory blocks associated with disk sectors that are written to frequently. In one embodiment, this requires a certain amount of overhead to be used to guarantee that there is always space available in the mapped portion to do the wear leveling. For example, if 1 MB of sectors are set aside for mapped portion 510, the disk controller may actually set aside 1.5 MB to allow the wear leveling to work properly.
Conclusion
It is noted that the foregoing examples have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the present invention. While the invention has been described with reference to various embodiments, it is understood that the words which have been used herein are words of description and illustration, rather than words of limitations. Further, although the invention has been described herein with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed herein; rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may effect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention in its aspects.
This application is a continuation application of U.S. patent application Ser. No. 12/627,710, filed Nov. 30, 2009, which is now U.S. Pat. No. 8,041,904, issued Oct. 18, 2011, which is incorporated herein by reference in its entirety. U.S. Pat. No. 8,041,904 is a divisional application of U.S. patent application Ser. No. 10/837,986, filed May 3, 2004, which is now U.S. Pat. No. 7,644,239, issued Jan. 5, 2010, which is incorporated herein by reference in its entirety. This application is related to the following U.S. patents: U.S. Pat. No. 7,082,495, issued Jul. 25, 2006 entitled “Method And Apparatus To Reduce Power Consumption And Improve Read/Write Performance Of Hard Disk Drives Using Non-Volatile Memory”; U.S. Pat. No. 7,017,037, issued Mar. 21, 2006 entitled “Apparatus And Method To Decrease Boot Time And Hibernate Awaken Time Of A Computer System”; and U.S. Pat. No. 7,036,040, issued Apr. 25, 2006 entitled “Improved Reliability Of Diskless Network-Bootable Computers Using Non-Volatile Memory Cache.”
| Number | Name | Date | Kind |
|---|---|---|---|
| 4476526 | Dodd | Oct 1984 | A |
| 4945474 | Elliott et al. | Jul 1990 | A |
| 4972316 | Dixon et al. | Nov 1990 | A |
| 4979108 | Crabbe, Jr. | Dec 1990 | A |
| 5307497 | Feigenbaum et al. | Apr 1994 | A |
| 5394531 | Smith | Feb 1995 | A |
| 5420998 | Horning | May 1995 | A |
| 5463739 | Albaugh et al. | Oct 1995 | A |
| 5652857 | Shimoi et al. | Jul 1997 | A |
| 5720029 | Kern et al. | Feb 1998 | A |
| 5740434 | Eastep | Apr 1998 | A |
| 5751932 | Horst et al. | May 1998 | A |
| 5754782 | Masada | May 1998 | A |
| 5764877 | Lomet et al. | Jun 1998 | A |
| 5806074 | Souder et al. | Sep 1998 | A |
| 5897638 | Lasser et al. | Apr 1999 | A |
| 5900870 | Malone et al. | May 1999 | A |
| 5943692 | Marberg et al. | Aug 1999 | A |
| 6018433 | Thayne et al. | Jan 2000 | A |
| 6018746 | Hill et al. | Jan 2000 | A |
| 6047291 | Anderson et al. | Apr 2000 | A |
| 6073232 | Kroeker et al. | Jun 2000 | A |
| 6098075 | Becraft, Jr. et al. | Aug 2000 | A |
| 6101601 | Matthews et al. | Aug 2000 | A |
| 6108004 | Medl | Aug 2000 | A |
| 6112024 | Almond et al. | Aug 2000 | A |
| 6199195 | Goodwin et al. | Mar 2001 | B1 |
| 6209088 | Reneris | Mar 2001 | B1 |
| 6240414 | Beizer et al. | May 2001 | B1 |
| 6247026 | Waldo et al. | Jun 2001 | B1 |
| 6314433 | Mills et al. | Nov 2001 | B1 |
| 6321234 | Debrunner | Nov 2001 | B1 |
| 6338056 | Dessloch et al. | Jan 2002 | B1 |
| 6338126 | Ohran et al. | Jan 2002 | B1 |
| 6360330 | Mutalik et al. | Mar 2002 | B1 |
| 6370534 | Odom et al. | Apr 2002 | B1 |
| 6370541 | Chou et al. | Apr 2002 | B1 |
| 6401093 | Anand et al. | Jun 2002 | B1 |
| 6438750 | Anderson | Aug 2002 | B1 |
| 6454159 | Takushima | Sep 2002 | B1 |
| 6477564 | Freyssinet et al. | Nov 2002 | B1 |
| 6505205 | Kothuri et al. | Jan 2003 | B1 |
| 6519597 | Cheng et al. | Feb 2003 | B1 |
| 6539456 | Stewart | Mar 2003 | B2 |
| 6542904 | Crus et al. | Apr 2003 | B2 |
| 6556983 | Altschuler et al. | Apr 2003 | B1 |
| 6560702 | Gharda et al. | May 2003 | B1 |
| 6567889 | Dekoning et al. | May 2003 | B1 |
| 6578046 | Chang et al. | Jun 2003 | B2 |
| 6615313 | Kato et al. | Sep 2003 | B2 |
| 6640278 | Nolan et al. | Oct 2003 | B1 |
| 6671699 | Black et al. | Dec 2003 | B1 |
| 6671757 | Multer et al. | Dec 2003 | B1 |
| 6684229 | Luong et al. | Jan 2004 | B1 |
| 6694336 | Multer et al. | Feb 2004 | B1 |
| 6714935 | Delo | Mar 2004 | B1 |
| 6718361 | Basani et al. | Apr 2004 | B1 |
| 6738789 | Multer et al. | May 2004 | B2 |
| 6751658 | Haun et al. | Jun 2004 | B1 |
| 6757696 | Multer et al. | Jun 2004 | B2 |
| 6760736 | Waldo et al. | Jul 2004 | B2 |
| 6772178 | Mandal et al. | Aug 2004 | B2 |
| 6871271 | Ohran et al. | Mar 2005 | B2 |
| 7017037 | Fortin et al. | Mar 2006 | B2 |
| 7036040 | Nicholson et al. | Apr 2006 | B2 |
| 7065627 | Dayan et al. | Jun 2006 | B2 |
| 7082495 | DeWhitt et al. | Jul 2006 | B2 |
| 7143120 | Oks et al. | Nov 2006 | B2 |
| 7366740 | Sleeman et al. | Apr 2008 | B2 |
| 7644239 | Ergan et al. | Jan 2010 | B2 |
| 7814261 | Lee | Oct 2010 | B2 |
| 20010047462 | Dimitroff et al. | Nov 2001 | A1 |
| 20020004876 | Timmer et al. | Jan 2002 | A1 |
| 20020091702 | Mullins | Jul 2002 | A1 |
| 20020143521 | Call | Oct 2002 | A1 |
| 20020152422 | Sharma et al. | Oct 2002 | A1 |
| 20020156970 | Stewart | Oct 2002 | A1 |
| 20020171966 | Ottesen et al. | Nov 2002 | A1 |
| 20020198891 | Li et al. | Dec 2002 | A1 |
| 20030101320 | Chauvel et al. | May 2003 | A1 |
| 20030154337 | Ohno et al. | Aug 2003 | A1 |
| 20030158839 | Faybishenko et al. | Aug 2003 | A1 |
| 20030177305 | Hetrick | Sep 2003 | A1 |
| 20030191916 | McBrearty et al. | Oct 2003 | A1 |
| 20030212660 | Kerwin | Nov 2003 | A1 |
| 20030212857 | Pacheco et al. | Nov 2003 | A1 |
| 20040003003 | McCartney et al. | Jan 2004 | A1 |
| 20040003223 | Fortin et al. | Jan 2004 | A1 |
| 20040015504 | Ahad et al. | Jan 2004 | A1 |
| 20040024795 | Hind et al. | Feb 2004 | A1 |
| 20040034765 | James | Feb 2004 | A1 |
| 20040044776 | Larkin | Mar 2004 | A1 |
| 20040059747 | Olarig et al. | Mar 2004 | A1 |
| 20040093463 | Shang | May 2004 | A1 |
| 20040107200 | Sjogren et al. | Jun 2004 | A1 |
| 20040174631 | Tanaka et al. | Sep 2004 | A1 |
| 20050149750 | Lisanke et al. | Jul 2005 | A1 |
| 20050172067 | Sinclair | Aug 2005 | A1 |
| 20050239494 | Klassen et al. | Oct 2005 | A1 |
| 20050262378 | Sleeman et al. | Nov 2005 | A1 |
| 20060106889 | Mannby | May 2006 | A1 |
| 20070073764 | Oks et al. | Mar 2007 | A1 |
| 20120047323 | Sareen et al. | Feb 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1465009 | Dec 2003 | CN |
| 63-247853 | Oct 1988 | JP |
| 03-294942 | Dec 1991 | JP |
| 4-246746 | Sep 1992 | JP |
| 5-62329 | Mar 1993 | JP |
| 5-94353 | Apr 1993 | JP |
| 5-225066 | Sep 1993 | JP |
| 6-83708 | Mar 1994 | JP |
| 06-231043 | Aug 1994 | JP |
| 6-236351 | Aug 1994 | JP |
| 7-504527 | May 1995 | JP |
| 7-253935 | Oct 1995 | JP |
| 10-091488 | Sep 1996 | JP |
| 8-263380 | Oct 1996 | JP |
| 09-106366 | Apr 1997 | JP |
| 10-154101 | Jun 1998 | JP |
| 2001-27967 | Jan 2001 | JP |
| 2001-67258 | Mar 2001 | JP |
| 2001-250315 | Sep 2001 | JP |
| 2002-259186 | Sep 2002 | JP |
| 479194 | Mar 2002 | TW |
| 502165 | Sep 2002 | TW |
| WO 9318461 | Sep 1993 | WO |
| WO 0111486 | Feb 2001 | WO |
| WO 0157675 | Aug 2001 | WO |
| WO 0175581 | Oct 2001 | WO |
| WO 0201364 | Jan 2002 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20120005422 A1 | Jan 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10837986 | May 2004 | US |
| Child | 12627710 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12627710 | Nov 2009 | US |
| Child | 13231088 | US |
