Source: http://www.google.ca/patents/US8489815
Timestamp: 2018-01-23 11:25:03
Document Index: 731199551

Matched Legal Cases: ['§119', 'Application No. 2', 'Application No. 200680047384', 'Application No. 200510083792', 'Application No. 200510116208', 'Application No. 200960145878', 'Application No. 200980136912', 'Application No. 200980137190', 'Application No. 200980145878', 'Application No. 200980137190', 'Application No. 200680047384', 'Application No. 200510083792', 'Application No. 03022573', 'Application No. 03022573', 'Application No. 03022573', 'Application No. 05103690', 'Application No. 05103697', 'Application No. 05103697', 'Application No. 05103697', 'Application No. 05103697', 'Application No. 05109295', 'Application No. 09813565', 'Application No. 09813565', 'Application No. 09814983', 'Application No. 09826570', 'Application No. 09826570', 'Application No. 05109295', 'Application No. 05109295', 'Application No. 05109295', 'Application No. 06839426', 'Application No. 191502', 'Application No. 2008', 'Application No. 2008', 'Application No. 2005', 'Application No. 2005', 'Application No. 2005', 'Application No. 2005', 'Application No. 2011', 'Application No. 2003129662', 'Application No. 094114140']

Patent US8489815 - Managing cache data and metadata - Google Patents
Embodiments of the invention provide techniques for managing cache metadata providing a mapping between addresses on a storage medium (e.g., disk storage) and corresponding addresses on a cache device at which data items are stored. In some embodiments, cache metadata may be stored in a hierarchical...http://www.google.ca/patents/US8489815?utm_source=gb-gplus-sharePatent US8489815 - Managing cache data and metadata
Publication number US8489815 B2
Application number US 13/365,093
Filing date 2 Feb 2012
Priority date 15 Sep 2008
Also published as CN102216899A, CN102216899B, EP2353081A2, EP2353081A4, EP2353081B1, US8032707, US8135914, US20100070747, US20110314202, US20120173824, WO2010056571A2, WO2010056571A3
Publication number 13365093, 365093, US 8489815 B2, US 8489815B2, US-B2-8489815, US8489815 B2, US8489815B2
Inventors Mehmet Iyigun, Yevgeniy M. Bak, Michael Fortin, Mahlon David Fields, Cenk Ergan, Alexander Kirshenbaum
Patent Citations (312), Non-Patent Citations (164), Referenced by (5), Classifications (19), Legal Events (2)
Managing cache data and metadata
US 8489815 B2
Embodiments of the invention provide techniques for managing cache metadata providing a mapping between addresses on a storage medium (e.g., disk storage) and corresponding addresses on a cache device at which data items are stored. In some embodiments, cache metadata may be stored in a hierarchical data structure comprising a plurality of hierarchy levels. When a reboot of the computer is initiated, only a subset of the plurality of hierarchy levels may be loaded to memory, thereby expediting the process of restoring the cache metadata and thus startup operations. Startup may be further expedited by using cache metadata to perform operations associated with reboot.
a storage medium storing a plurality of data items at respective addresses;
a cache device also storing the plurality of data items at corresponding addresses and cache metadata providing a mapping between the address on the storage medium and the corresponding address on the cache device at which each data item is stored, the cache metadata being stored in a hierarchical data structure comprising a plurality of hierarchy levels;
store cache metadata on the cache device in response to a command to shut down or reboot the computer;
upon initiating a reboot of the computer, load only a subset of the plurality of hierarchy levels to the memory; and
verify that a first data item of the plurality of data items was not modified after storage of the first data item in the cache device.
2. The computer system of claim 1, wherein the at least one processor is programmed to verify that the first data item was not modified at least in part by verifying a consistency between generations of cache contents.
3. The computer system of claim 2, wherein the at least one processor is programmed to evict the first data item from the cache device if determined to belong to an inconsistent cache generation.
4. The computer system of claim 1, wherein the at least one processor is further programmed to verify that the first data item was not modified at least in part by:
associating a representation of at least a portion of the first data item with the first data item;
retrieving at least a portion of the first data item from the cache device;
re-generating the representation of at least a portion of the first data item based on the retrieved at least the portion of the first data item; and
compare the associated representation with the re-generated representation to determine whether the retrieved at least the portion of the first data item is authentic.
5. The computer system of claim 4, wherein the at least one processor is programmed to generate the associated representation when the first data item is first written to the cache device.
6. The computer system of claim 5, wherein the at least one processor is programmed to write the associated representation to the cache device.
7. The computer system of claim 6, wherein the at least one processor is programmed to write the associated representation at a location adjacent to a location at which the first data item is stored in the cache device.
8. The computer system of claim 6, wherein the at least one processor is programmed to store the associated representation in cache metadata for the first data item.
9. The computer system of claim 6, wherein the at least one processor is programmed to retrieve the associated representation from the cache device.
10. The computer system of claim 4, wherein the at least one processor is programmed to generate the associated representation to comprise a cyclic redundancy code (CRC) of the at least the portion of the first data item.
11. The computer system of claim 4, wherein the at least one processor is programmed to generate the associated representation using a cryptographic technique.
12. The computer system of claim 11, wherein the cryptographic technique comprises generation of a message authentication code (MAC) for the at least the portion of the first data item.
13. The computer system of claim 4, wherein the at least one processor is programmed to, if it is determined that the retrieved at least the portion of the data item is inauthentic, evict the inauthentic at least the portion of the data item from the cache device.
14. The computer system of claim 13, wherein the at least one processor is programmed to, if it is determined that the retrieved at least the portion of the data item is inauthentic, read the data item from the address on the storage medium.
15. The computer system of claim 1, further comprising an operating system comprising programmed instructions, wherein the at least one processor executes the programmed instructions of the operating system to verify that the first data item was not modified after storage of the first data item.
16. A method for use in a computer system comprising a memory, a storage medium storing a plurality of data items at respective addresses, and a cache device also storing the plurality of data items at corresponding addresses and cache metadata providing a mapping between the address on the storage medium and the corresponding address on the cache device at which each data item is stored, the cache metadata being stored in a hierarchical data structure comprising a plurality of hierarchy levels, the method comprising acts of:
storing cache metadata on the cache device in response to a command to shut down or reboot the computer;
upon initiating a reboot of the computer system, loading only a subset of the plurality of hierarchy levels to the memory; and
verifying that a first data item of the plurality of data items was not modified after storage of the first data item in the cache device.
17. At least one recording medium storing instructions encoded thereon that, when executed by a computer system comprising a memory, a storage medium storing a plurality of data items at respective addresses, and a cache device also storing the plurality of data items at corresponding addresses and cache metadata providing a mapping between the respective address on the storage medium and the corresponding address on the cache device at which each data item is stored, the cache metadata being stored in a hierarchical data structure comprising a plurality of hierarchy levels, cause the computer system to perform a method comprising acts of:
This application is a continuation of U.S. patent application Ser. No. 13/221,542, filed on Aug. 30, 2011, entitled “MANAGING CACHE DATA AND METADATA,” which is a continuation of U.S. patent application Ser. No. 12/271,400, now U.S. Pat. No. 8,032,707, filed Nov. 14, 2008, entitled “MANAGING CACHE DATA AND METADATA,” which claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application Ser. No. 61/097,079, filed Sep. 15, 2008, entitled “MANAGEMENT OF CACHE DATA AND METADATA.” Each of the foregoing documents is incorporated herein by reference in its entirety.
This invention relates to techniques for employing non-volatile memory devices, such as removable and non-removable non-volatile random access memory (NVRAM) devices.
Some conventional operating systems provide a capability to employ a non-volatile memory device (i.e., a peripheral device operable to provide auxiliary storage and/or memory to a computer, such as a flash memory USB drive) as a block or file-level cache for slower storage devices (e.g., a disk storage medium, or one or more storage devices accessible via a network), to improve the performance of the operating system and/or applications. In this respect, because read and write operations can be performed significantly faster from or to a non-volatile memory device (hereinafter referred to as a “cache device” for simplicity) than from or to a slower storage device, using a cache device to cache data stored on such a slower device offers opportunities to significantly improve the speed of input/output (I/O) operations of operating systems and/or applications. To this end, the Microsoft Windows Vista operating system, produced by Microsoft Corporation of Redmond, Wash., includes a feature known as ReadyBoost which allows users to employ cache devices to cache data also residing in a slower storage device (referred to hereinafter as “disk storage” or “disk” for convenience, although it should be understood that these terms refer generally to any storage mechanism(s) and/or device(s) to which I/O is typically performed more slowly than a cache device, including storage devices accessible via a network).
Employing a cache device to cache data stored on disk may be accomplished using a cache manager component, which in some implementations is a driver implemented in the operating system's I/O stack. FIGS. 1A-1B depict example high-level processes 10A-10B whereby a cache manager component 100 manages the caching of data to cache device 110. Cache device 110 may be coupled, using wired and/or wireless communications infrastructure and protocol(s), to a computer (not shown) on which cache manager 100 resides. For example, cache device 110 may be removable from the computer (e.g., comprise a flash memory USB drive), non-removable and/or accessible to the computer via one or more wired and/or wireless networks.
At the start of the process 10A (FIG. 1A), a write request is received by cache manager 100 specifying that data should be written to address X on disk storage (i.e., cached volume 120). Cache manager 100 processes the request by causing the data to be written to address X on cached volume 120 in operation 101, and also to address Y on cache device 110 in operation 102. Process 10B (FIG. 1B) includes operations performed thereafter when a read request is received specifying that the data stored at address X on cached volume 120 should be read. Cache manager 100 determines that the data is cached on cache device 110 at address Y, and causes the data at address Y to be read in operation 103. The data is then served from the cache device to satisfy the read request in operation 104.
The cache manager maintains a mapping of disk addresses (e.g., address X) to corresponding cache addresses (e.g., address Y) in metadata, and this “cache metadata” is usually employed in reading from or writing to the cache device. Typically, cache metadata is maintained in memory and accessed by the cache manager when I/O requests are received. As such, when a read request is received by the cache manager which is directed to disk offset X, the cache manager uses the cache metadata to determine that the data is also stored at cache offset Y, and to satisfy the request by causing the data to be read from cache offset Y rather than disk offset X. When a write request is received by the cache manager which is directed to disk offset X, the cache manager employs the cache metadata to determine whether the data at that disk address is also stored in cache. If so (e.g., if the data is stored at cache address Y), the cache manager may cause the data to be written to the appropriate address in cache, or evict the cache contents at that address. If not, the cache manager may cause the data to be written to cache, and may update the cache metadata so that future reads to disk offset X may instead be serviced from the data stored on cache.
Conventional operating systems are capable of supporting cache devices with relatively limited storage capacity. For example, the ReadyBoost feature of the Windows Vista operating system supports cache devices with up to a four gigabyte storage capacity. (At the time Windows Vista was released, the maximum storage capacity of cache devices was approximately two gigabytes). The storage capacity of cache devices has grown rapidly in recent years, with some cache devices providing a storage capacity of up to sixteen gigabytes, which may store the equivalent of thirty-two gigabytes of data when compressed.
Applicants have appreciated that cache devices having relatively larger storage capacity offer significant opportunity to improve the speed of I/O operations performed by operating systems and applications. Applicants have also appreciated that one reason conventional operating systems support cache devices with only relatively limited storage capacity is that cache contents must be repopulated when certain types of power transitions (e.g., standby, hibernate (or equivalent modes used by non-Microsoft Windows operating systems), or reboot) occur. With cache devices that have relatively larger storage capacity, repopulating cache contents can take considerable time and consume significant processing resources. As an example, an eight gigabyte flash memory device, which may hold up to sixteen gigabytes of compressed data, may take up to thirty minutes to repopulate using background I/O from disk at approximately ten megabytes per second. This not only effectively negates any performance benefits that might have been gained by employing the cache device, but indeed may significantly slow system operations.
One reason cache contents must be repopulated across certain power transitions is that there is no way to reliably ensure that cache contents accurately represent the contents of disk storage when the computer is restarted, because the contents of the cache device and/or the disk may have been modified during the power transition. For example, when a first computer is shut down, a hacker could disconnect a removable cache device, connect it to another computer, and modify the cache contents, so that if the device were then reconnected to the first computer, incorrect data (hereinafter referred to as “inauthentic” data) could be served from the cache device to satisfy I/O requests. In addition to a hacker's malicious acts, cache contents might also become corrupted during a power transition due to a hardware failure of the computer or cache device.
Cache contents may also become “stale” during a power transition because data on disk was updated during the transition, so that when the computer is restarted, the cache contents may no longer accurately represent disk contents. For example, after shutdown a user might boot the disk into another operating system that does not recognize the cache device and modify data stored on the disk that is cached on the cache device, so that when the computer is restarted the cache contents no longer reflect what is stored on the disk. In another example, certain operations on a computer during shutdown might occur after the cache device is rendered inaccessible to the operating system (e.g., after the cache device is turned off), so that any writes to disk performed by the operating system subsequent to this point in time may not be accurately reflected by cache contents. Any of numerous events may cause cache contents to become stale across a power transition.
Embodiments of the present invention provide techniques for managing these and other concerns, so that cache contents may be relied upon as accurately reflecting data stored on disk across a power transition. For example, some embodiments of the invention provide techniques for verifying that cache contents remain authentic across a power transition. In addition, some embodiments provide techniques for reliably ensuring that cache contents do not become stale across a power transition. Further, some embodiments provide techniques for managing cache metadata across power transitions as well as during normal (“steady state”) operations, ensuring that the cache metadata may be efficiently accessed and reliably saved and restored when a power transition occurs.
By providing techniques which ensure that cache contents can be relied upon as accurately reflecting data stored on disk across power transitions, some embodiments of the invention may enable a cache device with substantial storage capacity to be employed to significantly speed up I/O operations performed by the operating system and/or applications. The increased speed of I/O operations may not only expedite normal, “steady state” operations of the computer, but also significantly speed up operations performed during boot, so that the computer is ready for use much more quickly.
In some embodiments, a method is provided for operating a computer having coupled thereto a storage medium and a cache device. The computer comprises an operating system. The method comprises acts of: (A) in response to a request to write a data item to an address on the storage medium, causing the data item to be written to the address on the storage medium and to a corresponding address on the cache device; (B) subsequent to a reboot of the operating system, determining whether the data item stored at the address on the cache device can reliably be employed to satisfy a request to read the data item from the address on the storage medium; and (C) if it is determined in (B) that the data item stored at the address on the cache device can reliably be employed to satisfy a request to read the data item from the address on the storage medium, causing the data item to be read from the address on the cache device.
Other embodiments provide at least one computer storage medium having stored thereon instructions which, when executed by a computer comprising an operating system and having coupled thereto a cache device, perform a method comprising acts of: (A) in response to a request to write a data item to an address on the computer storage medium, causing the data item to be written to the address on the computer storage medium and to a corresponding address on the cache device; (B) subsequent to a reboot of the operating system and in response to a request to read the data item from the address on the computer storage medium, determining whether the data item stored at the address on the cache device was modified after (A); and (C) if it is determined in (B) that the data item stored at the address on the cache device was not modified after (A), causing the data item to be read from the address on the cache device.
Still other embodiments provide a computer, comprising: a storage medium having at least one address at which data is stored; a cache device having at least one address at which data is stored; at least one processor programmed via an operating system to: in response to a request to write a data item to a first address on the storage medium, cause the data item to be written to the first address on the storage medium and to a corresponding address on the cache device; identify an occurrence of a write operation to an address on the storage medium which is not also performed to an address on the cache device; and determine, subsequent to a reboot of the operating system, whether the data item stored at the corresponding address on the cache device can reliably be used to satisfy a request to read the data item from the first address on the storage medium, by determining whether a write operation was performed to the first address on the storage medium which was not also performed to the corresponding address on the cache device.
FIGS. 1A-1B are block diagram depicting techniques for writing to and reading from a cache device, in accordance with the prior art;
FIGS. 2A-2B depict exemplary techniques for writing to and reading from a cache device in accordance with some embodiments of the invention;
FIG. 3 is a block diagram depicting an exemplary technique for ensuring that cache data accurately reflects data stored on disk after a power transition, in accordance with some embodiments of the invention;
FIG. 4 is a block diagram depicting an exemplary technique for storing cache metadata, in accordance with some embodiments of the invention;
FIG. 5 is a block diagram depicting exemplary storage operations for cache metadata, in accordance with some embodiments of the invention;
FIG. 6 is a flowchart depicting an exemplary technique for servicing read requests using a cache device, in accordance with some embodiments of the invention;
FIG. 7 is a block diagram depicting an example computer which may be used to implement aspects of the invention; and
FIG. 8 is a block diagram depicting an example computer memory on which instructions implementing aspects of the invention may be recorded.
Some embodiments of the invention provide techniques for ensuring that cache contents accurately reflect the contents of disk storage across a power transition. For example, some embodiments provide a capability for ensuring that cache contents remain authentic and/or have not become stale across the power transition. Further, some embodiments provide techniques for managing cache metadata, to ensure that metadata has not been tampered with during a power transition. In addition, some embodiments provide a capability for storing cache metadata which may improve the efficiency with which both power transitions and normal operations may be performed. The sections that follow describe these embodiments in detail.
I. Verifying Cache Data Authenticity
When a computer experiences a power transition (e.g., is taken into standby or hibernate mode, or is rebooted), a cache device may be disconnected from the computer, and its contents may be altered (e.g., by a malicious hacker). For example, when a computer is brought into standby or hibernate mode, a removable cache device such as a flash memory drive may be disconnected from the computer and its contents modified. Even non-removable devices such as internal NVRAM devices may be disconnected and their contents changed when the operating system is rebooted (i.e., reloaded, thereby restarting the computer). As a result, when the cache device is reconnected to the computer, it may store different information than the user believes (i.e., the data stored in cache may not be “authentic”). If inauthentic data is served from cache to satisfy an input/output (I/O) request, the computer's operation could be negatively affected.
Some embodiments of the invention provide techniques for detecting modifications that occur to cache contents during a power transition, to ensure that I/O requests are not satisfied using inauthentic data from cache. In some embodiments, a capability is provided to detect any “offline modifications” which occur to cache contents during a power transition which render them inauthentic.
Some embodiments provide this capability using a representation of at least a portion of the data. For example, a representation may be calculated or derived from at least a portion of the data and/or other information in a predetermined manner. The representation may be generated a first time when the data is written to cache, and stored at one or more locations. For example, the representation may be written to cache along with the data, or to some other location(s). When stored to cache, the representation may be stored in a manner which associates the representation with the data (e.g., it may be written to a cache address adjacent that to which the data is written, written to cache metadata associated with the data, and/or associated in some other fashion). When the data is subsequently read from cache, the representation may also be retrieved. The representation may be re-generated in the predetermined manner, and the regenerated representation may be compared to the retrieved representation. If the representations match, the data retrieved from cache is determined to be authentic, and served to satisfy the read request. If not, a request is issued to read the data instead from disk storage to satisfy the read request, and the inauthentic data stored on cache may be evicted (e.g., deleted).
FIGS. 2A-2B depict this process in greater detail. In particular, process 20A shown in FIG. 2A includes operations performed when data is written to cache, and process 20B shown in FIG. 2B includes operations performed subsequently when the data is read from cache. Processes 20A-20B each include operations performed by cached volume 120 (on the left side of each figure), cache manager 100 (in the middle) and cache device 110 (on the right).
At the start of process 20A (FIG. 2A), a write request directed to address X on disk storage is received by cache manager 100 in act 205. In act 210, cache manager 100 employs cache metadata (not shown) to determine an address Y on cache device 110 to which the data should also be written. Cache manager also generates the representation of at least a portion of the data.
Embodiments of the invention may generate this representation using any suitable technique. In some embodiments, one or more cryptographic authentication techniques may be employed to generate the representation. For example, in some embodiments, the representation may comprise a message authentication code (MAC) generated from the data and a set of secret keys and per-data item sequence numbers. However, the invention is not limited to such an implementation, as any suitable technique for generating the representation may be employed. For example, cryptographic authentication techniques need not be employed. As an example, a strong hash and/or cyclic redundancy code (CRC) might alternatively be used to represent data, and may be generated from individual data items stored to cache, or for one or more groups of data items. In this respect, Applicants have appreciated that if the goal of verifying data authenticity were to merely detect instances of hardware corruption (i.e., hacking of data were not a concern), then using a CRC may be sufficient, and may consume less processing resources than generating a MAC for each data item. However, if the goal is to prevent a hacker or malicious actor from modifying cache contents, then a cryptographic solution may be preferable, so that a representation such as a MAC may be used. The invention is not limited to any particular implementation, as any suitable technique may be employed.
In act 215, cache manager 100 issues the request to cache device 110 to write the data to cache address Y. Cache manager also issues a request to cache device 110 to write the representation. For example, cache manager 100 may specify that the representation should be written to one or more locations adjacent to cache address Y, or be stored in cache metadata for the data, and/or using any other technique. As discussed above, the invention is not limited to writing the representation to any particular location (e.g., it need not be written to cache device 110). If written to cache, the representation may be associated with the data in any manner desired.
In act 220, cache device 110 receives the request and processes it by writing the data and the representation in act 225.
In act 230, cache manager 100 issues a corresponding request to cached volume 120 to write the data to disk address X. Cached volume 120 receives this request in act 235 and processes it by writing the data to address X in act 240. Although shown in FIG. 2A as being performed subsequent to the write to cache in acts 215-225, acts 230-240 may be performed in parallel with acts 215-225, or at any other suitable time(s), as the invention is not limited to any particular implementation. Process 20A then completes.
Process 20B (FIG. 2B) includes operations performed to read the data stored to cache. In act 245, cache manager 100 receives a request to read the data stored at address X on cached volume 120. Using cache metadata (not shown), cache manager 100 determines that the data is stored at address Y on cache device 110 in act 250. In act 255, cache manager 100 issues a read request to cache device 110 to retrieve both the data stored at address Y and the associated representation. The request is received by cache device 110 in act 260 and processed in act 265, whereupon cache device 100 returns the results to cache manager 100.
In act 270, cache manager 100 determines whether the data retrieved from cache can be verified. In some embodiments, this is done by re-generating the representation of the data, and comparing the regenerated representation with the representation originally generated in act 215. For example, act 270 may include regenerating a MAC or CRC for the data, and comparing it to the representation retrieved from cache in act 265.
If it is determined in act 270 that the representation can be verified, the process proceeds to act 275, wherein the data retrieved from cache device 110 is served to satisfy the read request, and process 20B then completes. If it is determined in act 270 that the representation can not be verified, the process proceeds to act 280, wherein cache manager 100 issues a request to cache device 110 to evict (e.g., erase or otherwise make inaccessible) the data stored at address Y. Cache manager 100 then issues a request to cached volume 120 to read the data from address X on disk in act 285. This request is received in act 290 and processed in act 295, whereupon the data is returned to cache manager 100. The data read from address X is then served to satisfy the read request in act 299. Process 20B then completes.
If a cryptographic solution for verifying data authenticity is employed, any key(s) used to generate a representation may be written to locations other than the cache device for the duration of the power transition, to prevent a hacker from gaining access to the keys to regenerate representations for altered data items. For example, in some embodiments, keys may be stored in disk storage (e.g., when the computer is shut down) to prevent unauthorized access. However, the invention is not limited to such an implementation, as keys need not be stored, and if stored, may reside in any suitable location. For example, stored keys may be placed in any configuration store provided by the operating system that is available during system boot (e.g., the system registry in Windows), or re-generated based on some user input (e.g., a password) so that no key storage is necessary.
It should be appreciated that the above-described embodiments for verifying the authenticity of a data item stored on a cache device are merely examples, and that authenticity may be verified using any suitable technique. For example, data item authenticity need not be verified by generating a representation of at least a portion of the data item when the data item is written which is later re-generated when the data item is read. Any suitable technique which reliably ensures that a data item read from cache is authentic and matches the data item previously written to cache may be employed. The invention is not limited to any particular implementation.
II. Preventing Cache Data Staleness
As discussed above, conventional operating systems are incapable of detecting when write operations are performed to data items stored on disk during power transitions which render cache contents stale. Some embodiments of the invention provide mechanisms for detecting when these “offline writes” occur, thereby ensuring that cache contents accurately reflect data stored on disk after a power transition occurs.
With some operating systems (e.g., the Windows family of operating systems offered by Microsoft Corporation), the semantics of certain power transitions (e.g., standby and hibernate modes) are such that data on non-removable storage devices (e.g., disk storage) can not be modified during a power transition. As such, the cache contents corresponding to data on such non-removable media generally do not become stale. However, when the computer is shut down, a number of things can happen which make it possible for data on disk to be modified. For example, a user may boot the disk into another operating system on that computer, or connect the disk to another computer, and modify data stored on disk. In addition, as discussed above, the mechanics of shutdown of many conventional operating systems are such that at some point during the shutdown, a cache device is turned off and is no longer accessible by the operating system, but the operating system may continue to access the disk. As such, the operating system may update data items on disk which are cached on the cache device. Because the cache device has been turned off, the operating system has no way of also updating these cache contents, so that they are rendered stale.
To manage these and other occurrences, some embodiments of the invention provide techniques for detecting modifications to data stored on disk after a shutdown is initiated, so that cache contents which are rendered stale by such modifications may be updated, evicted from cache, or otherwise handled.
To detect writes which are performed to disk storage during shutdown operations occurring after a cache device is shut off, some embodiments of the invention employ a write recorder component. A write recorder component may, for example, be implemented as a driver in the operating system's I/O path, although the invention is not limited to such an implementation. For example, a write recorder component may be hardware-based. As an example, disk storage hardware might provide one or more interfaces that provide the capability to identify the set of modifications that occurred during a certain time period, or whether modifications occurred during a certain time period. For example, disk storage hardware may provide a spin-up/power up/boot counter which may be employed to deduce that at least some stored data items have been updated, in which case cache contents corresponding to the data stored on disk may be evicted (this should not occur frequently, so employing the cache device should still deliver substantial benefits). The invention is not limited to any particular implementation.
In some embodiments, the write recorder component is configured to become active when shutdown is initiated, and to keep track of all writes performed to disk storage until shutdown completes. As a result, when the computer is later restarted, these writes may be applied to cache contents. For example, when the computer is restarted and disk volumes come online, the cache manager may then started, and may begin tracking writes to disk. The cache manager may query the write recorder component to determine the offline writes that occurred after the cache device was shut off, merge these writes with those which the cache manager tracked during startup, and apply the merged set of writes to cache contents. Applying writes to cache contents may include, for example, updating the cache contents corresponding to the data on disk to which the writes were directed (e.g., performing the same write operations to these cache contents), evicting these cache contents, a combination of the two (e.g., applying write operations to certain cache contents and evicting others), or performing some other operation(s). After offline writes are applied to cache contents, the write recorder component may be shut down, and the cache device may begin servicing I/O requests.
FIG. 3 depicts an example process 30 for tracking offline writes and applying these writes to cache contents. In particular, process 300 includes operations performed by cache manager 100, write recorder 300, cache device 110 and cached volume 120 during a computer's shutdown and subsequent reboot.
In act 305, which occurs during computer shutdown, cache manager 100 activates write recorder 300 and supplies to it a “persistence identifier” which identifies the set (i.e., generation) of write operations to be tracked by the write recorder. (Examples of the uses for a persistence identifier are described in detail below.) In act 310, cache manager 100 writes the persistence identifier, as well as cache metadata stored in memory, to cache device 110. At this point in the shutdown process, cache device 110 is turned off and becomes inaccessible to cache manager 100.
In act 315, write recorder 300 writes the persistence identifier passed to it in act 305 to cached volume 120, and begins tracking any write operations performed to cached volume 120 during shutdown. For example, write recorder 300 may create a log file, or one or more other data structures, on cached volume 120 or at some other location(s) to indicate the addresses on disk to which write operations are performed, and/or the data written to those addresses. At the completion of act 315, the computer's shutdown operations have finished.
Thereafter, the computer is restarted. As part of the boot process, cached volume 120 is brought online, write recorder 300 and cache manager 100 are restarted. Cache manager 100 may then begin tracking write operations performed to cached volume 120. For example, cache manager 100 may create a log file and store it on cache device 110, cached volume 120, and/or the computer's memory (not shown in FIG. 3). In act 320, write recorder 300 reads the volume changes logged in act 315, as well as the persistence identifier written to cached volume 120 in act 315. The volume changes and persistence identifier are then passed to cache manager 100 in act 325.
It should be appreciated that write recorder 300 may be incapable of tracking of all writes to disk after cache device 110 has turned off. For example, hardware data corruption, untimely power failures and/or problems in writing the log file may render write recorder 300 incapable of tracking all offline writes performed to a disk volume. In such cases, write recorder 300 may indicate to cache manager 100 in act 325 that it can not reliably determine that the log is a complete and accurate record of all offline writes performed. If this occurs, cache manager 100 may evict the entire cache contents, or a portion thereof (e.g., corresponding to a particular disk volume for which the write recorder could not track all write operations), as potentially being unreliable. The remainder of the description of FIG. 3 assumes that write recorder 300 is capable of tracking all offline writes.
In act 330, cache manager 100 reads the cache metadata and persistence identifier from cache device 110 into memory. Cache manager 100 determines whether the persistence identifier can be verified (this is described further below). If not, cache manager 100 may evict the entire contents of cache device 110, or a portion thereof (e.g., corresponding to a particular disk volume for which the persistence identifier could not be verified). If the persistence identifier can be verified, cache manager 100 merges any write operations performed to disk storage since the computer was restarted with any write operations tracked by write recorder 300. For example, if one or more logs indicate the data written to each address on disk, cache manager 100 may select the latest update performed to each address and write it to memory.
In some embodiments, write recorder 300 may be configured to continue recording writes after the computer is restarted, so that cache manager 100 need not record writes performed after that point and merge them with writes tracked by write recorder 300. Instead, write recorder 300 may simply provide a record of all writes to cache manager 100.
Using the cache metadata read in act 330, cache manager 100 then applies the set of writes to the contents of cache device 110 in act 335. As described above, applying the writes may include evicting cache contents, updating cache contents, doing both, or performing some other operation(s). For example, offline writes tracked by write recorder 300 in act 315 may be applied by evicting the corresponding cache contents, while the writes tracked by cache manager 100 since the computer was restarted may be applied by updating the corresponding cache contents to reflect the writes. Applying write operations to cache contents may be performed in any suitable way, as the invention is not limited to any particular implementation.
At the completion of act 335, the process of FIG. 3 completes.
It should be appreciated that the invention is not limited to employing a write recorder component that is configured to become active when shutdown is initiated, as write operations not occurring during shutdown may also, or alternatively, be tracked. For example, in some implementations, a cache device may be susceptible to becoming inaccessible for periods of time. For example, if the cache device is accessed via one or more networks, connectivity could be lost, or if the cache device is removable from the computer, a surprise (e.g., unintentional) removal could occur. As a result, some embodiments may employ a write recorder to track all (or a portion of) writes performed to disk, not just those occurring during shutdown, and a cache device which is configured to periodically capture cache “snapshots” while still online. As such, if the cache becomes inaccessible for some period of time and is later reconnected, the latest cache snapshot can be updated using write operations tracked by the write recorder, rather than having to be completely rebuilt.
It should also be appreciated that while the example process 30 of FIG. 3 may detect offline writes performed by the operating system during shutdown, other measures may be needed to detect offline writes performed to disk after shutdown completes. Such writes may occur, for example, when a user boots the disk into another operating system after shutdown, or removes the disk from the computer after shutdown and connects it to another computer, and then modifies data stored on disk.
Recognizing the difficulties associated with attempting to track offline writes occurring after shutdown (e.g., by another operating system), some embodiments of the invention instead try to prevent them from occurring. For example, some embodiments attempt to make a particular disk volume inaccessible to operating systems that do not provide a write recorder component after shutdown. This may be accomplished in any of numerous ways.
In some embodiments, write recorder 300 may mark a disk volume in such a way that it becomes un-mountable by operating systems that do not provide a write recorder component to track offline writes. For example, write recorder 300 may modify the volume identifier that indicates the type of file system used on the volume. In this respect, those skilled in the art will recognize that a volume identifier enables an operating system to identify the type of file system used to store data on the volume, thereby enabling the operating system to understand the structure of data stored on the volume, where to find files, etc. For example, if a volume identifier indicates that an NT File System (NTFS) file system was used to store data on the volume, then another operating system attempting to mount the volume would understand that an NTFS file system would be needed to parse and access the data thereon. If the volume identifier provided no indication of the type of file system used to store data on the volume, most operating systems would fail to mount the volume, as there would be no reliable way to understand the structure of data stored thereon. As such, some embodiments of the invention modify the volume identifier of a disk volume to make it inaccessible, thereby preventing a user from booting the disk volume into another operating system and making offline changes to data stored on the volume.
Recognizing that some operating systems may be capable of identifying the type of file system used to store data on a volume even if the volume identifier were modified, some embodiments of the invention provide a mechanism for detecting when an operating system mounts the volume. In this respect, to mount a disk volume, any operating system would need to update the volume identifier (e.g., to indicate that a NTFS file system was employed to store data on the volume) to allow data thereon to be accessed. Any such update would be easily detectable upon reboot. If such an update were detected, some embodiments of the invention may assume that the contents of the volume had been modified since the last shutdown, and evict the cache contents corresponding to data stored on the volume.
Some embodiments of the invention provide a capability whereby a disk volume may be booted into another operating system which also employs a write recorder component. For example, if a disk were removed from one computer running an operating system that provides a write recorder component, and boots the disk into another operating system that provides a write recorder component, the other operating system might be configured to recognize that a changed volume identifier indicates that the volume may be cached. As a result, the other operating system may add to a log of offline writes (e.g., stored on the volume) created by the first operating system.
The above-described embodiments designed to make a disk volume un-mountable by certain operating systems may pose problems for certain applications which rely on the volume identifier to perform certain functions (e.g., backup applications). With these applications, if the volume identifier were changed, the volume may be unrecognizable and thus not backed up. Accordingly, some embodiments of the invention provide a mechanism for determining whether a file system was mounted after shutdown. If so, it is assumed that changes were made to data in the file system, and all cache contents corresponding to data in the file system may be evicted.
Some embodiments may detect the mounting of a file system after shutdown by placing the file system log at shutdown in a state which would require any operating system attempting to mount the file system to modify the log in some way (e.g., change its location, add a new entry, etc.). For example, write recorder 300 may note as part of the task of logging offline writes the location and/or content of the file system log when the file system is dismounted (e.g., in the log itself). Because any operating system attempting to mount the file system would have to change the log (e.g., if the file system were an NTFS file system, an operating system attempting to mount the file system would add an entry to the log), if the log has not changed upon reboot, it is assumed that the file system was not mounted by another operating system during the power transition, so that cache contents corresponding to data stored in the file system have not been rendered stale. Conversely, if the log has been changed in some way (e.g., its location has changed, and entry has been added, etc.) then it is assumed that the file system was mounted by another operating system, and that data stored therein has changed, rendering the cache contents corresponding to data stored in the file system stale. As such, these cache contents may be evicted.
In addition to providing mechanisms to prevent offline writes, some embodiments of the invention provide a capability to manage inconsistent generations of cache contents. Inconsistent generations of cache contents may be created for any of numerous reasons. One example may occur when first and second computers, having first and second cache devices connected thereto, employ techniques described herein to persist cache contents across power transitions. If the second cache device were connected to the first computer (or the first cache device connected to the second computer) and the first computer were restarted, incorrect data could be served from the second cache device to satisfy I/O requests. This is because the first computer's operating system could deem the contents of the second cache device authentic (since a regenerated representation of the data returned from cache could match a representation originally generated) and not stale (since offline writes could be applied to cache contents). Another example could arise if a first cache device were connected to a computer, the computer was shut down (thereby persisting cache contents), the computer was then restarted, a second cache device was connected, and the computer was shut down again (thereby persisting cache contents again). If the computer was then restarted again and the first cache device connected, incorrect data could be served to satisfy I/O requests, since there would be no reliable way to determine that the first cache device does not store the latest generation of cache contents.
Some embodiments provide a capability to identify inconsistent generations of cache contents so that cache contents persisted previous to the latest shutdown are not erroneously used to satisfy I/O requests. In some embodiments, this capability is provided via a unique persistence identifier, which may be generated (as an example) as shutdown is initiated, in any of numerous ways. For example, GUIDs and/or cryptographic random number generators may be employed for this purpose. As described above with reference to FIG. 3, the persistence identifier may be stored on the cache device (e.g., in or with cache metadata) as well as on the computer (e.g., on disk and/or memory) and verified (e.g., by comparing the two versions) as the computer is started. If verification is unsuccessful, cache contents may be evicted as representing a previous persisted cache generation.
As with the authentication keys discussed above, any keys used to generate a persistence identifier may be written to a location other than the cache device for the duration of a power transition. For example, in some embodiments a write recorder component may write the keys as well as the persistence identifier to disk storage (e.g., at shutdown). However, the invention is not limited to such an implementation, as those skilled in the art may envision numerous alternative locations in which keys may be saved. Keys may, for example, be kept in any configuration store provided by the operating system which is available during system boot (e.g., the registry in Windows).
III. Cache Metadata
As described above, cache metadata may provide a mapping between disk addresses where data items are stored and the corresponding addresses on a cache device where those data items are cached. Some embodiments of the invention provide a capability for storing cache metadata which allows this mapping to be relied upon across power transitions, so that cache contents may be reliably accessed when the computer is restarted.
With certain types of power transitions (e.g., standby and hibernate modes), simply storing cache metadata in memory (i.e., RAM) is acceptable since the contents of memory are preserved during standby and hibernate transitions. During reboot, however, the contents of system memory are not preserved. As such, some embodiments of the invention provide for storing cache metadata on some non-volatile medium/media during shutdown, and then restored upon reboot. For example, cache metadata may be stored on a cache device, and/or on one or more separate non-volatile media. Further, some embodiments may be capable of deriving some portions of cache metadata from others, so that storing all cache metadata is not required.
Some embodiments may employ the techniques described in Section I. above for verifying the authenticity of cache metadata, so as to detect and prevent inadvertent or malicious modifications to metadata during shutdown. For example, during startup when the cache device comes online, the cache manager may verify the authenticity of metadata as it is loaded to memory, using the techniques described above with reference to FIGS. 2A-2B. If the authenticity of cache metadata can not be verified, the corresponding cache contents may be updated based on data stored on disk, evicted, or otherwise processed as described above.
In some embodiments, cache metadata may be compressed to reduce the amount of metadata to save during shutdown and load at reboot. Because compression of metadata may require saving a separate piece of information (e.g., a header in the cache) containing information about the metadata, the techniques described above may be employed to verify the authenticity of this information as well at reboot.
With cache devices having relatively large storage capacity, a significant amount of metadata may be required to manage cache contents. For example, a cache device having a sixteen gigabyte storage capacity may be capable of storing up to thirty-two gigabytes of compressed data. In some implementations, disk addresses may be reflected in cache metadata in “data units” representing four kilobytes of disk storage. As such, to track the location of thirty-two gigabytes of data, eight million distinct data units are needed. If each of the eight million data units is represented in cache metadata using a sixteen-byte mapping (i.e., from a disk address to a cache address), then these mappings require one hundred twenty-eight megabytes of storage. Applicants have appreciated that writing one hundred twenty-eight megabytes of cache metadata to non-volatile media during shutdown, and restoring one hundred twenty-eight megabytes of cache metadata to memory at boot, would be prohibitively time-consuming and consume an excessive amount of processing resources.
Recognizing that the amount of cache metadata can not easily be reduced, some embodiments of the invention provide techniques designed to reduce the time and processing resources required to save and restore cache metadata. For example, some embodiments provide techniques whereby only a portion of cache metadata may be stored at shutdown or restored upon reboot.
In some embodiments, the capability to load and restore only a portion of cache metadata is provided by employing one or more hierarchical data structures (e.g., trees, multi-level arrays, etc.) to store cache metadata. Employing a hierarchical data structure may allow lower levels of the hierarchy to be stored on a non-volatile medium (e.g., the cache device) while only higher levels of the hierarchy are loaded to memory at startup. Thereafter, when read requests are processed, the cache metadata that is read from the non-volatile medium (i.e., from lower levels of the hierarchy) to perform the read operation may be “paged in” to (i.e., read from a storage medium into) memory so that it may be more quickly accessed for subsequent read requests to the same disk/cache address. When the computer is later shut down, only the cache metadata stored at the higher levels of the hierarchy, and the cache metadata to be stored in the lower levels of the hierarchy which was paged in to memory, may need to be saved to the non-volatile medium. As such, the amount of memory required to store cache metadata, and the time required to store cache metadata in non-volatile storage at shutdown and restore it to memory at reboot, may be reduced.
Some embodiments of the invention employ a B+ tree to store at least a portion of cache metadata. As those skilled in the art will appreciate, B+ trees may employ large branching factors, and therefore reduce the number of levels in the hierarchy employed. Using the example given above, if eight million data units are to be represented in cache metadata and a B+ tree with a branching factor of two hundred were employed (so that each node in the hierarchy has two hundred “child” nodes), a data structure having only three levels would be sufficient to store the metadata: a single “root” node at the highest level, two hundred nodes at the second level, and forty thousand nodes at the third level, with each of the forty thousand nodes including pointers to two hundred data units (or eight million data units total).
FIG. 4 depicts this example B+ tree which includes root node 400, level two nodes 410 1-200 and level three nodes 420 1-200. Each node includes two hundred elements each separated by pointers to nodes at a lower level in the hierarchy. For example, element 402 in root node 400 is delimited by pointers 401 and 403. A value (e.g., a cache address) associated with a given key (e.g., a disk address) may be determined by following the pointer to the left or right of an element in a node, with the pointer to the left of the element being followed if the key is less than the element, and the pointer to the right being followed if the key is greater than the element. For example, to determine a value for a key which is less than element 402, pointer 401 would be followed to level two node 410 1, to determine a value for a key greater than element 402 but less than element 404, pointer 403 would be followed to level two node 410 2 (not shown), and so on. Similarly, at the level two node, a pointer to the left or right of an element (depending on whether the key is less than or greater than elements in the node) is followed to a level three node. At level three, a final pointer is followed (again based on whether the key is less than or greater than elements in the node) to the value, with each pointer at level three referencing one of the eight million data units in cache metadata.
It should be appreciated that a B+ tree with a large branching factor provides a relatively “flat” hierarchy with almost all nodes being located at the bottom level of the hierarchy. That is, of the 40,201 total nodes in the tree, 40,000 are at the lowest level. Some embodiments of the invention take advantage of this by restoring only the top two levels of the hierarchy to memory at startup, while the cache metadata in the lowest level of the hierarchy is stored on the cache device until needed (e.g., it may be loaded into memory on demand as read requests are processed, loaded lazily, etc.). When the computer is shut down, only the data at the top two levels and the data loaded into memory during operation need to be stored on the cache device. As a result, both startup and shutdown operations may be performed quickly and efficiently.
Thus, some embodiments of the invention provide for pointers in nodes at one level of the hierarchy stored in memory (in the example above, level two of the hierarchy) which reference nodes at another level of the hierarchy stored on the cache device (in the example above, level three). For example, when a read request for a cached data item is received, embodiments of the invention follow pointers through one or more levels of the hierarchy stored in memory, and then to metadata at lower levels of the hierarchy stored in cache, to determine the address at which the data item is stored in cache. In some embodiments, once the cache address is determined for the data item, it may be stored in memory so that subsequent requests to read the item may be performed without having to read cache metadata from the cache device.
FIG. 5 depicts an example system 50 for managing cache metadata in accordance with some embodiments of the invention. FIG. 5 depicts memory 500 and cache device 110, both accessible to a computer (not shown). When the computer is started, cache metadata comprising one or more levels of a hierarchical data structure such as a B+ tree are loaded to memory 500 in operation 505. Using the example above to illustrate, if there are eight million data units represented in cache metadata, such that a three-level hierarchical data structure may be used to store the cache metadata, then the top two levels of the hierarchy may be loaded to memory 500. Of course, if more or less than eight million data units are be represented in metadata, and a hierarchical data structure having more or less than three levels is to be used, then a different number of levels to the hierarchy may be loaded to memory 500.
Thereafter, when a read request is directed to a data item maintained in cache, the cache address at which the data item is stored is determined by accessing cache metadata stored in the level(s) of the hierarchy stored in cache device 110. This cache metadata is then stored in memory 510, so that subsequent reads or writes to the data item may be performed without having to read cache metadata stored on cache device to determine the cache address at which the data item is stored. Instead, the cache address may be read from memory, which may be performed more quickly than a read to cache.
Later, when the computer is shut down, the cache metadata stored in memory (i.e., the metadata stored in the levels of the hierarchy loaded to memory in operation 505, and any metadata used to satisfy read requests written to memory in operation 510) is loaded to cache device 500 in act 515. As a result of the relatively small amount of cache metadata stored in memory, shutdown may be performed quickly, without requiring substantial processing resources.
It should be appreciated that a B+ tree is but one of numerous types of data structures which may be employed to store cache metadata, and that other types of data structures (e.g., hierarchical structures such as AVL trees, red-black trees, binary search trees, B-trees and/or other hierarchical and non-hierarchical data structures) may be employed. The invention is not limited to employing any one data structure or combination of data structures to store cache metadata.
Some embodiments may provide for a “target amount” of cache metadata to be kept in memory at any one time. The target amount may be determined in any suitable fashion. For example, a target amount may be a percentage of the amount of physical memory available to a computer. For example, if the computer has one gigabyte of memory, then two megabytes of cache metadata (as an example) may be stored in memory at any one time. Thus, when the computer is shut down, only two megabytes of cache metadata need to be loaded to the cache device.
In some embodiments, cache metadata may be cycled in and out of memory. For example, if a target amount of cache metadata is already stored in memory, and a read is performed which requires cache metadata to be read from the cache device, that metadata may be “paged in” to memory, and other cache metadata (e.g., that which was accessed least recently) may be erased (e.g., after being written to the cache device). For example, cache metadata may be written to the cache device if it has changed since the last time it was stored on the cache device.
FIG. 6 depicts an example. Specifically, process 60 shown in FIG. 6 includes operations which may be performed by cache manager 100 to read cache metadata using the techniques described above.
At the start of process 600, a request is received in act 605 to read data stored at disk address X. In act 610, a determination is made whether the cache address at which the data is stored can be identified from cache metadata stored in memory. If so, the process proceeds to act 615, wherein the identified cache address is determined, and then used to issue a read request to cache device 110 in act 620. Process 60 then completes. If the cache address can not be identified using cache metadata stored in memory, then the process proceeds to act 625, wherein cache metadata is read from cache device 110 to determine the cache address at which the data is stored. Using the cache offset identified in act 625, a read request is issued to the identified cache offset in act 620, and process 60 then completes.
It should be appreciated that storing cache metadata on the cache device may not only speed up the process of loading and restoring cache metadata during startup and shutdown, but may also speed up the system operations performed during startup and shutdown. In this respect, shutdown and startup often involve multiple accesses to certain data items, and performing two read operations to a cache device is typically faster than performing one read to disk storage. As a result, if a data item accessed during shutdown and/or startup and the metadata which specifies its location were both stored in cache, then the data item might be accessed more quickly then if the data item were stored on disk, since the two reads to cache (i.e., one to access cache metadata to determine the item's location, and a second to access the item itself) can typically be performed more quickly than a single read to disk. As such, individual operations performed during shutdown and startup may be expedited. Even further, if during a first read of cache metadata from cache the address at which the item is stored is paged into memory, then subsequent reads of the data item could be performed even more quickly, since a read to memory can typically be performed more quickly than a read to cache.
Various aspects of the systems and methods for practicing features of the invention may be implemented on one or more computer systems, such as the exemplary computer system 700 shown in FIG. 7. Computer system 700 includes input device(s) 702, output device(s) 701, processor 703, memory system 704 and storage 706, all of which are coupled, directly or indirectly, via interconnection mechanism 705, which may comprise one or more buses, switches, networks and/or any other suitable interconnection. The input device(s) 702 receive(s) input from a user or machine (e.g., a human operator), and the output device(s) 701 display(s) or transmit(s) information to a user or machine (e.g., a liquid crystal display). The processor 703 typically executes a computer program called an operating system (e.g., a Microsoft Windows-family operating system, or any other suitable operating system) which controls the execution of other computer programs, and provides scheduling, input/output and other device control, accounting, compilation, storage assignment, data management, memory management, communication and dataflow control. Collectively, the processor and operating system define the computer platform for which application programs and other computer program languages are written.
The processor 703 may also execute one or more computer programs to implement various functions. These computer programs may be written in any type of computer program language, including a procedural programming language, object-oriented programming language, macro language, or combination thereof. These computer programs may be stored in storage system 706. Storage system 706 may hold information on a volatile or non-volatile medium, and may be fixed or removable. Storage system 706 is shown in greater detail in FIG. 8.
Storage system 706 typically includes a computer-readable and writable nonvolatile recording medium 801, on which signals are stored that define a computer program or information to be used by the program. A medium may, for example, be a disk or flash memory. Typically, an operation, the processor 703 causes data to be read from the nonvolatile recording medium 801 into a volatile memory 802 (e.g., a random access memory, or RAM) that allows for faster access to the information by the processor 703 than does the medium 801. The memory 802 may be located in the storage system 706, as shown in FIG. 8, or in memory system 704, as shown in FIG. 7. The processor 703 generally manipulates the data within the integrated circuit memory 704, 802 and then copies the data to the medium 801 after processing is completed. A variety of mechanisms are known for managing data movement between the medium 801 and the integrated circuit memory element 704, 802, and the invention is not limited thereto. The invention is also not limited to a particular memory system 704 or storage system 706. The term “recording medium” and the like as used in the specification and the claims refers strictly to a statutory article(s) of manufacture that is not a signal per se.
Further, it should be appreciated that a (client or server) computer may be embodied in any of a number of forms, such as a rack-mounted computer, desktop computer, laptop computer, tablet computer, or other type of computer. Additionally, a (client or server) computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital Assistant (PDA), a smart phone or any other suitable portable or fixed electronic device.
Such computers may be interconnected by one or more networks in any suitable form, including as a local area network or a wide area network, such as an enterprise network or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks. Also, the various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms.
In this respect, the invention may be embodied as a storage medium (or multiple storage media) (e.g., a computer memory, one or more floppy disks, compact disks, optical disks, magnetic tapes, flash memories, circuit configurations in Field Programmable Gate Arrays or other semiconductor devices, or other computer storage media) encoded with one or more programs that, when executed on one or more computers or other processors, perform methods that implement the various embodiments of the invention discussed above. The storage medium or media can be transportable, such that the program or programs stored thereon can be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above.
US4612612 30 Aug 1983 16 Sep 1986 Amdahl Corporation Virtually addressed cache
US4945474 8 Apr 1988 31 Jul 1990 Internatinal Business Machines Corporation Method for restoring a database after I/O error employing write-ahead logging protocols
US4972316 30 Mar 1987 20 Nov 1990 International Business Machines Corporation Method of handling disk sector errors in DASD cache
US4979108 26 Dec 1989 18 Dec 1990 Ag Communication Systems Corporation Task synchronization arrangement and method for remote duplex processors
US5088026 9 Feb 1990 11 Feb 1992 International Business Machines Corporation Method for managing a data cache using virtual external storage addresses as arguments
US5175834 13 Apr 1990 29 Dec 1992 Nec Corporation Swapping apparatus with reduced secondary storage based on frequency of use of page regions
US5263136 30 Apr 1991 16 Nov 1993 Optigraphics Corporation System for managing tiled images using multiple resolutions
US5297258 21 Nov 1991 22 Mar 1994 Ast Research, Inc. Data logging for hard disk data storage systems
US5307497 25 Jun 1990 26 Apr 1994 International Business Machines Corp. Disk operating system loadable from read only memory using installable file system interface
US5394531 18 Nov 1991 28 Feb 1995 International Business Machines Corporation Dynamic storage allocation system for a prioritized cache
US5398325 7 May 1992 14 Mar 1995 Sun Microsystems, Inc. Methods and apparatus for improving cache consistency using a single copy of a cache tag memory in multiple processor computer systems
US5420998 10 Apr 1992 30 May 1995 Fujitsu Limited Dual memory disk drive
US5454098 28 Sep 1992 26 Sep 1995 Conner Peripherals, Inc. Method of emulating access to a sequential access data storage device while actually using a random access storage device
US5463739 22 Dec 1992 31 Oct 1995 International Business Machines Corporation Apparatus for vetoing reallocation requests during a data transfer based on data bus latency and the number of received reallocation requests below a threshold
US5551002 1 Jul 1993 27 Aug 1996 Digital Equipment Corporation System for controlling a write cache and merging adjacent data blocks for write operations
US5561783 22 Mar 1995 1 Oct 1996 Intel Corporation Dynamic cache coherency method and apparatus using both write-back and write-through operations
US5572660 13 Nov 1995 5 Nov 1996 Dell Usa, L.P. System and method for selective write-back caching within a disk array subsystem
US5574877 25 Sep 1992 12 Nov 1996 Silicon Graphics, Inc. TLB with two physical pages per virtual tag
US5652857 29 Jan 1996 29 Jul 1997 Fujitsu Limited Disk control apparatus for recording and reproducing compression data to physical device of direct access type
US5666532 2 May 1996 9 Sep 1997 Novell, Inc. Computer method and apparatus for asynchronous ordered operations
US5717954 13 Oct 1995 10 Feb 1998 Compaq Computer Corporation Locked exchange FIFO
US5720029 25 Jul 1995 17 Feb 1998 International Business Machines Corporation Asynchronously shadowing record updates in a remote copy session using track arrays
US5740434 5 Sep 1996 14 Apr 1998 Tandem Computers Incorporated System for maintenance of database integrity
US5751932 7 Jun 1995 12 May 1998 Tandem Computers Incorporated Fail-fast, fail-functional, fault-tolerant multiprocessor system
US5754782 4 Dec 1995 19 May 1998 International Business Machines Corporation System and method for backing up and restoring groupware documents
US5754888 18 Jan 1996 19 May 1998 The Board Of Governors For Higher Education, State Of Rhode Island And Providence Plantations System for destaging data during idle time by transferring to destage buffer, marking segment blank , reodering data in buffer, and transferring to beginning of segment
US5764877 1 Sep 1995 9 Jun 1998 Digital Equipment Corporation Media recovery with time-split B-trees
US5806074 19 Mar 1996 8 Sep 1998 Oracle Corporation Configurable conflict resolution in a computer implemented distributed database
US5809280 13 Oct 1995 15 Sep 1998 Compaq Computer Corporation Adaptive ahead FIFO with LRU replacement
US5809543 7 Nov 1996 15 Sep 1998 Unisys Corporation Fault tolerant extended processing complex for redundant nonvolatile file caching
US5832515 12 Sep 1996 3 Nov 1998 Veritas Software Log device layered transparently within a filesystem paradigm
US5875466 28 Feb 1997 23 Feb 1999 Alantec Corporation Active cache for a microprocessor
US5897638 16 Jun 1997 27 Apr 1999 Ab Initio Software Corporation Parallel virtual file system
US5897660 7 Apr 1995 27 Apr 1999 Intel Corporation Method for managing free physical pages that reduces trashing to improve system performance
US5900022 3 Sep 1997 4 May 1999 Advanced Micro Devices, Inc. Apparatus and method for reducing the cache miss penalty in a virtual addressed memory system by using a speculative address generator and an accurate address generator
US5900870 9 Nov 1994 4 May 1999 Massachusetts Institute Of Technology Object-oriented computer user interface
US5923838 7 Apr 1997 13 Jul 1999 Mitsubishi Denki Kabushiki Kaisha Microcomputer with built-in flash memory
US5943692 30 Apr 1997 24 Aug 1999 International Business Machines Corporation Mobile client computer system with flash memory management utilizing a virtual address map and variable length data
US5996054 12 Sep 1996 30 Nov 1999 Veritas Software Corp. Efficient virtualized mapping space for log device data storage system
US6000006 25 Aug 1997 7 Dec 1999 Bit Microsystems, Inc. Unified re-map and cache-index table with dual write-counters for wear-leveling of non-volatile flash RAM mass storage
US6018433 7 Nov 1997 25 Jan 2000 Iomega Corporation Disk cartridge and data storage device with incompatible disk cartridge insertion protection
US6018746 23 Dec 1997 25 Jan 2000 Unisys Corporation System and method for managing recovery information in a transaction processing system
US6047291 13 Jul 1998 4 Apr 2000 International Business Machines Corporation Relational database extenders for handling complex data types
US6073232 25 Feb 1997 6 Jun 2000 International Business Machines Corporation Method for minimizing a computer's initial program load time after a system reset or a power-on using non-volatile storage
US6092160 26 Sep 1997 18 Jul 2000 Nokia Mobile Phones Limited Memory management method
US6098075 16 Dec 1997 1 Aug 2000 International Business Machines Corporation Deferred referential integrity checking based on determining whether row at-a-time referential integrity checking would yield the same results as deferred integrity checking
US6108004 21 Oct 1997 22 Aug 2000 International Business Machines Corporation GUI guide for data mining
US6112024 2 Oct 1996 29 Aug 2000 Sybase, Inc. Development system providing methods for managing different versions of objects with a meta model
US6122685 6 May 1998 19 Sep 2000 Emc Corporation System for improving the performance of a disk storage device by reconfiguring a logical volume of data in response to the type of operations being performed
US6148368 31 Jul 1997 14 Nov 2000 Lsi Logic Corporation Method for accelerating disk array write operations using segmented cache memory and data logging
US6189071 28 Aug 1998 13 Feb 2001 Emc Corporation Method for maximizing sequential output in a disk array storage device
US6209088 21 Sep 1998 27 Mar 2001 Microsoft Corporation Computer hibernation implemented by a computer operating system
US6230233 13 Sep 1991 8 May 2001 Sandisk Corporation Wear leveling techniques for flash EEPROM systems
US6237065 14 May 1999 22 May 2001 Hewlett-Packard Company Preemptive replacement strategy for a caching dynamic translator
US6240414 19 Aug 1998 29 May 2001 Eisolutions, Inc. Method of resolving data conflicts in a shared data environment
US6249841 3 Dec 1998 19 Jun 2001 Ramtron International Corporation Integrated circuit memory device and method incorporating flash and ferroelectric random access memory arrays
US6272534 27 Jul 1999 7 Aug 2001 Storage Technology Corporation Method and system for efficiently storing web pages for quick downloading at a remote device
US6275436 23 May 2000 14 Aug 2001 Hitachi, Ltd Flash memory control method and apparatus processing system therewith
US6298428 30 Mar 1998 2 Oct 2001 International Business Machines Corporation Method and apparatus for shared persistent virtual storage on existing operating systems
US6301635 26 Sep 1997 9 Oct 2001 Nokia Mobile Phones Limited Memory device
US6311232 29 Jul 1999 30 Oct 2001 Compaq Computer Corporation Method and apparatus for configuring storage devices
US6314433 12 Jun 1998 6 Nov 2001 Hewlett-Packard Company Frame-based heroic data recovery
US6317806 20 May 1999 13 Nov 2001 International Business Machines Corporation Static queue and index queue for storing values identifying static queue locations
US6321234 8 Nov 1996 20 Nov 2001 Sybase, Inc. Database server system with improved methods for logging transactions
US6338056 22 Apr 1999 8 Jan 2002 International Business Machines Corporation Relational database extender that supports user-defined index types and user-defined search
US6345000 25 Nov 1998 5 Feb 2002 Sandisk Corporation Flash memory permitting simultaneous read/write and erase operations in a single memory array
US6366996 24 Jan 2000 2 Apr 2002 Pmc-Sierra, Inc. Page memory management in non time critical data buffering applications
US6370534 1 Jun 1999 9 Apr 2002 Pliant Technologies, Inc. Blocking techniques for data storage
US6370541 21 Sep 1999 9 Apr 2002 International Business Machines Corporation Design and implementation of a client/server framework for federated multi-search and update across heterogeneous datastores
US6378043 31 Dec 1998 23 Apr 2002 Oracle Corporation Reward based cache management
US6401093 31 Mar 1999 4 Jun 2002 International Business Machines Corporation Cross file system caching and synchronization
US6408058 27 Jul 1998 18 Jun 2002 Adl Systems S.A. Telewriting device
US6418510 14 Sep 2000 9 Jul 2002 International Business Machines Corporation Cooperative cache and rotational positioning optimization (RPO) scheme for a direct access storage device (DASD)
US6425057 27 Aug 1998 23 Jul 2002 Hewlett-Packard Company Caching protocol method and system based on request frequency and relative storage duration
US6438750 18 Jun 1999 20 Aug 2002 Phoenix Technologies Ltd. Determining loading time of an operating system
US6454159 11 Aug 2000 24 Sep 2002 International Business Machines Corporation Method for forming electrical connecting structure
US6477564 15 Jun 1999 5 Nov 2002 Bull S.A. Process for transforming and routing data between agent servers present in some machines and a central agent server present in another machine
US6505205 3 Jan 2002 7 Jan 2003 Oracle Corporation Relational database system for storing nodes of a hierarchical index of multi-dimensional data in a first module and metadata regarding the index in a second module
US6516380 5 Feb 2001 4 Feb 2003 International Business Machines Corporation System and method for a log-based non-volatile write cache in a storage controller
US6519597 2 Jun 1999 11 Feb 2003 International Business Machines Corporation Method and apparatus for indexing structured documents with rich data types
US6535949 19 Apr 1999 18 Mar 2003 Research In Motion Limited Portable electronic device having a log-structured file system in flash memory
US6539456 13 Oct 1999 25 Mar 2003 Intel Corporation Hardware acceleration of boot-up utilizing a non-volatile disk cache
US6542904 30 Jul 1999 1 Apr 2003 International Business Machines Corporation Method and system for efficiently providing maintenance activity on a relational database that is utilized within a processing system
US6557077 7 Jul 2000 29 Apr 2003 Lsi Logic Corporation Transportable memory apparatus and associated methods of initializing a computer system having the same
US6567889 19 Dec 1997 20 May 2003 Lsi Logic Corporation Apparatus and method to provide virtual solid state disk in cache memory in a storage controller
US6578046 5 Jun 2001 10 Jun 2003 International Business Machines Corporation Federated searches of heterogeneous datastores using a federated datastore object
US6615313 9 Feb 2001 2 Sep 2003 Fujitsu Limited Disk input/output control device maintaining write data in multiple cache memory modules and method and medium thereof
US6629201 2 May 2001 30 Sep 2003 Superspeed Software, Inc. System and method for high-speed substitute cache
US6636942 5 Oct 2001 21 Oct 2003 International Business Machines Corporation Storage structure for storing formatted data on a random access medium
US6647472 14 Feb 2003 11 Nov 2003 Hewlett-Packard Development Company, L.P. Fast suspend to disk
US6651141 29 Dec 2000 18 Nov 2003 Intel Corporation System and method for populating cache servers with popular media contents
US6671699 20 May 2000 30 Dec 2003 Equipe Communications Corporation Shared database usage in network devices
US6684229 23 Feb 1999 27 Jan 2004 Adaptec, Inc. Method of generating a database for use in an intelligent backup and restoring system
US6687158 21 Dec 2001 3 Feb 2004 Fujitsu Limited Gapless programming for a NAND type flash memory
US6714935 21 Sep 1998 30 Mar 2004 Microsoft Corporation Management of non-persistent data in a persistent database
US6721863 11 Sep 2000 13 Apr 2004 Kabushiki Kaisha Toshiba Disk control mechanism preferable for random disk write
US6742097 30 Jul 2001 25 May 2004 Rambus Inc. Consolidation of allocated memory to reduce power consumption
US6760736 20 Dec 2000 6 Jul 2004 Sun Microsystems, Inc. Methods and systems for distributed failure detection and recovery using leasing techniques
US6769050 10 Sep 2001 27 Jul 2004 Rambus Inc. Techniques for increasing bandwidth in port-per-module memory systems having mismatched memory modules
US6771536 27 Feb 2002 3 Aug 2004 Sandisk Corporation Operating techniques for reducing program and read disturbs of a non-volatile memory
US6772178 27 Jul 2001 3 Aug 2004 Sun Microsystems, Inc. Method and apparatus for managing remote data replication in a distributed computer system
US6782453 12 Feb 2002 24 Aug 2004 Hewlett-Packard Development Company, L.P. Storing data in memory
US6788612 25 Apr 2003 7 Sep 2004 Aplus Flash Technology, Inc. Flash memory array structure suitable for multiple simultaneous operations
US6877081 13 Feb 2001 5 Apr 2005 International Business Machines Corporation System and method for managing memory compression transparent to an operating system
US6879266 14 Jul 2000 12 Apr 2005 Quickshift, Inc. Memory module including scalable embedded parallel data compression and decompression engines
US6901499 27 Feb 2002 31 May 2005 Microsoft Corp. System and method for tracking data stored in a flash memory device
US6910106 20 Dec 2002 21 Jun 2005 Microsoft Corporation Methods and mechanisms for proactive memory management
US6918022 28 Feb 2001 12 Jul 2005 Intel Corporation Memory space organization
US6928521 1 Aug 2000 9 Aug 2005 International Business Machines Corporation Method, system, and data structures for using metadata in updating data in a storage device
US6930919 26 Feb 2004 16 Aug 2005 Samsung Electronics Co., Ltd. NAND-type flash memory device having array of status cells for storing block erase/program information
US6938116 31 Dec 2001 30 Aug 2005 Samsung Electronics Co., Ltd. Flash memory management method
US6941423 22 Dec 2003 6 Sep 2005 Intel Corporation Non-volatile mass storage cache coherency apparatus
US6959318 6 Mar 1998 25 Oct 2005 Intel Corporation Method of proxy-assisted predictive pre-fetching with transcoding
US7007072 22 Jun 2001 28 Feb 2006 Storage Technology Corporation Method and system for efficiently storing web pages for quick downloading at a remote device
US7010645 27 Dec 2002 7 Mar 2006 International Business Machines Corporation System and method for sequentially staging received data to a write cache in advance of storing the received data
US7017037 27 Jun 2002 21 Mar 2006 Microsoft Corporation Apparatus and method to decrease boot time and hibernate awaken time of a computer system utilizing disk spin-up-time
US7036040 26 Nov 2002 25 Apr 2006 Microsoft Corporation Reliability of diskless network-bootable computers using non-volatile memory cache
US7039765 19 Dec 2002 2 May 2006 Hewlett-Packard Development Company, L.P. Techniques for cache memory management using read and write operations
US7043610 5 May 2003 9 May 2006 Aristos Logic Corporation System and method for maintaining cache coherency without external controller intervention
US7057942 28 Dec 2004 6 Jun 2006 Kabushiki Kaisha Toshiba Memory management device and memory device
US7062675 25 Jun 2002 13 Jun 2006 Emc Corporation Data storage cache system shutdown scheme
US7065627 25 Mar 2002 20 Jun 2006 International Business Machines Corporation Method and system for providing an event driven image for a boot record
US7068575 30 Jul 2003 27 Jun 2006 Microsoft Corporation High speed optical disc recording
US7082495 21 Feb 2003 25 Jul 2006 Microsoft Corporation Method and apparatus to reduce power consumption and improve read/write performance of hard disk drives using non-volatile memory
US7082499 3 Oct 2002 25 Jul 2006 Sharp Kabushiki Kaisha External memory control device regularly reading ahead data from external memory for storage in cache memory, and data driven type information processing apparatus including the same
US7143120 3 May 2004 28 Nov 2006 Microsoft Corporation Systems and methods for automated maintenance and repair of database and file systems
US7171532 30 Aug 2004 30 Jan 2007 Hitachi, Ltd. Method and system for data lifecycle management in an external storage linkage environment
US7185155 9 Jun 2005 27 Feb 2007 Microsoft Corporation Methods and mechanisms for proactive memory management
US7231497 15 Jun 2004 12 Jun 2007 Intel Corporation Merging write-back and write-through cache policies
US7284149 16 Oct 2002 16 Oct 2007 Ken Scott Fisher Intermittent connection protection for external computer devices
US7366740 30 Jul 2004 29 Apr 2008 Microsoft Corporation Systems and methods for automatic maintenance and repair of enitites in a data model
US7366866 30 Oct 2003 29 Apr 2008 Hewlett-Packard Development Company, L.P. Block size allocation in copy operations
US7380090 14 Apr 2006 27 May 2008 Hitachi, Ltd. Storage device and control method for the same
US7395401 30 Sep 2005 1 Jul 2008 Sigmatel, Inc. System and methods for accessing solid-state memory devices
US7409537 6 Oct 2005 5 Aug 2008 Microsoft Corporation Fast booting an operating system from an off state
US7412369 9 Jun 2000 12 Aug 2008 Stmicroelectronics, Inc. System and method for designing and optimizing the memory of an embedded processing system
US7412562 17 Oct 2005 12 Aug 2008 Intel Corporation Using non-volatile memories for disk caching of partition table entries
US7451353 23 Dec 2005 11 Nov 2008 Intel Corporation Cache disassociation detection
US7490197 21 Oct 2004 10 Feb 2009 Microsoft Corporation Using external memory devices to improve system performance
US7631140 27 Apr 2005 8 Dec 2009 Panasonic Corporation Data accessing method, device in which the data accessing method is executed and recording medium
US7644239 3 May 2004 5 Jan 2010 Microsoft Corporation Non-volatile memory cache performance improvement
US7698513 9 Jun 2005 13 Apr 2010 Microsoft Corporation Methods and mechanisms for proactive memory management
US7774508 29 Nov 2004 10 Aug 2010 Panasonic Corporation Electronic apparatus, control method thereof, host device, and control method thereof
US7805571 5 Feb 2009 28 Sep 2010 Microsoft Corporation Using external memory devices to improve system performance
US7814261 6 Dec 2004 12 Oct 2010 Samsung Electronics Co., Ltd. Flash memory and method of dynamically loading firmware operation module in optical drive
US7818701 22 Dec 2006 19 Oct 2010 Cypress Semiconductor Corporation Memory controller with variable zone size
US7945734 10 Aug 2007 17 May 2011 Eastman Kodak Company Removable storage device with code to allow change detection
US7953774 19 Sep 2008 31 May 2011 Microsoft Corporation Aggregation of write traffic to a data store
US8006037 6 May 2010 23 Aug 2011 Microsoft Corporation Using external memory devices to improve system performance
US8032723 13 Apr 2010 4 Oct 2011 Microsoft Corporation Methods and mechanisms for proactive memory management
US8108450 15 Apr 2011 31 Jan 2012 Microsoft Corporation Aggregation of write traffic to a data store
US8255645 13 Sep 2011 28 Aug 2012 Microsoft Corporation Non-volatile memory cache performance improvement
US9764877 2 Jun 2014 19 Sep 2017 Tr Holdings Inc. Capped container
US20010007123 1 Feb 2001 5 Jul 2001 Nobuyuki Seguchi Stored program controlled switching system
US20010007999 23 Feb 2001 12 Jul 2001 Rasmussen Norman J. High-throughput interface between a system memory controller and a peripheral device
US20010047462 31 Jul 2001 29 Nov 2001 Dimitroff John E. Cascaded removable media data storage system
US20020004876 12 Dec 2000 10 Jan 2002 Fee Computation Data processor with cache
US20020073276 8 Dec 2000 13 Jun 2002 Howard John H. Data storage system and method employing a write-ahead hash log
US20020083275 * 30 Aug 2001 27 Jun 2002 Shinichi Kawamoto Cache coherent control system
US20020087797 29 Dec 2000 4 Jul 2002 Farid Adrangi System and method for populating cache servers with popular media contents
US20020091702 15 Nov 2001 11 Jul 2002 Ward Mullins Dynamic object-driven database manipulation and mapping system
US20020108017 5 Feb 2001 8 Aug 2002 International Business Machines Corporation System and method for a log-based non-volatile write cache in a storage controller
US20020143521 10 Dec 2001 3 Oct 2002 Call Charles G. Methods and apparatus for storing and manipulating variable length and fixed length data elements as a sequence of fixed length integers
US20020152422 26 Mar 2001 17 Oct 2002 Rahul Sharma Method and apparatus for managing replicated and migration capable session state for a Java platform
US20020156970 13 Oct 1999 24 Oct 2002 David C. Stewart Hardware acceleration of boot-up utilizing a non-volatile disk cache
US20020171966 16 May 2001 21 Nov 2002 International Business Machines Corporation Power savings method and apparatus for disk drives
US20020178326 21 May 2002 28 Nov 2002 Fujitsu Limited Storage unit
US20020198891 14 Jun 2001 26 Dec 2002 International Business Machines Corporation Methods and apparatus for constructing and implementing a universal extension module for processing objects in a database
US20020199075 21 Jun 2001 26 Dec 2002 International Business Machines Corporation Method of allocating physical memory space having pinned and non-pinned regions
US20030074550 16 Oct 2001 17 Apr 2003 Wilks Andrew W. Method for allowing CD removal when booting embedded OS from a CD-ROM device
US20030101320 29 May 2002 29 May 2003 Gerard Chauvel Cache with selective write allocation
US20030110357 14 Nov 2001 12 Jun 2003 Nguyen Phillip V. Weight based disk cache replacement method
US20030154314 7 Feb 2003 14 Aug 2003 I/O Integrity, Inc. Redirecting local disk traffic to network attached storage
US20030154337 25 Feb 2003 14 Aug 2003 Hiroshi Ohno Multiple operating system control method
US20030158839 26 Mar 2002 21 Aug 2003 Yaroslav Faybishenko System and method for determining relevancy of query responses in a distributed network search mechanism
US20030177305 18 Mar 2002 18 Sep 2003 Hetrick William A. Method and apparatus for using a solid state disk device as a storage controller cache
US20030191916 4 Apr 2002 9 Oct 2003 International Business Machines Corporation Apparatus and method of cascading backup logical volume mirrors
US20030202377 16 Apr 2003 30 Oct 2003 Eliyahou Harari Flash EEprom system
US20030212660 8 May 2003 13 Nov 2003 Kerwin Douglas W. Database scattering system
US20030212857 9 May 2002 13 Nov 2003 International Business Machines Corporation Adaptive startup policy for accelerating multi-disk array spin-up
US20040003003 26 Jun 2002 1 Jan 2004 Microsoft Corporation Data publishing systems and methods
US20040003223 27 Jun 2002 1 Jan 2004 Microsoft Corporation Apparatus and method to decrease boot time and hibernate awaken time of a computer system
US20040010639 9 Jul 2003 15 Jan 2004 Hitachi, Ltd. External storage subsystem
US20040019762 16 Jul 2003 29 Jan 2004 Hitachi, Ltd. Semiconductor integrated circuit
US20040024795 10 Apr 2001 5 Feb 2004 Hugh Hind System and method for synchronizing data records between multiple databases
US20040034765 9 Oct 2002 19 Feb 2004 James O?Apos;Connell Daniel Method and apparatus for booting a computer system
US20040059747 23 Sep 2003 25 Mar 2004 Olarig Sompong P. Method and apparatus for restoring computer resources
US20040068627 20 Dec 2002 8 Apr 2004 Stuart Sechrest Methods and mechanisms for proactive memory management
US20040078508 2 Oct 2003 22 Apr 2004 Rivard William G. System and method for high performance data storage and retrieval
US20040093463 17 Oct 2003 13 May 2004 Rung-Ji Shang RAID-5 disk having cache memory implemented using non-volatile RAM
US20040103238 26 Nov 2002 27 May 2004 M-Systems Flash Disk Pioneers Ltd. Appliance, including a flash memory, that is robust under power failure
US20040107200 25 Nov 2003 3 Jun 2004 Bjorn-Harald Sjogren Database constraint enforcer
US20040136259 10 Sep 2003 15 Jul 2004 Nokia Corporation Memory structure, a system, and an electronic device, as well as a method in connection with a memory circuit
US20040153694 26 Nov 2002 5 Aug 2004 Microsoft Corporation Reliability of diskless network-bootable computers using non-volatile memory cache
US20040162950 22 Dec 2003 19 Aug 2004 Coulson Richard L. Non-volatile mass storage cache coherency apparatus
US20040168018 27 Feb 2004 26 Aug 2004 Aasheim Jered Donald Free sector manager for data stored in flash memory devices
US20040172576 27 Sep 2002 2 Sep 2004 Takeo Yoshii Data writing apparatus, data writing method, and program
US20040174631 9 Mar 2004 9 Sep 2004 Hideaki Tanaka High reliability storage drive and data write method
US20040221089 31 Dec 2003 4 Nov 2004 Fujitsu Prime Software Technologies Limited Cache control program
US20040230743 8 Jun 2004 18 Nov 2004 Rambus Inc. Techniques for increasing bandwidth in port-per-module memory systems having mismatched memory modules
US20040243612 30 May 2003 2 Dec 2004 Microsoft Corporation System and method for resizing a database
US20050005188 20 Jun 2003 6 Jan 2005 International Business Machines Corporation Preserving cache data against cluster reboot
US20050021907 11 Sep 2003 27 Jan 2005 Kentaro Shimada Storage system and a method of speeding up writing data into the storage system
US20050111260 21 Dec 2004 26 May 2005 Micron Technology, Inc. Boosted substrate/tub programming for flash memories
US20050125708 26 Jan 2004 9 Jun 2005 Texas Instruments Incorporated Method for streamlining error connection code computation while reading or programming a NAND flash memory
US20050138283 18 Dec 2003 23 Jun 2005 Garney John I. Writing cache lines on a disk drive
US20050141284 23 Sep 2004 30 Jun 2005 Takuya Futatsuyama Pattern layout of word line transfer transistors in NAND flash memory which executes subblock erase
US20050145923 6 Jan 2004 7 Jul 2005 Chiou-Feng Chen NAND flash memory with enhanced program and erase performance, and fabrication process
US20050149750 31 Dec 2003 7 Jul 2005 International Business Machines Corporation Method and system for diagnosing operation of tamper-resistant software
US20050160223 15 Jan 2004 21 Jul 2005 Super Talent Electronics Inc. Dual-Mode Flash Storage Exchanger that Transfers Flash-Card Data to a Removable USB Flash Key-Drive With or Without a PC Host
US20050172067 4 Feb 2004 4 Aug 2005 Sandisk Corporation Mass storage accelerator
US20050193160 6 Jul 2004 1 Sep 2005 Sybase, Inc. Database System Providing Methodology for Extended Memory Support
US20050204091 11 Mar 2004 15 Sep 2005 Kilbuck Kevin M. Non-volatile memory with synchronous DRAM interface
US20050228964 9 Jun 2005 13 Oct 2005 Microsoft Corporation Methods and mechanisms for proactive memory management
US20050239494 23 Jul 2003 27 Oct 2005 Research In Motion Limited Data store management system and method for wireless devices
US20050246487 3 May 2004 3 Nov 2005 Microsoft Corporation Non-volatile memory cache performance improvement
US20050262378 30 Jul 2004 24 Nov 2005 Microsoft Corporation Systems and methods for automatic maintenance and repair of enitites in a data model
US20050286855 19 Apr 2004 29 Dec 2005 Matsushita Electric Industrial Co., Ltd. Data recording apparatus
US20060010293 6 Jul 2005 12 Jan 2006 Schnapp Michael G Cache for file system used in storage system
US20060074953 30 Sep 2004 6 Apr 2006 International Business Machines Corporation Metadata management for a data abstraction model
US20060075185 6 Oct 2004 6 Apr 2006 Dell Products L.P. Method for caching data and power conservation in an information handling system
US20060080553 8 Oct 2004 13 Apr 2006 International Business Machines Corporation Secure memory caching structures for data, integrity and version values
US20060087893 18 Oct 2005 27 Apr 2006 Sony Corporation Storage device and information processing system
US20060106889 12 Nov 2004 18 May 2006 Mannby Claes-Fredrik U Method, system, and program for managing revisions to a file
US20060112195 21 Nov 2005 25 May 2006 Canon Kabushiki Kaisha Electronic device and control method therefor
US20060112215 21 Nov 2005 25 May 2006 Samsung Electronics Co., Ltd. Apparatus and method for processing data of flash memory
US20060136472 20 Dec 2004 22 Jun 2006 Venkateswararao Jujjuri Achieving cache consistency while allowing concurrent changes to metadata
US20060136664 16 Dec 2004 22 Jun 2006 Trika Sanjeev N Method, apparatus and system for disk caching in a dual boot environment
US20060155931 10 Jan 2005 13 Jul 2006 Microsoft Corporation System and methods for an overlay disk and cache using portable flash memory
US20060177067 3 Feb 2006 10 Aug 2006 Samsung Electronics Co., Ltd. Hybrid broadcast encryption method
US20060236034 19 Apr 2005 19 Oct 2006 Pomaranski Ken G External state cache for computer processor
US20060248276 28 Apr 2005 2 Nov 2006 Frank Kilian Cache monitoring using shared memory
US20060277359 6 Jun 2005 7 Dec 2006 Faber Robert W Blank memory location detection mechanism
US20070005882 30 Jan 2006 4 Jan 2007 Gallagher William J System and method for scheduling disk writes in an application server or transactional environment
US20070011405 11 Jul 2005 11 Jan 2007 Adusumilli Vijay P High-speed interface for high-density flash with two levels of pipelined cache
US20070043787 17 Aug 2005 22 Feb 2007 Cannon David M Maintaining an aggregate including active files in a storage pool in a random access medium
US20070043929 17 Aug 2005 22 Feb 2007 Kevin Safford System and method for responding to TLB misses
US20070061511 * 15 Sep 2005 15 Mar 2007 Faber Robert W Distributed and packed metadata structure for disk cache
US20070073764 28 Nov 2006 29 Mar 2007 Microsoft Corporation Systems and methods for automatic database or file system maintenance and repair
US20070150966 22 Dec 2005 28 Jun 2007 Kirschner Wesley A Method and apparatus for maintaining a secure software boundary
US20070156954 29 Dec 2005 5 Jul 2007 Intel Corporation Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessiblity
US20070207800 20 Feb 2007 6 Sep 2007 Daley Robert C Diagnostics And Monitoring Services In A Mobile Network For A Mobile Device
US20070208910 14 Apr 2006 6 Sep 2007 Hitachi, Ltd. Storage device and control method for the same
US20070233939 29 Mar 2007 4 Oct 2007 Mosaid Technologies Incorporated Flash memory system control scheme
US20070294474 20 Jun 2006 20 Dec 2007 Microsoft Corporation Efficiently synchronizing with separated disk caches
US20080010401 17 Sep 2007 10 Jan 2008 Intel Corporation Cache write integrity logging
US20080010415 5 Jul 2006 10 Jan 2008 International Business Machines Corporation A pseudo lru tree-based priority cache
US20080162485 14 Mar 2008 3 Jul 2008 Long David J Transaction-Aware Caching for Access Control Metadata
US20080172519 1 Jul 2007 17 Jul 2008 Sandisk Il Ltd. Methods For Supporting Readydrive And Readyboost Accelerators In A Single Flash-Memory Storage Device
US20080183958 25 Jan 2008 31 Jul 2008 Cheriton David R Hierarchical immutable content-addressable memory processor
US20090144495 5 Feb 2009 4 Jun 2009 Microsoft Corporation Using external memory devices to improve system performance
US20090150335 6 Dec 2007 11 Jun 2009 Fernando Latorre Achieving coherence between dynamically optimized code and original code
US20090150599 18 Nov 2008 11 Jun 2009 Bennett Jon C R Method and system for storage of data in non-volatile media
US20090150611 10 Dec 2007 11 Jun 2009 Microsoft Corporation Management of external memory functioning as virtual cache
US20090287890 15 May 2008 19 Nov 2009 Microsoft Corporation Optimizing write traffic to a disk
US20100070701 14 Nov 2008 18 Mar 2010 Microsoft Corporation Managing cache data and metadata
US20100070747 14 Nov 2008 18 Mar 2010 Microsoft Corporation Managing cache data and metadata
US20100082550 19 Sep 2008 1 Apr 2010 Microsoft Corporation Aggregation of write traffic to a data store
US20100199043 13 Apr 2010 5 Aug 2010 Microsoft Corporation Methods and mechanisms for proactive memory management
US20100199063 13 Apr 2010 5 Aug 2010 Microsoft Corporation Methods and mechanisms for proactive memory management
US20100217929 6 May 2010 26 Aug 2010 Microsoft Corporation Using External Memory Devices to Improve System Performance
US20110197016 15 Apr 2011 11 Aug 2011 Microsoft Corporation Aggregation of Write Traffic to a Data Store
US20110276743 21 Jul 2011 10 Nov 2011 Microsoft Corporation Using external memory devices to improve system performance
US20110314202 30 Aug 2011 22 Dec 2011 Microsoft Corporation Managing cache data and metadata
US20120047323 2 Nov 2011 23 Feb 2012 Microsoft Corporation Boot management of non-volatile memory
US20120102265 5 Jan 2012 26 Apr 2012 Microsoft Corporation Aggregation of Write Traffic to a Data Store
CN1266229C 10 Aug 2004 26 Jul 2006 汕头市龙华珠光颜料有限公司 Pigment of multi-gradition discolour at diffierent direction and production process thereof
CN1465009A 1 Jun 2001 31 Dec 2003 英特尔公司 Non-volatile cache integrated with mass storage device
EP0547992A2 19 Nov 1992 23 Jun 1993 International Business Machines Corporation Method and system for enhanced efficiency of data recovery in balanced tree memory structures
EP0712067B1 8 Nov 1995 31 Jul 2002 Mitsubishi Denki Kabushiki Kaisha Flash disk card
EP0744697A1 21 May 1996 27 Nov 1996 Symbios Logic Inc. Method and apparatus for transferring data between computer devices
RU2010317C1 Title not available
TW479194B Title not available
TW502165B Title not available
1 "Computervision Launches Design Automation Development Platform for Windows, UNIX Desktop Applications", PR Newswire, Jan. 10, 1995.
2 "Developer's Guide to Apple Data Detectors-For Version 1.0.2", Apple Computer, Inc., Dec. 1, 1997.
3 "Developer's Guide to Apple Data Detectors—For Version 1.0.2", Apple Computer, Inc., Dec. 1, 1997.
4 "Improved Recovery from Partial Page Writes of Data Pages", IBM Technical Disclosure Bulletin, vol. 36, No. 05, May 1993.
5 "Mechanical Design Software", Computer-Aided Engineering, Dec. 1993.
6 "Non-Volatile Memory Host Controller Interface (NVMHCI) 1.0", Apr. 14, 2008. ftp://download.intel.com/standards/nvmhci/spec.pdf.
7 "Optimization of CF Host Operation," SanDisk® Corporation, Feb. 28, 2005.
8 "Optimizing Program/Erase Times", Spansion™, Sep. 2, 2004.
9 "Oracle9i SQL Reference", Release 2 (9.2), Oct. 2002.
10 "Referential Integrity Implementation Details and Advantages", IBM Technical Disclosure Bulletin, vol. 38, No. 03, Mar. 1995.
11 Allchin, "Microsoft Explains Vista ReadyBoost," CDRinfo, Nov. 21, 2006.
12 Anderson, "A Case for Buffer Servers", Proceedings of the Seventh Workshop on Hot Topics in Operating Systems, Mar. 28-30, 1999.
13 Andrews, "Combining Language and Database Advances in an Object-Oriented Development Environment", Conference on Object-Oriented Programming Systems, Languages, and Applications(OOPSLA'87), Oct. 4-8, 1987.
14 Archer, "ReadyBoost Q&A," Jun. 2, 2006.
15 Archer, "ReadyBoost-Using Your USB Key to Speed Up Windows Vista," Apr. 14, 2006.
16 Archer, "ReadyBoost—Using Your USB Key to Speed Up Windows Vista," Apr. 14, 2006.
17 Beard, "Multilevel and Graphical Views of Metadata", Fifth International Forum on Research and Technology Advances in Digital Libraries, Apr. 22-24, 1998.
18 Beitner, "Multimedia Support and Authoring in Microcosm: an extended model", 1994.
19 Berg, "How Do I Create Persistent Java Objects?", Dr. Dobb's Journal, Apr. 1997.
20 Bhattacharya, "Coordinating Backup/Recovery and Data Consistency Between Database and File Systems", Proceedings of the 2002 ACM SIGMOD International Conference on Management of Data, Jun. 3-6, 2002.
21 Billiris, "The Performance of Three Database Storage Structures for Managing Large Objects", Proceedings of the 1992 ACM SIGMOD International Conference on Management of Data, Jun. 2-5, 1992.
22 Bisson, et al., "A Hybrid Disk-Aware Spin-Down Algorithm with I/O Subsystem Support", Department of Computer Science, University of California, Santa Cruz. http://www.soe.ucsc.edu/~tbisson/papers/bisson-ipccc07.pdf.
23 Bisson, et al., "A Hybrid Disk-Aware Spin-Down Algorithm with I/O Subsystem Support", Department of Computer Science, University of California, Santa Cruz. http://www.soe.ucsc.edu/˜tbisson/papers/bisson—ipccc07.pdf.
24 Booch, "Object-Oriented Analysis and Design with Applications", The Benjainin/Cummings Publishing Company, Inc., 1994.
25 Bracchi, "Binary Logical Associations in Data Modelling", Modelling in Data Base Management Systems, Proceedings of the IFIP Working Conference on Modelling in Data Base Management Systems, Jan. 5-8, 1976.
26 Budiu, "A Dual-Disk File System: ext4", Apr. 16, 1997.
27 Bullock, "Recovery of Data Pages After Partial Page Writes", IBM Technical Disclosure Bulletin, Aug. 1, 1991.
28 Buneman, "Inheritance and Persistence in Database Programming Languages", Proceedings of the 1986 ACM SIGMOD International Conference on Management of Data, May 28-30, 1986.
29 CA Examiner's Report for Application No. 2,523,761, Feb. 26, 2013.
30 Cammarata, "Extending a Relational Database with Deferred Referential Integrity Checking and Intelligent Joins", Proceedings of the 1989 ACM SIGMOD International Conference on Management of Data, May 31-Jun. 2, 1989.
31 Chien, "Concurrent Aggregates (CA): Design and Experience with a Concurrent Object-Oriented Language Based on Aggregates", Journal of Parallel and Distributed Computing, Mar. 1995.
32 Chryssostomidis; "Geometric Modeling Issues in Computer Aided Design of Marine Structures", Marine Technology Society Journal, vol. 22, No. 2, Dec. 1988.
33 Ciccozzi, "Microsoft Press Computer Dictionary", Third Edition, 1997.
34 CN Decision on Rejection for Application No. 200680047384.6, Nov. 11, 2010.
35 CN Notice on First Office Action for Application No. 200510083792.4, Feb. 1, 2008.
36 CN Notice on First Office Action for Application No. 200510116208.0, Jun. 6, 2008.
37 CN Notice on the First Office Action for Application No. 200960145878.1, Jan. 29, 2013.
38 CN Notice on the First Office Action for Application No. 200980136912.9, Jan. 14, 2013.
39 CN Notice on the First Office Action for Application No. 200980137190.9, Oct. 24, 2012.
40 CN Notice on the First Office Action for Application No. 200980145878.1, Jan. 29, 2013.
41 CN Notice on the Second Office Action for Application No. 200980137190.9, Mar. 20, 2013.
42 CN The First Office Action for Application No. 200680047384.6, Jan. 22, 2010.
43 CN The Second Office Action for Application No. 200510083792.4, Jun. 27, 2008.
44 D'Andrea, "UniSQL's Next-Generation Object-Relational Database Management System", Proceedings of the 1996 ACM SIGMOD International Conference on Management of Data, vol. 25, No. 3, Sep. 1996.
45 Darby, "Object Serialization in Java 1.1: Making Objects Persistent", WEB Techniques, Sep. 1997.
46 Darden, "Data Integrity: The Dell|EMC Distinction". http://www.dell.com/content/topics/global.aspx/power/en/ps2q02-darden?c=us&cs=555&1=en&s=biz.
47 Darden, "Data Integrity: The Dell|EMC Distinction". http://www.dell.com/content/topics/global.aspx/power/en/ps2q02—darden?c=us&cs=555&1=en&s=biz.
48 Dietrich, Jr., "TGMS: An Object-Oriented System for Programming Geometry", Software-Practice and Experience, Oct. 1989.
49 Dobashi, "Skylight for Interior Lighting Design", Eurographics '94 Conference Proceedings, vol. 13, No. 3, 1994.
50 Dorsch, "Accel signs with IBM to buy Altium PCB unit-Accel Technologies acquires the assets to Altium's P-CAD business unit", LookSmart's FindArticles, Electronic News, Jan. 16, 1995.
51 Dorsch, "Accel signs with IBM to buy Altium PCB unit—Accel Technologies acquires the assets to Altium's P-CAD business unit", LookSmart's FindArticles, Electronic News, Jan. 16, 1995.
52 Dove, "Windows XP for embedded applications", Jul. 10, 2008.
53 Ekman, "TLB and Snoop Energy-Reduction using Virtual Caches in Low-Power Chip-Multiprocessors," Aug. 12, 2002.
54 EP Communication for Application No. 03022573.4-1229, Reference EP28554-/df, Aug. 2, 2007.
55 EP Communication for Application No. 03022573.4-1229, Reference EP28554-/df, Nov. 8, 2007.
56 EP Communication for Application No. 03022573.4-1229, Reference EP28554-/df, Oct. 6, 2008.
57 EP Communication for Application No. 05103690.3-2201, Reference EP34981TE900kap, Apr. 24, 2008.
58 EP Communication for Application No. 05103697.8-2201, Reference EP34979TE900dfi, Jun. 17, 2008.
59 EP Communication for Application No. 05103697.8-2201, Reference EP34979TE900dfi, May 21, 2007.
60 EP Communication for Application No. 05103697.8-2201, Reference EP34979TE900dfi, Nov. 7, 2008.
61 EP Communication for Application No. 05103697.8-2201, Reference EP34979TE900dfi, Oct. 26, 2007.
62 EP Communication for Application No. 05109295.5-2201, Reference EP3683ORK900dfi, Jun. 8, 2007.
63 EP Communication for Application No. 09813565.0-1229 / 2329360 PCT/US2009056419, Reference FB24240, Apr. 3, 2012.
64 EP Communication for Application No. 09813565.0-1229/2329360 PCT/US2009056419, Apr. 3, 2012.
65 EP Communication for Application No. 09814983.4-2224/2329361 PCT/US2009055198, Reference FB24231, Oct. 10, 2012.
66 EP Communication for Application No. 09826570.5-1229 / 2353081 PCT/US2009063127, Reference FB24586, May 29, 2012.
67 EP Communication for Application No. 09826570.5-1229/2353081 PCT/US2009063127, Reference FB24586, May 29, 2012.
68 EP Decision to refuse a European Patent for Application No. 05109295.5-2201, Reference EP36830RK900dfi, Aug. 7, 2012.
69 EP Provision of a copy of the minutes for Application No. 05109295.5-2201, Reference EP36830RK900dfi, Aug. 7, 2012.
70 EP Summons to attend oral proceedings for Application No. 05109295.5-2201/1650666, Reference EP36830RK900dfi, Mar. 8, 2012.
71 EP Supplementary Search Report for Application No. 06839426, May 4, 2009.
72 Fegaras, "Optimizing Object Queries Using an Effective Calculus", ACM Transactions on Database Systems, vol. 25, No. 4, Dec. 2000.
73 Findler, "Contract Soundness for Object-Oriented Languages", Proceedings of the 2001 ACM SIGPLAN Conference on Object-Oriented Programming Systems, Languages and Applications, Oct. 14-18, 2001.
74 Foley, "Computer Graphics: Principles and Practices", Second Edition, Addison-Wesley Publishing Company, Chapter 5, pp. 201-227, 1990.
75 Fox, "Invention: The phantom car", NewScientist.com, Aug. 17, 2005.
76 Friis-Christensen, "Requirements and Research Issues in Geographic Data Modeling", Proceedings of the 9th ACM International Symposium on Advances in Geographic Information Systems, Nov. 9-10, 2001.
77 Fuh, "Implementation of SQL3 Structured Types with Inheritance and Value Substitutability", Proceedings of 25th International Conference on Very Large Data Bases (VLDB '99), Sep. 7-10, 1999.
78 Garret, Jr., "An Object-Oriented Environment for Representing Building Design and Construction Data", Advanced Construction Technology Center, Mar. 15, 1989.
79 Goscinski, "Distributed Operating Systems: The logical Design", Addison-Wesley Publishers Ltd., 1991.
80 Greenan, et al., "CompulsiveFS: Making NVRAM Suitable for Extremely Reliable Storage". http://www.usenix.org/events/fast07/wips/greenan.pdf.
81 Harrison, "Structure Editors: User-Defined Type Values and Type Inference", International Conference on Software Methods and Tools (SMT 2000), Nov. 6-9, 2000.
82 Haverlock, "Object Serialization, Java, and C++", Dr. Dobb's Journal, Aug. 1, 1998.
83 Hay, "Data Model Patterns: Convention of Thought", Dorset House Publishing, Chapter 4 (pp. 46-67), and Chapter 12 (pp. 235-259), 1996.
84 Hernandez, "The Merge/Purge Problem for Large Databases", Proceedings of the 1995 ACM SIGMOD International Conference on Management of Data, May 22-25, 1995.
85 Hsiao, "DLFM: A Transactional Resource Manager", Proceedings of the 2000 ACM SIGMOD International Conference on Management of Data, May 16-18, 2000.
86 IL Notification of Defects in Patent Application No. 191502, Feb. 17, 2013.
87 International Search Report dated Mar. 12, 2010 from PCT/US2009/056419.
88 International Search Report dated May 31, 2010 from PCT/US2009/063127.
89 iSCSI, "Performance evaluations of iSCSI implementation", printed Jan. 10, 2008.
90 JP Notice of Reasons for Rejection for Application No. 2008-545888, Apr. 19, 2012.
91 JP Notice of Reasons for Rejection for Application No. 2008-545888, Aug. 29, 2012.
92 JP Notice of Rejection for Application No. 2005-134492, Jan. 25, 2011.
93 JP Notice of Rejection for Application No. 2005-135274, Sep. 24, 2010.
94 JP Notice of Rejection for Application No. 2005-135274, Sep. 9, 2011.
95 JP Notice of Rejection for Application No. 2005-306948, Mar. 11, 2011.
96 JP Notice of Rejection for Application No. 2011-527865, Oct. 16, 2012.
97 Kaneko, "Design of 3D CG Data Model of "Move" Animation Database System", Advanced Database Research and Development Series, Proceedings of the Second Far-East Workshop on Future Database Systems, Apr. 26-28, 1992.
98 Kaneko, "Towards Dynamics Animation on Object-Oriented Animation Database System ‘Move’", Advanced Database Research and Development Series, Proceedings of the Third International Symposium on Database Systems for Advanced Applications, Apr. 6-8, 1993.
99 Kaneko, "Towards Dynamics Animation on Object-Oriented Animation Database System 'Move'", Advanced Database Research and Development Series, Proceedings of the Third International Symposium on Database Systems for Advanced Applications, Apr. 6-8, 1993.
100 Katz, "Toward a Unified Framework for Version Modeling in Engineering Databases", ACM Computing Surveys, vol. 22, No. 4, Dec. 1990.
101 Kawabe, "A Framework for 3D Modeling: Constraint-Based Description and Non-Manifold Geometric Modeling", Organization of Engineering Knowledge for Product Modelling in Computer Integrated Manufacturing, A Collection of Contributions Based on Lectures Presented at the 2nd Toyota Conference, Oct. 2-5, 1988.
102 Kempfer, "CAD Jumps on Windows 3.1 Bandwagon", Computer Aided Engineering, Nov. 1993.
103 Khan, "A Performance Evaluation of Storing XML Data in Relational Database Management Systems", Third International Workshop on Web Information and Data Management (WIDM 2001), Nov. 9, 2001.
104 Khoshafian, "Object Identity", Proceedings of the ACM Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA'86), Sep. 1986.
105 Kiesling, "ODBC in UNIX Environments", Dr. Dobb's Journal, Dec. 2002.
106 King, "TriStarp—An Investigation into the Implementation and Exploitation of Binary Relational Storage Structures", Proceedings of the 8th British National Conference on Data Bases (BNCOD-8), Jul. 9-11, 1990.
107 Krouse, "Geometric Models for CAD/CAM", Machine Design, Jul. 24, 1980.
108 Larsen, "Improve Programming Performance with Intel® Flash Memory Enhanced Factory Programming," Intel Corporation, printed May 9, 2006.
109 LeBlanc, "Design Data Storage and Extraction Using Objects", Concurrent Engineering: Research and Applications, Mar. 1993.
110 Leontiev, "On Type Systems for Object-Oriented Database Programming languages", ACM Computing Surveys, vol. 34, No. 4, Dec. 2002.
111 Levy, "Incremental Recovery in Main Memory Database Systems", IEEE Transactions on Knowledge and Data Engineering, vol. 4, No. 6, Dec. 1992.
112 Lim, "Transaction Processing in Mobile, Heterogeneous Database Systems", IEEE Transactions on Knowledge and Data Engineering, vol. 14, No. 6, Nov./Dec. 2002.
113 Mallet, "Myrtle: A set-oriented meta-interpreter driven by a "relational" trace for deductive databases debuoging", Jan. 1999.
114 Mariani, "Oggetto: An Object Oriented Database Layered on a Triple Store", The Computer Journal, vol. 35, No. 2, Apr. 1992.
115 Matthews, "Improving File System Performance With Adpative Methods", Fall 1999.
116 McMahon, "SED—A Non-interactive Text Editor", Bell laboratories Jan. 10, 1979.
117 Melton, "SQL and Management of External Data", ACM SIGMOD Record, vol. 30, No. 1, Mar. 2001.
118 Mitchell, "Managing Cache Coherence in Multiprocessor Computer Systems", printed Jul. 10, 2008.
119 Mitchell, "The logic of Architecture", Massachusetts Institute of Technology, pp. 139-143, Apr. 26, 1990.
120 Motoazabu, "IEEE1394: A Dream Interface at the Turning Point", PC User, Softbank Publishing Corporation, Oct. 24, 1999.
121 Navathe, "Evolution of Data Modeling for Databases", Communications of the ACM, vol. 35, No. 9, Sep. 1992.
122 Nelson, "Generic Support for Caching and Disconnected Operation", 4th Workshop on Workstation Operating Systems (WWOS-IV), Oct. 14-15, 1993.
123 Nieplocha, "ARMCI: A Portable Aggregate Remote Memory Copy Interface", Oct. 30, 2000.
124 Nijssen, "Conceptual Schema and Relational Database Design: A Fact Oriented Approach", Prentice Hall, pp. 9-33, 42-43, 48-51, and 156-171, Jun. 1989.
125 Novell Documentation. NetWare 6, "NSS Features and Benefits", printed Jul. 10, 2008.
126 Ohn, "Path conscious caching of B+ tree indexes in a shared disks cluster", Journal of Parallel and Distributed Computing, pp. 286-301, Dec. 2006.
127 Orenstein, "Query Processing in the ObjectStore Database System", Proceedings of the 1992 ACM SIGMOD International Conference on Management of Data, Jun. 2-5, 1992.
128 Ottogalli, "Visualisation of Distributed Applications for Performance Debugging", International Conference on Computational Science (ICCS 2001), May 28-30, 2001.
129 Pachet, "A Combinatorial Approach to Content-based Music Selection", Proceedings of the IEEE International Conference on Multimedia Computing and Systems (ICMCS 1999), vol. 1, Jun. 7-11, 1999.
130 Papiani, "A Distributed Scientific Data Archive Using the Web, XML and SQL/MED", SIGMOD Record, vol. 28, No. 3, Sep. 1999.
131 PCT International Search Report and Written Opinion for Application No. PCT/US2006/048402, Reference 314396.02 WO, May 8, 2007.
132 PCT International Search Report and Written Opinion for Application No. PCT/US2009/055198, reference 324268-02 WO, Feb. 26, 2010.
133 Ponnekanti, "Online Index Rebuild", Proceedings of the 2000 ACM SIGMOD International Conference on Management of Data, May 16-18, 2000.
134 Powell, "Object, References, Identifiers and Equality White Paper", SunSoft, OMG TC Document No. 93.7.5, Jul. 2, 1993.
135 Prosise, "2-D Drafting: Why Pay More?", PC Magazine, Feb. 23, 1993.
136 Ramsey, "An Algebraic Approach to File Synchronization", Proceedings of the Joint 8th European Software Engineering Conference (ESEC), and the 9th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-9), Sep. 10-14, 2001.
137 Read III, "Developing the Next Generation Cockpit Display System", Proceedings of the IEEE 1996 National Aerospace and Electronics Conference (NAECON), May 20-23, 1996.
138 Reiner, "Benefits of X-based Three-Tier Client/Server Model with ESRI Applications", Virtual Solutions, 1995.
139 Rosenblum, "The Design and Implementation of a Log-Structured File System", Proceedings of the 13th ACM Symposium on Operating Systems Principles, Jul. 24, 1991.
140 Rouse, "CAD Pioneers Are Still Trailblazing", Machine Design, vol. 59, No. 25, Oct. 22, 1987.
141 Roussopoulos, "Using Semantic Networks for Data Base Management", Proceedings of the First International Conference on Very Large Data Bases (VLDB'75), Sep. 22-24, 1975.
142 RU Official Action for Application No. 2003129662, Nov. 11, 2007.
143 Santos, "Computer Aided Mechanical Engineering Design Environment for Concurrent Design Process", Proceedings of the 1993 ITEC Workshop on Concurrent Engineering, Simulation in Concurrent Engineering, May 4-6, 1993.
144 Seshadri, "Enhanced abstract data types in object-relational databases", The VLDB Journal, The International Journal on Very Large Databases, vol. 7, No. 3, Aug. 1998.
145 Simoes, "A RISC-Microcontroller Based Photovoltaic System for Illumination Applications", Fifteenth Annual IEEE Applied Power Electronics Conference and Exposition (APEC 2000), Feb. 6-10, 2000.
146 Simon, "Strategic Database Technology: Management for the Year 2000", Morgan Kaufmann Publishers, Inc., pp. 3-33, 55-69, May 1995.
147 Singhal, "DDB: An Object Oriented Design Data Manager for VLSI CAD", Proceedings of the 1993 ACM SIGMOD International Conference on Management of Data, May 26-28, 1993.
148 Sreekanth, "A Specification Environment for Configuring a Discrete-Part Manufacturing System Simulation Infrastructure", International Conference on Systems, Man and Cybernetics, Systems Engineering in the Service of Humans, Oct. 17-20, 1993.
149 Sreenath, "A hybrid computation environment for multibody simulation", Mathematics and Computers in Simulation, vol. 34, Issue 2, Aug. 1992.
150 Stevens, "Value in 3-D", Industry Week, Jan. 8, 1996.
151 Stonebraker, "The Case for Partial Indexes", SIGMOD Record, vol. 18, No. 4, Dec. 1989.
152 Strickland, "Intersection of Relational and Object", Proceedings of the AM/FM International Conference XVII, Mar. 14-17, 1994.
153 Sutherland, "The Hybrid Object-Relational Architecture (HORA): An Integration of Object-Oriented and Relational Technology", Proceedings of the 1993 ACM/SIGAPP Symposium on Applied Computing, States of the Art and Practice, Feb. 14-16, 1993.
154 Suzuki, "Geometric Modeling for Modeling Products", Proceedings of the Third International Conference on Engineering Graphics and Descriptive Geometry, vol. 2, Jul. 11-16, 1983.
155 Taylor, "An Integrated Robot System Architecture", Proceedings of the IEEE, vol. 71, No. 7, Jul. 1983.
156 TW Search Report for Application No. 094114140, Nov. 22, 2011.
157 Varlamis, "Bridging XML-Schema and relational databases. A system for generating and manipulating relational databases using valid XML documents", Proceedings of the 2001 ACM Symposium on Document Engineering, Nov. 9-10, 2001.
158 Vitter, "External Memory Algorithms," Proceedings of the 6th Annual European Symposium on Algorithms, Aug. 24, 1998.
159 Watanabe, "Knowledge Integration for Architectural Design", Knowledge-Based Computer-Aided Architectural Design, Jul. 1994.
160 Waugh, "Specifying metadata standards for metadata tool configuration", Computer Networks and ISDN Systems, Proceedings of the Seventh International World Wide Web Conference, Apr. 14-18, 1998.
161 Wilcox, "Object Databases: Object methods in distributed computing" Dr. Dobbs Journal, Nov. 1994.
162 Wold, "Content-Based Classification, Search, and Retrieval of Audio", IEEE MultiMedia, vol. 3, Issue 3, Sep. 1996.
163 Yoshikawa, "XRel: A Path-Based Approach to Storage and Retrieval of XML Documents Using Relational Databases", ACM Transactions on Internet Technology, vol. 1, No. 1, Aug. 2001.
164 Zhu, et al., "Power Aware Storage Cache Management", Department of Illinois, University of Illinois at Urbana-Champaign, Urbana, IL. http://opera.cs.uiuc.edu/paper/TC05.pdf.
US8756538 * 19 Feb 2013 17 Jun 2014 International Business Machines Corporation Parsing data representative of a hardware design into commands of a hardware design environment
US9684596 25 Feb 2015 20 Jun 2017 Microsoft Technology Licensing, Llc Application cache replication to secondary application(s)
US9684607 25 Feb 2015 20 Jun 2017 Microsoft Technology Licensing, Llc Automatic recovery of application cache warmth
US20120054421 * 3 Aug 2011 1 Mar 2012 Hitachi, Ltd. Information device equipped with cache memories, apparatus and program using the same device
US20130219150 * 19 Feb 2013 22 Aug 2013 International Business Machines Corporation Parsing Data Representative of a Hardware Design into Commands of a Hardware Design Environment
U.S. Classification 711/118, 711/206, 711/3
International Classification G06F9/26, G06F13/00, G06F12/00, G06F13/28, G06F9/34
Cooperative Classification G06F2212/222, G06F12/0862, G06F12/14, G06F2212/1032, G06F2212/1016, G06F12/0804, G06F12/0866, G06F12/0871, G06F2212/2022, G06F2212/466, G06F2212/1052