# US 2004/0064647 A1 · Method and apparatus to reduce power consumption and improve read/write performance of hard disk drives using non-volatile memory

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0064647 A1
- Document ID: US20040064647A1
- Status: Published application
- Kind: A1
- Application number: 10/372,734
- Filed: 2003-02-21
- Published: 2004-04-01
- Earliest claimed: 2002-06-27
- Assignees: Microsoft Corporation
- Inventors: Dean L. DeWhitt; Clark D. Nicholson; W. Jeff Westerinen; Michael R. Fortin; John M. Parchem; Charles P. Thacker
- Web page: https://patentgrep.com/patent/US20040064647A1

## CPC

- G06F 1/3203: Power management, i.e. event-based initiation of a power-saving mode
- G06F 3/0625: {Power saving in storage systems}
- G06F 3/0647: {Migration mechanisms}
- G06F 3/068: {Hybrid storage device}
- G06F 9/4418: {Suspend and resume; Hibernate and awake}
- G06F 3/0601: {Interfaces specially adapted for storage systems}
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

A method and apparatus to improve the read/write performance of a hard drive is presented. The hard drive includes solid state, non-volatile (NV) memory as a read/write cache. Data specified by the operating system is stored in the NV memory. The operating system provides a list of data to be put in NV memory. The data includes data to be pinned in NV memory and data that is dynamic. Pinned data persists in NV memory until the operating system commands it to be flushed. Dynamic data can be flushed by the hard drive controller. Data sent by an application for storage is temporary stored in NV memory in data blocks until the operating system commits it to the disk.

## Claims

### Claim 1

A method for operating a persistent storage device having solid state, non-volatile (“NV”) memory and a disk drive, the method comprising the steps of:
loading at least one block of data in NV memory from the disk drive in response to receiving a list of data to be pre-cached; and
flushing the at least one block of data in response to receiving a flush command.

### Claim 2 (depends on 1)

The method of claim 1 wherein the step of loading the at least one block of data in NV memory includes the step of pinning a block of data in the NV memory.

### Claim 3 (depends on 1)

The method of claim 1 wherein the step of loading the at least one block of data in NV memory includes the step of immediately spinning up the disk drive.

### Claim 4 (depends on 1)

The method of claim 1 wherein the NV memory has pinned data blocks and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing pinned data blocks in response to receiving a command to flush pinned data blocks.

### Claim 5 (depends on 1)

The method of claim 1 wherein the NV memory has non-pinned data blocks and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing non-pinned data blocks in response to receiving a command to flush a dynamic cache.

### Claim 6 (depends on 1)

The method of claim 1 wherein the NV memory has at least one pinned data block and at least one non-pinned data block and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing the at least one pinned data block and the at least one non-pinned data block in response to receiving a command to flush all data blocks.

### Claim 7 (depends on 1)

The method of claim 1 further comprising the step of providing capabilities to the computer system in response to receiving a request to provide capabilities.

### Claim 8 (depends on 1)

The method of claim 1 wherein the persistent storage device is in a computing device having a motherboard, the NV memory is located on the motherboard, and the step of loading at least one block of data in NV memory from the disk drive in response to receiving a list of data to be pre-cached includes the step of transferring the at least one block of data to the NV memory on the motherboard from the disk drive.

### Claim 9 (depends on 1)

The method of claim 1 wherein the persistent storage device is in a computing device having an iSCSI board, the NV memory is located on the iSCSI board, and the step of loading at least one block of data in NV memory from the disk drive in response to receiving a list of data to be pre-cached includes the step of transferring the at least one block of data to the NV memory on the iSCSI board from the disk drive.

### Claim 10

A method for operating a computer system having a persistent storage device having a disk drive and solid state, non-volatile (“NV) memory, the method comprising the steps of:
determining capabilities of the persistent storage device;
providing a list of blocks to pin in the NV memory to the persistent storage device if the persistent storage device has the ability to pin blocks; and
providing a list of blocks to cache in the NV memory to the persistent storage device.

### Claim 11 (depends on 10)

The method of claim 10 wherein the step of determining the capabilities of the persistent device comprises the steps of:
determining a size of the NV memory;
determining features supported by the NV memory; and
determining a state of the disk drive.

### Claim 12 (depends on 10)

The method of claim 10 further comprising the step of predicting a next set of blocks that will be accessed by a user.

### Claim 13 (depends on 12)

The method of claim 12 further comprising the steps of providing a list of the next set of blocks that will be accessed by the user to the persistent storage device and commanding the persistent storage device to cache the list of the next set of blocks.

### Claim 14 (depends on 10)

The method of claim 10 further comprising the step of commanding the persistent storage device to flush blocks listed in a flush list from NV memory to the disk drive.

### Claim 15 (depends on 14)

The method of claim 14 wherein the step of commanding the persistent storage device to flush blocks listed in a flush list comprises the step of commanding the persistent storage device to flush all blocks in NV memory to the disk drive.

### Claim 16 (depends on 14)

The method of claim 14 wherein the step of commanding the persistent storage device to flush blocks listed in a flush list comprises the step of commanding the persistent storage device to flush all pinned blocks in NV memory to the disk drive.

### Claim 17 (depends on 14)

The method of claim 14 wherein the step of commanding the persistent storage device to flush blocks listed in a flush list comprises the step of commanding the persistent storage device to flush all non-pinned blocks in NV memory to the disk drive.

### Claim 18 (depends on 10)

The method of claim 10 further comprising the step of commanding the persistent storage device to store a set of blocks in NV memory, the set of blocks forming a write transaction.

### Claim 19 (depends on 18)

The method of claim 18 further comprising the step of commanding the persistent storage device to commit the write transaction to the disk drive.

### Claim 20

An interface for enabling an operating system to control a solid state, non-volatile (“NV”) memory cache in a hard drive, the interface comprising: a first command to determine capabilities of the hard drive; a second command to pin a list of blocks in the NV memory; a third command to pre-cache a list of blocks in the NV memory; and a fourth command to flush commands from the NV memory to a hard drive disk.

### Claim 21 (depends on 20)

The interface of claim 20 further comprising a fifth command to write a set of blocks that comprise a write transaction to NV memory.

### Claim 22 (depends on 21)

The interface of claim 21 further comprising a sixth command to commit the write transaction to the hard drive disk.

### Claim 23 (depends on 20)

The interface of claim 20 wherein the fourth command to flush commands from the NV memory to the hard drive disk comprises an instruction to flush a list of blocks from the NV memory to the hard drive disk.

### Claim 24 (depends on 20)

The interface of claim 20 wherein the fourth command to flush commands from the NV memory to the hard drive disk comprises an instruction to flush all blocks in the NV memory from the NV memory to the hard drive disk.

### Claim 25 (depends on 20)

The interface of claim 20 wherein the fourth command to flush commands from the NV memory to the hard drive disk comprises an instruction to flush pinned blocks from the NV memory to the hard drive disk.

### Claim 26 (depends on 20)

The interface of claim 20 wherein the fourth command to flush commands from the NV memory to the hard drive disk comprises an instruction to flush a non-pinned blocks from the NV memory to the hard drive disk.

### Claim 27 (depends on 1)

A computer-readable medium having computer executable instructions for operating a persistent storage device having solid state, non-volatile (“NV”) memory and a disk drive, the computer executable instructions for performing the steps of claim 1.

### Claim 28 (depends on 27)

The computer-readable medium of claim 27 wherein the step of loading at least one block of data in NV memory includes the step of pinning a block of data in the NV memory.

### Claim 29 (depends on 27)

The computer-readable medium of claim 27 wherein the step of loading at least one block of data in NV memory includes the step of immediately spinning up the disk drive.

### Claim 30 (depends on 27)

The computer-readable medium of claim 27 wherein the NV memory has a static section for pinned data blocks and a dynamic section for non-pinned data blocks and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing pinned data blocks in response to receiving a command to flush pinned data blocks.

### Claim 31 (depends on 27)

The computer-readable medium of claim 27 wherein the NV memory has a static section for pinned data blocks and a dynamic section for non-pinned data blocks and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing non-pinned data blocks in response to receiving a command to flush a dynamic cache.

### Claim 32 (depends on 27)

The computer-readable medium of claim 27 wherein the NV memory has a static section for pinned data blocks and a dynamic section for non-pinned data blocks and the step of flushing the at least one block of data in response to receiving a flush command comprises the step of flushing pinned data blocks and non-pinned data blocks in response to receiving a command to flush all data blocks.

### Claim 33 (depends on 27)

The computer-readable medium of claim 27 further comprising the step of providing capabilities to the computer system in response to receiving a request to provide capabilities.

### Claim 34 (depends on 10)

A computer-readable medium having computer executable instructions for operating a computer system having a persistent storage device having NV memory and a disk drive, the computer executable instructions for performing the steps of claim 10.

### Claim 35 (depends on 34)

The computer-readable medium of claim 34 having further computer-executable instructions for performing the step of predicting a next set of blocks that will be accessed by a user.

### Claim 36 (depends on 35)

The computer-readable medium of claim 35 having further computer-executable instructions for performing the steps of providing a list of the next set of blocks that will be accessed by the user to the persistent storage device and commanding the persistent storage device to cache the list of the next set of blocks.

### Claim 37 (depends on 34)

The computer-readable medium of claim 34 having further computer-executable instructions for performing the step of commanding the persistent storage device to flush blocks listed in a flush list from NV memory to the disk drive.

### Claim 38 (depends on 37)

The computer-readable medium of claim 37 wherein the step of commanding the persistent storage device to flush blocks listed in a flush list comprises one of commanding the persistent storage device to flush all blocks in NV memory to the disk drive, commanding the persistent storage device to flush all pinned blocks in NV memory to the disk drive, and commanding the persistent storage device to flush all non-pinned blocks in NV memory to the disk drive.

### Claim 39 (depends on 34)

The computer-readable medium of claim 34 having further computer-executable instructions for performing the step of commanding the persistent storage device to store a set of blocks in NV memory, the set of blocks forming a write transaction.

### Claim 40 (depends on 39)

The computer-readable medium of claim 39 having further computer-executable instructions for performing the step of commanding the persistent storage device to commit the write transaction to the disk drive.

### Claim 41

A method for operating a persistent storage device having solid state, non-volatile (“NV”) memory and a disk drive in a computing device, the method comprising the steps of:
storing data received from the computing device in data blocks in NV memory;
determining when the NV memory available space is below a threshold;
flushing at least a portion of the NV memory to the disk drive if the NV memory available space is below the threshold; and
sending data stored on the disk drive that is requested by the computing device directly to the computing device.

### Claim 42 (depends on 41)

The method of claim 41 wherein the step of flushing the at least a portion of the NV memory to the disk drive comprises the steps of immediately spinning up the disk drive and flushing the at least a portion of the NV memory to the disk drive.

### Claim 43 (depends on 41)

The method of claim 41 wherein the step of flushing the at least a portion of the NV memory to the disk drive comprises the steps of waiting until the disk drive is spinning for data to be sent to the computing device and flushing the at least a portion of the NV memory to the disk drive after the disk drive has spun up.

### Claim 44

A persistent storage device comprising:
a disk drive;
an array of solid state, non-volatile (“NV”) memory blocks in communication with the disk drive and a controller, the controller in communication with the disk drive, the controller for controlling the disk drive and the NV memory and adapted to store at least one data block received from a computing device in at least one memory block in NV memory and flush the at least one block of data in response to receiving a flush command.

### Claim 45 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to load at least one block of data in NV memory from the disk drive in response to receiving a list of data to be pre-cached

### Claim 46 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to pin a block of data in the NV memory.

### Claim 47 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to immediately spin up the disk drive to load the at least one block of data in NV memory.

### Claim 48 (depends on 44)

The persistent storage device of claim 44 wherein each memory block is one of a pinned data block and a non-pinned data block and the controller is further adapted to flush pinned data blocks in response to receiving a command to flush pinned data blocks.

### Claim 49 (depends on 44)

The persistent storage device of claim 44 wherein each memory block is one of a pinned data block and a non-pinned data block and the controller is further adapted to flush non-pinned data blocks in response to receiving a command to flush a dynamic cache.

### Claim 50 (depends on 44)

The persistent storage device of claim 44 wherein the NV memory comprises an array of memory blocks, each memory block being one of a pinned data block and a non-pinned data block and the controller is further adapted to flush pinned data blocks and non-pinned data blocks in response to receiving a command to flush all data blocks.

### Claim 51 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to provide capabilities to the computer system in response to receiving a request to provide capabilities.

### Claim 52 (depends on 51)

The persistent storage device of claim 51 wherein the controller provides a size of the NV memory, features supported by the NV memory, and the state of the disk drive when the controller provides capabilities to the computer system,

### Claim 53 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to:
determine when the NV memory available space is below a threshold; and
flush at least a portion of the NV memory to the disk drive if the NV memory available space is below the threshold.

### Claim 54 (depends on 44)

The persistent storage device of claim 44 wherein the controller is further adapted to send data stored on the disk drive that is requested by a computing device directly to the computing device.
