Managing cache pools

• US 9,141,527 B2
• Filed: 02/27/2012
• Issued: 09/22/2015
• Est. Priority Date: 02/25/2011
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: Intelligent Intellectual Property Holdings LLC
• Inventors: Atkisson, David, Flynn, David
• Primary Examiner(s): Choe, Yong
• Assistant Examiner(s): Waddy, Jr., Edward
• Application Number:
  US13/406,287
• Publication Number:
  US 20120221774A1
• Time in Patent Office: 1,303 Days
• Field of Search: 711/103, 711/133, 711/135, 711/118, 711/171, 711/E12.019, 711/E12.022, 711/E12.04, 711/113, 711/143, 711/154, 711/E12.008, 711/E12.026, 711/E12.001, 711/170
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 12/0802 Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
• CPC Class Codes: G06F 12/0895 of parts of caches, e.g. directory or tag array
• CPC Class Codes: G06F 12/126 with special data handling, e.g. priority of data or instructions, handling errors or pinning
• CPC Class Codes: G06F 2212/601 Reconfiguration of cache memory

Abstract

Apparatuses, systems, and methods are disclosed for managing cache pools. A storage request module monitors storage requests received by a cache. The storage requests include read requests and write requests. A read pool module adjusts a size of a read pool of the cache to increase a read hit rate of the storage requests. A dirty write pool module adjusts a size of a dirty write pool of the cache to increase a dirty write hit rate of the storage requests.

Claims

1. A method comprising:

monitoring storage requests received by a cache, the storage requests comprising read requests and write requests;

adjusting a size of a read pool of the cache to increase a read hit rate of the storage requests; and

adjusting a size of a dirty write pool of the cache to increase a dirty write hit rate of the storage requests,

wherein adjusting the size of the read pool and the dirty write pool comprises reducing a target pool size in response to a miss for a corresponding one of the read pool and the dirty write pool.

2. The method of claim 1, further comprising determining a target read pool size for the read pool and a target dirty write pool size for the dirty write pool based on the monitored storage requests received by the cache.

3. The method of claim 2, wherein adjusting the size of the read pool comprises selecting data for eviction from the cache based at least partially on a difference between an actual read pool size and the target read pool size.

4. The method of claim 3, wherein the read pool of the cache comprises a recent read pool and a frequent read pool and adjusting the size of the read pool further comprises increasing a target recent read pool size of the recent read pool in response to a read hit in the recent read pool, requested data transitioning from the recent read pool to the frequent read pool in response to a frequent read threshold number of read hits for the requested data in the recent read pool.

5. The method of claim 3, wherein adjusting the size of the read pool further comprises reducing the target read pool size in response to a read miss, the actual size of the read pool increasing in response to caching data of the read miss in the cache.

6. The method of claim 2, wherein adjusting the size of the dirty write pool of the cache comprises destaging dirty write data from the dirty write pool of the cache at a destage rate, the destage rate based on a difference between an actual dirty write pool size and the target dirty write pool size.

7. The method of claim 6, further comprising setting the destage rate such that the size of the dirty write pool remains within a maximum dirty write pool size of the dirty write pool.

8. The method of claim 6, wherein adjusting the size of the dirty write pool further comprises increasing the target dirty write pool size in response to a dirty write hit.

9. The method of claim 6, wherein adjusting the size of the dirty write pool further comprises increasing the target dirty write pool size in response to a clean write hit.

10. The method of claim 6, wherein adjusting the size of the dirty write pool further comprises decreasing the target dirty write pool size in response to a write miss, the actual size of the dirty write pool increasing in response to servicing a write request of the write miss.

11. The method of claim 1, wherein the read pool of the cache comprises a recent read pool and a frequent read pool, adjusting the size of the read pool comprises adjusting a size of the recent read pool to increase the read hit rate of the storage requests, and adjusting the size of the read pool further comprises adjusting a size of the frequent read pool to increase the read hit rate of the storage requests.

12. The method of claim 1, further comprising adjusting a size of a clean write pool of the cache to increase the read hit rate and the dirty write hit rate of the storage requests, wherein adjusting the size of the clean write pool of the cache comprises adjusting a destage rate at which data is moved from the dirty write pool to the clean write pool to increase the dirty write hit rate and adjusting an eviction rate at which data is evicted from the clean write pool to increase the read hit rate.

13. The method of claim 1, further comprising,

reading requested data from the cache to service a read request;

and

writing the requested data forward on a sequential log-based writing structure of the cache in response to the read request.

14. The method of claim 13, wherein the read request satisfies a frequent read threshold number of read hits for the requested data, the requested data transitioning from a recent read pool of the read pool to a frequent read pool of the read pool in response to the read request.

15. The method of claim 1, further comprising maintaining metadata for evicted data, the evicted data comprising read data from the read pool and clean write data destaged from the dirty write pool.

16. The method of claim 15, wherein the metadata comprises one or more entries for the evicted data in a mapping structure, the mapping structure mapping logical addresses of the cache to locations on physical storage media of the cache, the metadata for the evicted data indicating that the physical storage media of the cache does not currently store the evicted data.

17. The method of claim 15, further comprising adding the evicted data to a frequent read pool of the read pool of the cache, based on the metadata for the evicted data, in response to a subsequent read request for the evicted data.

18. An apparatus comprising:

a storage request module configured to monitor storage requests received by a cache, the storage requests comprising read requests and write requests;

a read pool module configured to determine a target read pool size for a read pool of the cache to increase a read hit rate of the storage requests, wherein determining the target read pool size comprises reducing the target read pool size in response to a read miss;

an eviction module configured to select data for eviction from the cache based at least partially on a difference between an actual read pool size and the target read pool size;

a dirty write pool module configured to determine a target dirty write pool size for a dirty write pool of the cache to increase a dirty write hit rate of the storage requests; and

a destage module configured to adjust a destage rate for destaging dirty write data from the dirty write pool of the cache, the destage module configured to adjust the destage rate based on a difference between an actual dirty write pool size and the target dirty write pool size.

19. The apparatus of claim 18, further comprising a clean write pool module configured to determine a target clean write pool size for a clean write pool of the cache based on the monitored storage requests, wherein the eviction module is configured to select the data for eviction from the cache based at least partially on a difference between an actual clean write pool size and the target clean write pool size.

20. A system comprising:

a processor;

a storage controller for a nonvolatile solid-state storage device, the nonvolatile solid-state storage device in communication with the processor over one or more communications buses;

a cache controller in communication with the storage controller, the cache controller comprising,

a storage request module configured to monitor storage requests received by the cache controller, the storage requests comprising read requests and write requests;

a read pool module configured to adjust a size of a read pool of the cache to increase a read hit rate of the storage requests; and

a dirty write pool module configured to adjust a size of a dirty write pool of the cache to increase a dirty write hit rate of the storage requests, wherein adjusting the size of the dirty write pool comprises reducing a target dirty write pool size in response to a write miss.