US20060230226A1 - Hard disk drive with optional cache memory - Google Patents
Hard disk drive with optional cache memory Download PDFInfo
- Publication number
- US20060230226A1 US20060230226A1 US11/198,177 US19817705A US2006230226A1 US 20060230226 A1 US20060230226 A1 US 20060230226A1 US 19817705 A US19817705 A US 19817705A US 2006230226 A1 US2006230226 A1 US 2006230226A1
- Authority
- US
- United States
- Prior art keywords
- cache memory
- hard disk
- disk drive
- data
- computer system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
- G06F12/0873—Mapping of cache memory to specific storage devices or parts thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/60—Details of cache memory
- G06F2212/601—Reconfiguration of cache memory
Definitions
- the present invention relates to data storage devices and, more particularly, to a hard disk drive with an optional cache memory.
- Hard disk drives typically are used as mass storage devices in systems such as personal computers, media players, set-top boxes and many other systems.
- hard disk drives over other non-volatile data storage devices such as flash memories is their cost efficiency per bit of stored data.
- the portable devices that usually include hard disk drives are laptop computers, portable media players and GPS receivers. Such devices typically are powered by rechargeable batteries.
- a major constraint on such devices is the time that they can operate on a single battery charge. It therefore is important to design components of these systems, notably the hard disk drives of these systems, that are major consumers of power, to be economical in their use of power.
- FIG. 1 is a high-level schematic block diagram of a prior art hard disk drive (HDD) 10 that uses a flash memory 12 as a cache memory.
- the data recording medium of HDD 10 is a magnetic recording medium 14 on a disk-like platter 16 .
- a controller 18 writes to magnetic medium 14 and reads from magnetic medium 14 using an electromechanical mechanism that includes a motor 20 for spinning platter 16 , a read-write head 24 for reading and writing data bits at arbitrarily selected locations on platter 16 and an arm 22 for moving read-write head 24 to those locations.
- Cache memory 12 is used to limit the number of accesses to HDD 10 by its host device in which motor 20 is powered up. Limiting these accesses reduces the power consumption of HDD 10 and also increases the reliability of the overall system, for two reasons. First, read-write head 24 is parked for a larger portion of the time and so is the likelihood of platter 16 being damaged as a consequence of rough handling is decreased. Second, flash memory 12 , having no moving parts, typically is more reliable than magnetic medium 14 as a data storage medium, reducing the chance of data loss in case of system failure.
- the degrees of freedom available to the designer of a system that includes HDD 10 include:
- Cache management responsibility whether caching is managed by the host's operating system or by controller 18 .
- Caching medium volatile (e.g., DRAM) vs. non-volatile (e.g. flash)
- a typical method of HDD cache management is as follows: When HDD 10 receives data to store as a consequence of a write operation by the host of HDD 10 , controller 18 writes the data to cache memory 12 . When cache memory 12 is full, controller 18 transfers the data to magnetic medium 14 of platter 16 .
- This method of operating HDD 10 saves substantially in power consumption. How much power is saved, vs. always writing to platter 16 , is a function of the number of write accesses and the size of cache memory 12 .
- Calculations for typical laptop computers (HDD capacity around 60 GB, flash memory capacity around 64-128 MB) show that the amount of data written per hour to cache memory 12 is a tiny fraction of the capacity of a typical platter 16 . Using a relatively small cache memory 12 can give a 20%-30% reduction in power consumption in a typical consumer device.
- a computer system including: (a) a hard disk drive; and (b) an interface for optionally operationally connecting, to the computer system, a cache memory for the hard disk drive.
- a hard disk drive including: (a) a nonvolatile medium for storing data; (b) a controller for writing the data to the nonvolatile medium and for reading the data from the nonvolatile medium; and (c) an interface for optionally operationally connecting, to the controller, a cache memory for the nonvolatile medium.
- a method of operating a hard disk drive that includes a nonvolatile data storage medium, including the steps of: (a) providing an interface for optionally operationally associating a cache memory with the hard disk drive; and (b) in exchanging data with the hard disk drive, determining whether the cache memory is operationally associated with the hard disk drive.
- a method of producing computer systems including the steps of: (a) providing each computer system with a respective hard disk drive; (b) providing each computer system with a respective interface for optionally operationally connecting, to the each computer system, a cache memory for the respective hard disk drive of the each computer system; and (c) in configuring each computer system for delivery to a respective customer, deciding whether to operationally connect the cache memory to the each computer system at the respective interface of the each computer system.
- a computer-readable storage medium having computer-readable code embodied on the computer-readable storage medium, the computer-readable code for exchanging data with a hard disk drive in a computer system that includes an interface for optionally operationally connecting, to the computer system, a cache memory for the hard disk drive, the hard disk drive including a nonvolatile data storage medium, the computer-readable code including: (a) program code for determining whether the cache memory is operationally connected to the computer system; and (b) program code for, if the cache memory is operationally connected to the computer system, then, in writing the data to the hard disk drive: (i) if the cache memory is full: (A) copying contents of the cache memory to the nonvolatile data storage medium, and (B) writing the data to the nonvolatile data storage medium, and (ii) otherwise, writing the data to the cache memory.
- a computer system of the present invention includes a hard disk drive and an interface for optionally operationally connecting, to the computer system, a cache memory for the hard drive. That the connection of the cache memory to the computer system is “optional” means that the computer system is fully operational even without the cache memory.
- the cache memory if present, merely enhances the operation of the computer system, for example by conserving power.
- the interface is for reversibly operationally connecting the cache memory to the computer system.
- the computer system includes a mechanism, such as a system bus, that is separate from the hard disk drive and that is for operationally connecting the hard disk drive to the interface.
- a computer system also includes an operating system for using the cache memory to cache data that are to be written to the hard disk drive.
- an operating system for using the cache memory to cache data that are to be written to the hard disk drive.
- caching is the only purpose for which the operating system uses the cache memory. Note that using the cache memory “only” for caching data to be written to the hard disk drive does not preclude reading, from the cache memory, data that are waiting to be transferred to the hard disk drive.
- the hard disk drive includes a controller, and the interface is directly operationally connected to the controller.
- a hard disk drive of the present invention includes a nonvolatile (e.g., magnetic or optical) medium for storing data, a controller for writing the data to the nonvolatile medium and for reading the data from the nonvolatile medium, and an interface for optionally operationally connecting, to the controller, a cache memory for the nonvolatile medium. That the connection of the cache memory to the controller is “optional” means that the hard disk drive is fully operational even without the cache memory.
- the cache memory if present, merely enhances the operation of the hard disk drive, for example by conserving power.
- the hard disk drive includes an electromechanical mechanism that the controller uses to write the data to the magnetic medium and to read the data from the magnetic medium.
- the electromechanical mechanism provides the controller with random access to the magnetic medium.
- the cache memory be non-volatile, for example a flash memory.
- the scope of the present invention also includes a method of operating a hard disk drive that includes a nonvolatile data storage medium.
- An interface is provided for optionally operationally associating a cache memory with the hard disk drive. That the association is “optional” means that the hard disk drive is fully operational even in the absence of the cache memory.
- the cache memory if present, merely enhances the operation of the hard disk drive, for example by conserving power.
- it In exchanging data with the hard disk drive, i.e., in writing data to the hard disk drive or in reading data from the hard disk drive, it first is determined whether the cache memory is in fact operationally associated with the hard disk drive. If the cache memory is in fact operationally associated with the hard disk drive,
- the cache memory In writing new data (i.e., data not yet cached) to the hard disk drive, if the cache memory is full, meaning that there is no room in the cache memory to write the new data, the contents of the cache memory are copied to the nonvolatile data storage medium and the new data are written to the nonvolatile data storage medium. If the cache memory is not full, then the data are written to the cache memory.
- the data In reading data from the hard disk drive, it first is determined whether the data reside in the cache memory. If the data reside in the cache memory, then the data are read from the cache memory. If the data do not reside in the cache memory, then the data are read from the nonvolatile data storage medium.
- the scope of the present invention also includes a method of producing computer systems.
- Each computer system is provided with a respective hard disk drive and with a respective interface for optionally operationally connecting, to the computer system, a cache memory for the computer system's hard disk drive. That the connection of the cache memory to the computer system is “optional” means that the computer system is fully operational even without the cache memory.
- the cache memory if present, merely enhances the operation of the computer system, for example by conserving power.
- it is decided whether to actually operationally connect a cache memory for the computer system's hard disk drive to the computer system's interface. Whether the computer system is delivered to the customer with or without a cache memory for the hard disk drive operationally connected to the computer system depends on the customer's requirements.
- each computer system is provided with its own mechanism, separate from its hard disk drive, for operationally connecting the hard disk drive to the interface.
- each hard disk drive includes a controller, and each computer system's interface is directly operationally connected to the controller of that computer system's hard disk drive.
- the cache memories could be volatile memories or, preferably and alternatively, non-volatile memories such as flash memories.
- the scope of the present invention also includes a computer-readable storage medium having embodied thereon computer-readable code for implementing the method of the present invention for operating a hard disk drive.
- the present invention provides many advantages over the prior art. Among these advantages are the following:
- a consumer or an original equipment manufacturer can select how much cache to attach to his/her/its hard disk drive. It is up to the consumer or to the original equipment manufacturer, rather than the manufacturer of the hard disk drive, to bear the cost of cache memory. Omitting the cache memory for a user who does not need one bears only a small penalty in cost, the cost of the interface.
- a customer By purchasing a hard disk drive or a computer system of the present invention without a cache memory, a customer saves money up front.
- the customer is free at any time to invest in an upgrade to a hard disk drive or a computer system with caching.
- the customer is free to exercise this option when prices of cache memories are low.
- a vendor of a hard disk or computer system of the present invention adds value to its product at minimal cost and minimal operational overhead.
- a vendor can target products of the same product line separately to customers who need caching and to customers who do not need caching.
- FIG. 1 is a high-level schematic block diagram of a prior art hard disk drive
- FIG. 2 is a high-level schematic block diagram of a hard disk drive of the present invention
- FIG. 3 is a partial high-level schematic block diagram of a computer system of the present invention.
- FIG. 4 is a flow chart of writing to a hard disk drive according to the present invention.
- FIG. 5 is a flow chart of reading from a hard disk drive according to the present invention.
- the present invention is of a hard disk drive and a related computer system that can be configured easily, per application, to optimize cost vs. power consumption.
- nonvolatile data storage media for example optical storage media
- description herein of the preferred embodiments of the present invention is in terms of a hard disk drive whose nonvolatile data storage medium is a magnetic medium such as magnetic medium 14 . It will be clear to those skilled in the art how to apply the principles of the present invention to other nonvolatile data storage media.
- FIG. 2 illustrates a hard disk drive 30 of the present invention.
- Hard disk drive 30 shares most of its components with hard disk drive 10 .
- the principal difference between hard disk drive 10 and hard disk drive 30 is that instead of a hard-wired cache memory 12 , hard disk drive 30 includes an interface 32 for an optional cache memory 34 .
- Interface 32 is a standard interface for reversibly connecting a memory such as a flash memory to controller 18 .
- interface 32 is a standard USB interface; in other versions of HDD 30 , interface 32 is a slot such as commonly is used in appliances such as digital cameras and MP3 players for inserting a flash memory card.
- cache memory 34 need not be a non-volatile memory, in the overwhelming majority of cases cache memory 34 is a non-volatile memory such as a flash memory.
- cache memory 34 is sealed permanently to interface 32 .
- an original equipment manufacturer may seal cache memory 34 permanently to interface 32 of a HDD 30 that the original equipment manufacturer purchases from a manufacturer of hard disk drives.
- Interface 32 is adapted to allow controller 18 to sense the presence and size of cache memory 34 .
- interface 32 is a USB interface
- controller 18 conducts an enumeration process according to the USB standard to determine whether cache memory 34 is present in interface 32 and, if cache memory 34 is present in interface 32 , what the size of cache memory 34 is.
- controller 18 In the absence of cache memory 34 , controller 18 always writes incoming data directly to magnetic medium 14 of platter 16 . If cache memory 34 is present, controller 18 caches incoming data in cache memory 34 , as described above, until cache memory 34 is full, at which time controller 34 transfers the contents of cache memory 34 to magnetic medium 14 of platter 16 and erases cache memory 34 .
- FIG. 3 illustrates a software implementation of the present invention.
- FIG. 3 is a partial high-level schematic block diagram of a computer system 40 of the present invention.
- System 40 includes a processor 42 ; a RAM 44 ; input and output devices such as a keyboard and a display screen, represented collectively by an I/O block 46 ; a hard disk drive 56 that is similar to prior art hard disk drive 10 except for lacking a cache memory; and an interface 48 for optionally reversibly connecting to system 40 a cache memory 50 that is used for caching writes to HDD 10 .
- Components 42 , 44 , 46 , 48 and 56 communicate with each other via a common system bus 52 .
- HDD 56 Among the data stored on HDD 56 is the code of an operating system 54 .
- processor 42 downloads the code of operating system 54 to RAM 44 and then executes the code of operating system 54 from RAM 44 to manage the operation of system 40 .
- HDD 56 thus is an example of a computer-readable storage medium in which is embedded computer-readable code for implementing the method of the present invention. Note that actions described herein as being performed “by operating system 54 ” actually are operations that are performed by processor 42 by executing code of operating system 54 .
- interface 48 is a standard interface for reversibly connecting a memory such as a flash memory to system 40 .
- interface 48 is a standard USB interface; in other versions of system 40 , interface 48 is a slot such as commonly is used in appliances such as digital cameras and MP3 players for inserting a flash memory card.
- cache memory 50 like cache memory 34 , need not be a non-volatile memory, in the overwhelming majority of cases cache memory 50 is a non-volatile memory such as a flash memory.
- the operational connection between interface 48 and cache memory 50 usually is kept reversible.
- interface 48 is adapted to allow processor 42 , under the control of operating system 54 , to sense the presence and size of cache memory 50 .
- the code of operating system 54 includes code for sensing the presence and size of cache memory 50 when system 40 is powered up. A flag that indicates the presence or absence of cache memory 50 then is set in a register in processor 42 or else in RAM 44 . If cache memory 50 is present, then the size of cache memory 50 is recorded in another register in processor 42 or alternatively in RAM 44 . Subsequently, operating system 54 tests the presence and size of cache memory 50 by inspecting the flag and the recorded size, rather than by interrogating interface 48 .
- the code of operating system 54 also includes code for using cache memory 50 as a cache for HDD 56 if cache memory 50 is present.
- operating system 54 In the absence of cache memory 50 , when operating system 54 receives an instruction from an application program to write data to HDD 56 , operating system 54 writes those data directly to HDD 56 . If cache memory 50 is present, then when operating system 54 receives an instruction from an application program to write data to HDD 56 , operating system 54 instead first attempts to write the data to cache memory 50 . If cache memory 50 is full, then operating system 54 writes the data to HDD 56 , copies the contents of cache memory 50 to HDD 56 , and erases cache memory 50 .
- cache memory 50 is available to operating system 54 for any purpose for which operating system 54 needs a memory, it is preferable to restrict the use of cache memory 50 by operating system 54 to the caching of data to be written to hard disk 56 .
- FIG. 4 is a flow chart of writing to HDD 30 or 56 .
- controller 18 of HDD 30 receives an instruction from the host of HDD 30 to write data to platter 16
- operating system 54 receives an instruction from an application program to write data to HDD 56 .
- controller 18 or operating system 54 determines whether cache memory 34 or 50 is present. If cache memory 34 or 50 is absent, then in block 64 , controller 18 writes the data directly to magnetic medium 14 of platter 16 , or operating system 54 writes the data directly to HDD 56 . If cache memory 34 or 50 is present, then in block 66 , controller 18 or operating system 54 determines whether cache memory 34 or 50 is full.
- controller 18 or operating system 54 writes the data to cache memory 34 or 50 . If cache memory 34 or 50 is full, then in block 70 controller 18 writes the data directly to magnetic medium 14 of platter 16 , or operating system 54 writes the data directly to HDD 56 . Then, in block 72 , controller 18 copies the contents of cache memory 34 to magnetic medium 14 of platter 16 , or operating system 54 copies the contents of cache memory 50 to HDD 56 . Finally, in block 74 , controller 18 or operating system 54 erases cache memory 34 or 50 .
- FIG. 5 is a flow chart of reading from HDD 30 or 56 .
- controller 18 of HDD 30 receives an instruction from the host of HDD 30 to read data from platter 16
- operating system 54 receives an instruction from an application program to read data from HDD 56 .
- controller 18 or operating system 54 determines whether cache memory 34 or 50 is present. If cache memory 34 or 50 is absent, then in block 84 , controller 18 reads the data directly from magnetic medium 14 of platter 16 , or operating system 54 reads the data directly from HDD 56 .
- controller 18 or operating system 54 determines whether the requested data are present in cache memory 34 or 50 . If the requested data are present in cache memory 34 or 50 , then in block 88 controller 18 or operating system 54 reads the data from cache memory 34 or 50 . Otherwise, in block 84 , controller 18 reads the data directly from magnetic medium 14 of platter 16 , or operating system 54 reads the data directly from HDD 56 .
- the present invention supports an innovative method of producing computer systems.
- the computer systems are manufactured with hard disk drives and with interfaces for cache memories as described above.
- the interfaces could be integral to the hard disk drives, if the hard disk drives are configured like HDD 30 ; or alternatively the interfaces could be coupled to the hard disk drives via a system bus as in computer system 40 .
- the producer decides whether to fill each order with a computer system that includes a cache memory 34 or 50 operationally connected to that computer system's interface 32 or 48 or, alternatively, to deliver the computer system without cache memory 34 or 50 , depending on the customer's requirements.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Memory System Of A Hierarchy Structure (AREA)
Abstract
Description
- The present invention relates to data storage devices and, more particularly, to a hard disk drive with an optional cache memory.
- Almost every modern electronic system needs a storage device. One of the most popular storage devices is the hard disk drive. Hard disk drives typically are used as mass storage devices in systems such as personal computers, media players, set-top boxes and many other systems.
- The main advantage of hard disk drives over other non-volatile data storage devices such as flash memories is their cost efficiency per bit of stored data. One of the limitations of hard disk drives, particularly with regard to their use in portable devices, is their relatively high power consumption. Among the portable devices that usually include hard disk drives are laptop computers, portable media players and GPS receivers. Such devices typically are powered by rechargeable batteries. A major constraint on such devices is the time that they can operate on a single battery charge. It therefore is important to design components of these systems, notably the hard disk drives of these systems, that are major consumers of power, to be economical in their use of power.
- One of the known methods for minimizing the power consumption of a hard disk drive is the inclusion in the hard disk drive of an auxiliary memory such as a flash memory that is used as a data cache.
FIG. 1 is a high-level schematic block diagram of a prior art hard disk drive (HDD) 10 that uses a flash memory 12 as a cache memory. The data recording medium of HDD 10 is amagnetic recording medium 14 on a disk-like platter 16. Acontroller 18 writes tomagnetic medium 14 and reads frommagnetic medium 14 using an electromechanical mechanism that includes a motor 20 forspinning platter 16, a read-writehead 24 for reading and writing data bits at arbitrarily selected locations onplatter 16 and anarm 22 for moving read-writehead 24 to those locations. Cache memory 12 is used to limit the number of accesses to HDD 10 by its host device in which motor 20 is powered up. Limiting these accesses reduces the power consumption of HDD 10 and also increases the reliability of the overall system, for two reasons. First, read-writehead 24 is parked for a larger portion of the time and so is the likelihood ofplatter 16 being damaged as a consequence of rough handling is decreased. Second, flash memory 12, having no moving parts, typically is more reliable thanmagnetic medium 14 as a data storage medium, reducing the chance of data loss in case of system failure. - The degrees of freedom available to the designer of a system that includes HDD 10 include:
- 1. Physical location: whether cache memory 12 is physically part of HDD 10 or is elsewhere in the host system, for example on the motherboard of the host system.
- 2. Cache management responsibility: whether caching is managed by the host's operating system or by
controller 18. - 3. Caching medium: volatile (e.g., DRAM) vs. non-volatile (e.g. flash)
- A typical method of HDD cache management is as follows: When HDD 10 receives data to store as a consequence of a write operation by the host of HDD 10,
controller 18 writes the data to cache memory 12. When cache memory 12 is full,controller 18 transfers the data tomagnetic medium 14 ofplatter 16. This method of operating HDD 10 saves substantially in power consumption. How much power is saved, vs. always writing toplatter 16, is a function of the number of write accesses and the size of cache memory 12. Calculations for typical laptop computers (HDD capacity around 60 GB, flash memory capacity around 64-128 MB) show that the amount of data written per hour to cache memory 12 is a tiny fraction of the capacity of atypical platter 16. Using a relatively small cache memory 12 can give a 20%-30% reduction in power consumption in a typical consumer device. - The trade-off in such caching is between the additional cost of cache memory 12 vs. the power saved. This is an important limitation, as hard disk drives have become a standard commodity that is used in a wide variety of applications. However, in some applications, low cost is a more important constraint than low power consumption; in other applications, low power consumption is a more important constraint than low cost; and in yet other applications, both constraints are important. The exact fine tuning between cost and power thus varies from one application to another, and can even vary from one user to another.
- There is thus a widely recognized need for, and it would be highly advantageous to have, a commodity hard disk drive that can be adapted easily to the cost and power constraints of a wide variety of applications.
- According to the present invention there is provided a computer system including: (a) a hard disk drive; and (b) an interface for optionally operationally connecting, to the computer system, a cache memory for the hard disk drive.
- According to the present invention there is provided a hard disk drive including: (a) a nonvolatile medium for storing data; (b) a controller for writing the data to the nonvolatile medium and for reading the data from the nonvolatile medium; and (c) an interface for optionally operationally connecting, to the controller, a cache memory for the nonvolatile medium.
- According to the present invention there is provided a method of operating a hard disk drive that includes a nonvolatile data storage medium, including the steps of: (a) providing an interface for optionally operationally associating a cache memory with the hard disk drive; and (b) in exchanging data with the hard disk drive, determining whether the cache memory is operationally associated with the hard disk drive.
- According to the present invention there is provided a method of producing computer systems, including the steps of: (a) providing each computer system with a respective hard disk drive; (b) providing each computer system with a respective interface for optionally operationally connecting, to the each computer system, a cache memory for the respective hard disk drive of the each computer system; and (c) in configuring each computer system for delivery to a respective customer, deciding whether to operationally connect the cache memory to the each computer system at the respective interface of the each computer system.
- According to the present invention there is provided a computer-readable storage medium having computer-readable code embodied on the computer-readable storage medium, the computer-readable code for exchanging data with a hard disk drive in a computer system that includes an interface for optionally operationally connecting, to the computer system, a cache memory for the hard disk drive, the hard disk drive including a nonvolatile data storage medium, the computer-readable code including: (a) program code for determining whether the cache memory is operationally connected to the computer system; and (b) program code for, if the cache memory is operationally connected to the computer system, then, in writing the data to the hard disk drive: (i) if the cache memory is full: (A) copying contents of the cache memory to the nonvolatile data storage medium, and (B) writing the data to the nonvolatile data storage medium, and (ii) otherwise, writing the data to the cache memory.
- A computer system of the present invention includes a hard disk drive and an interface for optionally operationally connecting, to the computer system, a cache memory for the hard drive. That the connection of the cache memory to the computer system is “optional” means that the computer system is fully operational even without the cache memory. The cache memory, if present, merely enhances the operation of the computer system, for example by conserving power.
- Preferably, the interface is for reversibly operationally connecting the cache memory to the computer system.
- In one variant of the computer system of the present invention, the computer system includes a mechanism, such as a system bus, that is separate from the hard disk drive and that is for operationally connecting the hard disk drive to the interface. Preferably, such a computer system also includes an operating system for using the cache memory to cache data that are to be written to the hard disk drive. Most preferably, such caching is the only purpose for which the operating system uses the cache memory. Note that using the cache memory “only” for caching data to be written to the hard disk drive does not preclude reading, from the cache memory, data that are waiting to be transferred to the hard disk drive.
- In another variant of the computer system, the hard disk drive includes a controller, and the interface is directly operationally connected to the controller.
- A hard disk drive of the present invention includes a nonvolatile (e.g., magnetic or optical) medium for storing data, a controller for writing the data to the nonvolatile medium and for reading the data from the nonvolatile medium, and an interface for optionally operationally connecting, to the controller, a cache memory for the nonvolatile medium. That the connection of the cache memory to the controller is “optional” means that the hard disk drive is fully operational even without the cache memory. The cache memory, if present, merely enhances the operation of the hard disk drive, for example by conserving power.
- Preferably, if the nonvolatile medium is a magnetic medium, then the hard disk drive includes an electromechanical mechanism that the controller uses to write the data to the magnetic medium and to read the data from the magnetic medium. Most preferably, the electromechanical mechanism provides the controller with random access to the magnetic medium.
- Although the scope of the present invention, in the case of both the computer system and the hard disk drive, includes volatile cache memories, it is preferred that the cache memory be non-volatile, for example a flash memory.
- The scope of the present invention also includes a method of operating a hard disk drive that includes a nonvolatile data storage medium. An interface is provided for optionally operationally associating a cache memory with the hard disk drive. That the association is “optional” means that the hard disk drive is fully operational even in the absence of the cache memory. The cache memory, if present, merely enhances the operation of the hard disk drive, for example by conserving power. In exchanging data with the hard disk drive, i.e., in writing data to the hard disk drive or in reading data from the hard disk drive, it first is determined whether the cache memory is in fact operationally associated with the hard disk drive. If the cache memory is in fact operationally associated with the hard disk drive,
- then:
- In writing new data (i.e., data not yet cached) to the hard disk drive, if the cache memory is full, meaning that there is no room in the cache memory to write the new data, the contents of the cache memory are copied to the nonvolatile data storage medium and the new data are written to the nonvolatile data storage medium. If the cache memory is not full, then the data are written to the cache memory.
- or:
- In reading data from the hard disk drive, it first is determined whether the data reside in the cache memory. If the data reside in the cache memory, then the data are read from the cache memory. If the data do not reside in the cache memory, then the data are read from the nonvolatile data storage medium.
- The scope of the present invention also includes a method of producing computer systems. Each computer system is provided with a respective hard disk drive and with a respective interface for optionally operationally connecting, to the computer system, a cache memory for the computer system's hard disk drive. That the connection of the cache memory to the computer system is “optional” means that the computer system is fully operational even without the cache memory. The cache memory, if present, merely enhances the operation of the computer system, for example by conserving power. Finally, in configuring each computer system for delivery to a customer thereof, it is decided whether to actually operationally connect a cache memory for the computer system's hard disk drive to the computer system's interface. Whether the computer system is delivered to the customer with or without a cache memory for the hard disk drive operationally connected to the computer system depends on the customer's requirements.
- Preferably, each computer system is provided with its own mechanism, separate from its hard disk drive, for operationally connecting the hard disk drive to the interface. Alternatively, each hard disk drive includes a controller, and each computer system's interface is directly operationally connected to the controller of that computer system's hard disk drive.
- The cache memories could be volatile memories or, preferably and alternatively, non-volatile memories such as flash memories.
- The scope of the present invention also includes a computer-readable storage medium having embodied thereon computer-readable code for implementing the method of the present invention for operating a hard disk drive.
- The present invention provides many advantages over the prior art. Among these advantages are the following:
- A consumer or an original equipment manufacturer can select how much cache to attach to his/her/its hard disk drive. It is up to the consumer or to the original equipment manufacturer, rather than the manufacturer of the hard disk drive, to bear the cost of cache memory. Omitting the cache memory for a user who does not need one bears only a small penalty in cost, the cost of the interface.
- Having to keep on hand only one kind of hard disk drive or only one kind of computer system simplifies the inventory tasks of a vendor of hard disk drives and computer systems of the present invention.
- By purchasing a hard disk drive or a computer system of the present invention without a cache memory, a customer saves money up front. The customer is free at any time to invest in an upgrade to a hard disk drive or a computer system with caching. The customer is free to exercise this option when prices of cache memories are low.
- A vendor of a hard disk or computer system of the present invention adds value to its product at minimal cost and minimal operational overhead. A vendor can target products of the same product line separately to customers who need caching and to customers who do not need caching.
- The invention is herein described, by way of example only, with reference to the accompanying drawings, wherein:
-
FIG. 1 is a high-level schematic block diagram of a prior art hard disk drive; -
FIG. 2 is a high-level schematic block diagram of a hard disk drive of the present invention; -
FIG. 3 is a partial high-level schematic block diagram of a computer system of the present invention; -
FIG. 4 is a flow chart of writing to a hard disk drive according to the present invention; -
FIG. 5 is a flow chart of reading from a hard disk drive according to the present invention. - The present invention is of a hard disk drive and a related computer system that can be configured easily, per application, to optimize cost vs. power consumption.
- The principles and operation of a hard disk drive according to the present invention may be better understood with reference to the drawings and the accompanying description.
- Although the scope of the present invention extends to hard disk drives that use any kind of nonvolatile data storage media, for example optical storage media, the description herein of the preferred embodiments of the present invention is in terms of a hard disk drive whose nonvolatile data storage medium is a magnetic medium such as
magnetic medium 14. It will be clear to those skilled in the art how to apply the principles of the present invention to other nonvolatile data storage media. - Referring again to the drawings,
FIG. 2 illustrates a hard disk drive 30 of the present invention. Hard disk drive 30 shares most of its components with hard disk drive 10. The principal difference between hard disk drive 10 and hard disk drive 30 is that instead of a hard-wired cache memory 12, hard disk drive 30 includes aninterface 32 for anoptional cache memory 34.Interface 32 is a standard interface for reversibly connecting a memory such as a flash memory tocontroller 18. For example, in some versions of HDD 30,interface 32 is a standard USB interface; in other versions of HDD 30,interface 32 is a slot such as commonly is used in appliances such as digital cameras and MP3 players for inserting a flash memory card. Although inprinciple cache memory 34 need not be a non-volatile memory, in the overwhelming majority ofcases cache memory 34 is a non-volatile memory such as a flash memory. Usually, the reversibility of the operational connection betweeninterface 32 andcache memory 34 is preserved, to allow a user of a system that includes HDD 30 to swap cache memories 34 (e.g. to upgrade to a larger cache memory 34) on a per-application basis. Optionally,cache memory 34 is sealed permanently tointerface 32. For example, an original equipment manufacturer may sealcache memory 34 permanently to interface 32 of a HDD 30 that the original equipment manufacturer purchases from a manufacturer of hard disk drives. -
Interface 32 is adapted to allowcontroller 18 to sense the presence and size ofcache memory 34. For example, ifinterface 32 is a USB interface, then whencache memory 34 is connected to interface 32, or when HDD 30 is powered up,controller 18 conducts an enumeration process according to the USB standard to determine whethercache memory 34 is present ininterface 32 and, ifcache memory 34 is present ininterface 32, what the size ofcache memory 34 is. In the absence ofcache memory 34,controller 18 always writes incoming data directly tomagnetic medium 14 ofplatter 16. Ifcache memory 34 is present,controller 18 caches incoming data incache memory 34, as described above, untilcache memory 34 is full, at whichtime controller 34 transfers the contents ofcache memory 34 tomagnetic medium 14 ofplatter 16 and erasescache memory 34. - HDD 30 of
FIG. 2 is a hardware/firmware implementation of the present invention.FIG. 3 illustrates a software implementation of the present invention. Specifically,FIG. 3 is a partial high-level schematic block diagram of a computer system 40 of the present invention. System 40 includes aprocessor 42; aRAM 44; input and output devices such as a keyboard and a display screen, represented collectively by an I/O block 46; ahard disk drive 56 that is similar to prior art hard disk drive 10 except for lacking a cache memory; and an interface 48 for optionally reversibly connecting to system 40 acache memory 50 that is used for caching writes to HDD 10.Components common system bus 52. Among the data stored onHDD 56 is the code of anoperating system 54. When system 40 is powered up,processor 42 downloads the code ofoperating system 54 to RAM 44 and then executes the code ofoperating system 54 fromRAM 44 to manage the operation of system 40.HDD 56 thus is an example of a computer-readable storage medium in which is embedded computer-readable code for implementing the method of the present invention. Note that actions described herein as being performed “by operatingsystem 54” actually are operations that are performed byprocessor 42 by executing code ofoperating system 54. - Like
interface 32, interface 48 is a standard interface for reversibly connecting a memory such as a flash memory to system 40. For example, in some versions of system 40, interface 48 is a standard USB interface; in other versions of system 40, interface 48 is a slot such as commonly is used in appliances such as digital cameras and MP3 players for inserting a flash memory card. Althoughcache memory 50, likecache memory 34, need not be a non-volatile memory, in the overwhelming majority ofcases cache memory 50 is a non-volatile memory such as a flash memory. As in the case of the connection betweeninterface 32 andcache memory 34, the operational connection between interface 48 andcache memory 50 usually is kept reversible. - Also like
interface 32, interface 48 is adapted to allowprocessor 42, under the control ofoperating system 54, to sense the presence and size ofcache memory 50. The code ofoperating system 54 includes code for sensing the presence and size ofcache memory 50 when system 40 is powered up. A flag that indicates the presence or absence ofcache memory 50 then is set in a register inprocessor 42 or else inRAM 44. Ifcache memory 50 is present, then the size ofcache memory 50 is recorded in another register inprocessor 42 or alternatively inRAM 44. Subsequently,operating system 54 tests the presence and size ofcache memory 50 by inspecting the flag and the recorded size, rather than by interrogating interface 48. The code ofoperating system 54 also includes code for usingcache memory 50 as a cache forHDD 56 ifcache memory 50 is present. In the absence ofcache memory 50, when operatingsystem 54 receives an instruction from an application program to write data toHDD 56,operating system 54 writes those data directly toHDD 56. Ifcache memory 50 is present, then when operatingsystem 54 receives an instruction from an application program to write data toHDD 56,operating system 54 instead first attempts to write the data tocache memory 50. Ifcache memory 50 is full, then operatingsystem 54 writes the data toHDD 56, copies the contents ofcache memory 50 toHDD 56, and erasescache memory 50. - Although in
principle cache memory 50 is available to operatingsystem 54 for any purpose for whichoperating system 54 needs a memory, it is preferable to restrict the use ofcache memory 50 by operatingsystem 54 to the caching of data to be written tohard disk 56. -
FIG. 4 is a flow chart of writing toHDD 30 or 56. Inblock 60,controller 18 of HDD 30 receives an instruction from the host of HDD 30 to write data toplatter 16, oroperating system 54 receives an instruction from an application program to write data toHDD 56. Inblock 62,controller 18 oroperating system 54 determines whethercache memory cache memory block 64,controller 18 writes the data directly tomagnetic medium 14 ofplatter 16, oroperating system 54 writes the data directly toHDD 56. Ifcache memory block 66,controller 18 oroperating system 54 determines whethercache memory cache memory block 68controller 18 oroperating system 54 writes the data tocache memory cache memory block 70controller 18 writes the data directly tomagnetic medium 14 ofplatter 16, oroperating system 54 writes the data directly toHDD 56. Then, inblock 72,controller 18 copies the contents ofcache memory 34 tomagnetic medium 14 ofplatter 16, oroperating system 54 copies the contents ofcache memory 50 toHDD 56. Finally, inblock 74,controller 18 oroperating system 54 erasescache memory -
FIG. 5 is a flow chart of reading fromHDD 30 or 56. Inblock 80,controller 18 of HDD 30 receives an instruction from the host of HDD 30 to read data fromplatter 16, oroperating system 54 receives an instruction from an application program to read data fromHDD 56. Inblock 82,controller 18 oroperating system 54 determines whethercache memory cache memory block 84,controller 18 reads the data directly frommagnetic medium 14 ofplatter 16, oroperating system 54 reads the data directly fromHDD 56. Ifcache memory HDD 30 or 56 may still be incache memory platter 16 or fromHDD 56. Therefore, inblock 86,controller 18 oroperating system 54 determines whether the requested data are present incache memory cache memory block 88controller 18 oroperating system 54 reads the data fromcache memory block 84,controller 18 reads the data directly frommagnetic medium 14 ofplatter 16, oroperating system 54 reads the data directly fromHDD 56. - The present invention, as described above, supports an innovative method of producing computer systems. The computer systems are manufactured with hard disk drives and with interfaces for cache memories as described above. The interfaces could be integral to the hard disk drives, if the hard disk drives are configured like HDD 30; or alternatively the interfaces could be coupled to the hard disk drives via a system bus as in computer system 40. As orders for computer systems are received, the producer decides whether to fill each order with a computer system that includes a
cache memory interface 32 or 48 or, alternatively, to deliver the computer system withoutcache memory - While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made.
Claims (30)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/198,177 US20060230226A1 (en) | 2005-04-12 | 2005-08-08 | Hard disk drive with optional cache memory |
US13/450,340 US9424197B2 (en) | 2005-04-12 | 2012-04-18 | Hard disk drive with optional cache memory |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US67059405P | 2005-04-12 | 2005-04-12 | |
US11/198,177 US20060230226A1 (en) | 2005-04-12 | 2005-08-08 | Hard disk drive with optional cache memory |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/450,340 Division US9424197B2 (en) | 2005-04-12 | 2012-04-18 | Hard disk drive with optional cache memory |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060230226A1 true US20060230226A1 (en) | 2006-10-12 |
Family
ID=37084393
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/198,177 Abandoned US20060230226A1 (en) | 2005-04-12 | 2005-08-08 | Hard disk drive with optional cache memory |
US13/450,340 Active US9424197B2 (en) | 2005-04-12 | 2012-04-18 | Hard disk drive with optional cache memory |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/450,340 Active US9424197B2 (en) | 2005-04-12 | 2012-04-18 | Hard disk drive with optional cache memory |
Country Status (1)
Country | Link |
---|---|
US (2) | US20060230226A1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070156954A1 (en) * | 2005-12-29 | 2007-07-05 | Intel Corporation | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessiblity |
US20080140921A1 (en) * | 2004-06-10 | 2008-06-12 | Sehat Sutardja | Externally removable non-volatile semiconductor memory module for hard disk drives |
US20080276016A1 (en) * | 2007-05-02 | 2008-11-06 | Akira Fujibayashi | Storage controller and storage controller control method |
US20090024793A1 (en) * | 2007-07-17 | 2009-01-22 | Fontenot Nathan D | Method and apparatus for managing data in a hybrid drive system |
US20090135700A1 (en) * | 2007-11-28 | 2009-05-28 | Akira Fujibayashi | Storage controller and storage controller control method |
US20090164733A1 (en) * | 2007-12-21 | 2009-06-25 | Mips Technologies, Inc. | Apparatus and method for controlling the exclusivity mode of a level-two cache |
US20090193176A1 (en) * | 2008-01-30 | 2009-07-30 | Universal Scientific Industrial Co., Ltd | Data storage device having a built-in display |
US8527692B2 (en) * | 2011-08-26 | 2013-09-03 | Hewlett-Packard Development Company, L.P. | Data storage apparatus with a HDD and a removable solid state device |
CN103778024A (en) * | 2012-10-24 | 2014-05-07 | 英业达科技有限公司 | Server system and message processing method thereof |
US9158355B2 (en) | 2006-08-10 | 2015-10-13 | Marvell World Trade Ltd. | Dynamic core switching |
US9424197B2 (en) | 2005-04-12 | 2016-08-23 | Sandisk Il Ltd. | Hard disk drive with optional cache memory |
US9558124B2 (en) | 2013-11-08 | 2017-01-31 | Seagate Technology Llc | Data storage system with passive partitioning in a secondary memory |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105824570B (en) * | 2015-01-04 | 2018-11-23 | 致伸科技股份有限公司 | The method that the hard disk device of power consumption can be reduced and reduce hard disk device power consumption |
US9927975B2 (en) * | 2016-08-03 | 2018-03-27 | Micron Technology, Inc. | Hybrid memory drives, computer system, and related method for operating a multi-mode hybrid drive |
Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4399503A (en) * | 1978-06-30 | 1983-08-16 | Bunker Ramo Corporation | Dynamic disk buffer control unit |
US5133060A (en) * | 1989-06-05 | 1992-07-21 | Compuadd Corporation | Disk controller includes cache memory and a local processor which limits data transfers from memory to cache in accordance with a maximum look ahead parameter |
US5321814A (en) * | 1991-01-25 | 1994-06-14 | Unisys Corporation | System for optional module detection and reconfiguration |
US5325509A (en) * | 1991-03-05 | 1994-06-28 | Zitel Corporation | Method of operating a cache memory including determining desirability of cache ahead or cache behind based on a number of available I/O operations |
US5584012A (en) * | 1993-06-08 | 1996-12-10 | Hitachi, Ltd. | Cache control method and rotary storage device having cache control |
US5586291A (en) * | 1994-12-23 | 1996-12-17 | Emc Corporation | Disk controller with volatile and non-volatile cache memories |
US5638506A (en) * | 1991-04-08 | 1997-06-10 | Storage Technology Corporation | Method for logically isolating a cache memory bank from a memory bank group |
US5860083A (en) * | 1996-11-26 | 1999-01-12 | Kabushiki Kaisha Toshiba | Data storage system having flash memory and disk drive |
US6028725A (en) * | 1997-06-30 | 2000-02-22 | Emc Corporation | Method and apparatus for increasing disc drive performance |
US20010047394A1 (en) * | 1999-09-10 | 2001-11-29 | Kloba David D. | System, method, and computer program product for executing scripts on mobile devices |
US6396913B1 (en) * | 1999-10-22 | 2002-05-28 | Convergys Cmg Utah Inc. | System and method for processing call detail records |
US6480933B1 (en) * | 1998-11-06 | 2002-11-12 | Bull S.A. | Disk cache device and method for secure writing of hard disks in mass memory subsystems |
US6665755B2 (en) * | 2000-12-22 | 2003-12-16 | Nortel Networks Limited | External memory engine selectable pipeline architecture |
US6725342B1 (en) * | 2000-09-26 | 2004-04-20 | Intel Corporation | Non-volatile mass storage cache coherency apparatus |
US6754725B1 (en) * | 2001-05-07 | 2004-06-22 | Cypress Semiconductor Corp. | USB peripheral containing its own device driver |
US6766413B2 (en) * | 2001-03-01 | 2004-07-20 | Stratus Technologies Bermuda Ltd. | Systems and methods for caching with file-level granularity |
US6785132B1 (en) * | 2000-06-07 | 2004-08-31 | Crystal Group Inc. | Method and system for providing flash memory in an industrial personal computer |
US20050125602A1 (en) * | 2003-12-04 | 2005-06-09 | Ehrlich Richard M. | HDD with storage of critical data in FLASH |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2681969B1 (en) * | 1991-09-26 | 1993-12-24 | Hewlett Packard Cy | DEVICE FOR INDICATING THE PRESENCE OF AN OPTIONAL COMPONENT ON A CARD. |
US5636355A (en) * | 1993-06-30 | 1997-06-03 | Digital Equipment Corporation | Disk cache management techniques using non-volatile storage |
ATE239255T1 (en) * | 1998-08-10 | 2003-05-15 | Micron Technology Inc | PROCESSOR OR CENTRAL UNIT WITH INTERNAL REGISTER FOR PERIPHERAL STATUS |
IL130796A (en) * | 1999-07-05 | 2003-07-06 | Brightcom Technologies Ltd | Packet processor |
US6629211B2 (en) * | 2001-04-20 | 2003-09-30 | International Business Machines Corporation | Method and system for improving raid controller performance through adaptive write back/write through caching |
US7100076B2 (en) * | 2003-05-09 | 2006-08-29 | Hewlett-Packard Development Company, L.P. | Minimum latency reinstatement of database transaction locks |
US7644239B2 (en) | 2004-05-03 | 2010-01-05 | Microsoft Corporation | Non-volatile memory cache performance improvement |
US7490197B2 (en) * | 2004-10-21 | 2009-02-10 | Microsoft Corporation | Using external memory devices to improve system performance |
US20060230226A1 (en) | 2005-04-12 | 2006-10-12 | M-Systems Flash Disk Pioneers, Ltd. | Hard disk drive with optional cache memory |
-
2005
- 2005-08-08 US US11/198,177 patent/US20060230226A1/en not_active Abandoned
-
2012
- 2012-04-18 US US13/450,340 patent/US9424197B2/en active Active
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4399503A (en) * | 1978-06-30 | 1983-08-16 | Bunker Ramo Corporation | Dynamic disk buffer control unit |
US5133060A (en) * | 1989-06-05 | 1992-07-21 | Compuadd Corporation | Disk controller includes cache memory and a local processor which limits data transfers from memory to cache in accordance with a maximum look ahead parameter |
US5321814A (en) * | 1991-01-25 | 1994-06-14 | Unisys Corporation | System for optional module detection and reconfiguration |
US5325509A (en) * | 1991-03-05 | 1994-06-28 | Zitel Corporation | Method of operating a cache memory including determining desirability of cache ahead or cache behind based on a number of available I/O operations |
US5638506A (en) * | 1991-04-08 | 1997-06-10 | Storage Technology Corporation | Method for logically isolating a cache memory bank from a memory bank group |
US5584012A (en) * | 1993-06-08 | 1996-12-10 | Hitachi, Ltd. | Cache control method and rotary storage device having cache control |
US5586291A (en) * | 1994-12-23 | 1996-12-17 | Emc Corporation | Disk controller with volatile and non-volatile cache memories |
US5860083A (en) * | 1996-11-26 | 1999-01-12 | Kabushiki Kaisha Toshiba | Data storage system having flash memory and disk drive |
US6028725A (en) * | 1997-06-30 | 2000-02-22 | Emc Corporation | Method and apparatus for increasing disc drive performance |
US6480933B1 (en) * | 1998-11-06 | 2002-11-12 | Bull S.A. | Disk cache device and method for secure writing of hard disks in mass memory subsystems |
US20010047394A1 (en) * | 1999-09-10 | 2001-11-29 | Kloba David D. | System, method, and computer program product for executing scripts on mobile devices |
US6396913B1 (en) * | 1999-10-22 | 2002-05-28 | Convergys Cmg Utah Inc. | System and method for processing call detail records |
US6785132B1 (en) * | 2000-06-07 | 2004-08-31 | Crystal Group Inc. | Method and system for providing flash memory in an industrial personal computer |
US6725342B1 (en) * | 2000-09-26 | 2004-04-20 | Intel Corporation | Non-volatile mass storage cache coherency apparatus |
US6665755B2 (en) * | 2000-12-22 | 2003-12-16 | Nortel Networks Limited | External memory engine selectable pipeline architecture |
US6766413B2 (en) * | 2001-03-01 | 2004-07-20 | Stratus Technologies Bermuda Ltd. | Systems and methods for caching with file-level granularity |
US6754725B1 (en) * | 2001-05-07 | 2004-06-22 | Cypress Semiconductor Corp. | USB peripheral containing its own device driver |
US20050125602A1 (en) * | 2003-12-04 | 2005-06-09 | Ehrlich Richard M. | HDD with storage of critical data in FLASH |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080140921A1 (en) * | 2004-06-10 | 2008-06-12 | Sehat Sutardja | Externally removable non-volatile semiconductor memory module for hard disk drives |
US9424197B2 (en) | 2005-04-12 | 2016-08-23 | Sandisk Il Ltd. | Hard disk drive with optional cache memory |
US8347141B2 (en) | 2005-12-29 | 2013-01-01 | Intel Corporation | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessibility |
US20090077313A1 (en) * | 2005-12-29 | 2009-03-19 | Trika Sanjeev N | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessibility |
US7627713B2 (en) * | 2005-12-29 | 2009-12-01 | Intel Corporation | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessibility |
US20070156954A1 (en) * | 2005-12-29 | 2007-07-05 | Intel Corporation | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessiblity |
US7962785B2 (en) | 2005-12-29 | 2011-06-14 | Intel Corporation | Method and apparatus to maintain data integrity in disk cache memory during and after periods of cache inaccessibility |
US9158355B2 (en) | 2006-08-10 | 2015-10-13 | Marvell World Trade Ltd. | Dynamic core switching |
US20080276016A1 (en) * | 2007-05-02 | 2008-11-06 | Akira Fujibayashi | Storage controller and storage controller control method |
US20090024793A1 (en) * | 2007-07-17 | 2009-01-22 | Fontenot Nathan D | Method and apparatus for managing data in a hybrid drive system |
US7861038B2 (en) * | 2007-07-17 | 2010-12-28 | International Business Machines Corporation | Method and apparatus for managing data in a hybrid drive system |
US20090135700A1 (en) * | 2007-11-28 | 2009-05-28 | Akira Fujibayashi | Storage controller and storage controller control method |
US7917699B2 (en) * | 2007-12-21 | 2011-03-29 | Mips Technologies, Inc. | Apparatus and method for controlling the exclusivity mode of a level-two cache |
US8234456B2 (en) | 2007-12-21 | 2012-07-31 | Mips Technologies, Inc. | Apparatus and method for controlling the exclusivity mode of a level-two cache |
US20110153945A1 (en) * | 2007-12-21 | 2011-06-23 | Mips Technologies, Inc. | Apparatus and Method for Controlling the Exclusivity Mode of a Level-Two Cache |
US20090164733A1 (en) * | 2007-12-21 | 2009-06-25 | Mips Technologies, Inc. | Apparatus and method for controlling the exclusivity mode of a level-two cache |
US20090193176A1 (en) * | 2008-01-30 | 2009-07-30 | Universal Scientific Industrial Co., Ltd | Data storage device having a built-in display |
US8527692B2 (en) * | 2011-08-26 | 2013-09-03 | Hewlett-Packard Development Company, L.P. | Data storage apparatus with a HDD and a removable solid state device |
US8762637B2 (en) | 2011-08-26 | 2014-06-24 | Hewlett-Packard Development Company, L.P. | Data storage apparatus with a HDD and a removable solid state device |
CN103778024A (en) * | 2012-10-24 | 2014-05-07 | 英业达科技有限公司 | Server system and message processing method thereof |
US9558124B2 (en) | 2013-11-08 | 2017-01-31 | Seagate Technology Llc | Data storage system with passive partitioning in a secondary memory |
Also Published As
Publication number | Publication date |
---|---|
US9424197B2 (en) | 2016-08-23 |
US20120233385A1 (en) | 2012-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9424197B2 (en) | Hard disk drive with optional cache memory | |
US7549021B2 (en) | Enhanced data integrity using parallel volatile and non-volatile transfer buffers | |
US8433882B2 (en) | Disk array control device and storage device | |
US8180953B2 (en) | Data accessing method for flash memory, and storage system and controller system thereof | |
EP2538337B1 (en) | Command resequencing in memory operations | |
JP4836647B2 (en) | Storage device using nonvolatile cache memory and control method thereof | |
US20070130442A1 (en) | Apparatus and Methods Using Invalidity Indicators for Buffered Memory | |
US7441085B2 (en) | Memory control method for restoring data in a cache memory | |
TW201835768A (en) | Information processing device, storage device, and information processing system | |
US8531883B1 (en) | Managing data writing to memories | |
JP4791286B2 (en) | Disk device and electronic device | |
KR20080084082A (en) | Memory card and memory system including the same and operating method thereof | |
US20080025706A1 (en) | Information recording apparatus and control method thereof | |
US20070168607A1 (en) | Storage device using nonvolatile cache memory and control method thereof | |
US8112589B2 (en) | System for caching data from a main memory with a plurality of cache states | |
CN101118460A (en) | Adaptive storage system including hard disk drive with flash interface | |
US20070168605A1 (en) | Information storage device and its control method | |
US20070168602A1 (en) | Information storage device and its control method | |
US20070168603A1 (en) | Information recording apparatus and control method thereof | |
US8762636B2 (en) | Data storage system having a global cache memory distributed among non-volatile memories within system disk drives | |
US8156278B2 (en) | Non-volatile data storage system and method thereof | |
TW202004505A (en) | Data storing method and data storing apparatus for reducing power consumption upon sudden power-off | |
US20090027796A1 (en) | Information recording device and control method therefor | |
US20090222613A1 (en) | Information processing apparatus and nonvolatile semiconductor memory drive | |
US20070168604A1 (en) | Information recording apparatus and method for controlling the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: M-SYSTEMS FLASH DISK PIONEERS, LTD., ISRAEL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MEIR, AVRAHAM;ZYLBERBERG, YORAM;REEL/FRAME:016868/0581 Effective date: 20050803 |
|
AS | Assignment |
Owner name: MSYSTEMS LTD, ISRAEL Free format text: CHANGE OF NAME;ASSIGNOR:M-SYSTEMS FLASH DISK PIONEERS LTD.;REEL/FRAME:021798/0361 Effective date: 20060504 |
|
AS | Assignment |
Owner name: SANDISK IL LTD., ISRAEL Free format text: CHANGE OF NAME;ASSIGNOR:MSYSTEMS LTD;REEL/FRAME:021853/0846 Effective date: 20070101 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |