STORAGE REGION MAPPING FOR A DATA STORAGE DEVICE

• US 20170017588A1
• Filed: 07/17/2015
• Published: 01/19/2017
• Est. Priority Date: 07/17/2015
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: Sandisk Technologies Incorporated (Western Digital Corporation)
• Inventors: THOMAS, NICHOLAS JAMES, FRID, MARINA, GENSHAFT, IGOR
• Granted Patent: US 9,626,312 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 12/1009 using page tables, e.g. page table structures
• CPC Class Codes: G06F 13/18 based on priority control G06F13/1605 takes precedence
• CPC Class Codes: G06F 2212/1024 Latency reduction
• CPC Class Codes: G06F 2212/656 Address space sharing
• CPC Class Codes: G06F 2212/7201 Logical to physical mapping or translation of blocks or pages
• CPC Class Codes: G06F 2212/7205 Cleaning, compaction, garbage collection, erase control
• CPC Class Codes: G06F 2212/7208 Multiple device management, e.g. distributing data over multiple flash devices
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0658 Controller construction arrangements
• CPC Class Codes: G06F 3/0688 Non-volatile semiconductor memory arrays

Abstract

A data storage device includes a controller coupled to multiple groups of data storage dies, such as a meta-meta-die. The controller is configured to write data to a first meta-block if a storage size associated with a first group of data storage dies associated with a first priority is greater than or equal to a threshold storage size. The first meta-block includes a respective block of each data storage die of the first group. The controller is further configured to write the data to a second meta-block if the storage size associated with the first group is less than the threshold storage size. The second meta-block includes a respective block of each data storage die of the first group and further includes a respective block of each data storage die of the second group. Each data storage die of the second group is associated with a second priority.

Claims

1. A data storage device comprising:

a memory device including multiple groups of data storage dies, the multiple groups including a first group and a second group, the first group associated with a first priority and the second group associated with a second priority; and

a controller coupled to the multiple groups of data storage dies, wherein the controller is configured to write data to a first meta-block if a storage size associated with the first group is greater than or equal to a threshold storage size, the first meta-block including a respective block of each data storage die of the first group, and wherein the controller is further configured to write the data to a second meta-block if the storage size associated with the first group is less than the threshold storage size, the second meta-block including a respective block of each data storage die of the first group and further including a respective block of each data storage die of the second group.

2. The data storage device of claim 1, wherein the multiple groups of data storage dies include a meta-meta-die.

3. The data storage device of claim 1, wherein the controller is further configured to store a status table indicating data storage dies associated with the first priority and data storage dies associated with the second priority.

4. The data storage device of claim 3, wherein the controller includes a mapping engine configured to access the status table to determine, in connection with a write operation to write data to the memory device, that each data storage die of the first group is associated with the first priority and that each data storage die of the second group is associated with the second priority.

5. The data storage device of claim 1, wherein the first priority indicates that each data storage die of the first group is available for a write operation and is not scheduled for a maintenance operation.

6. The data storage device of claim 1, wherein the second priority indicates that each data storage die of the second group is scheduled for a maintenance operation.

7. The data storage device of claim 1, wherein the multiple groups of data storage dies further include a third group of data storage dies, each data storage die of the third group of data storage dies having a third priority, and wherein the third priority indicates that each data storage die of the third group is unavailable for a write operation.

8. An apparatus comprising:

a memory device, wherein the memory device includes multiple groups of data storage dies, the multiple groups of data storage dies including a first group and a second group; and

a mapping engine, the mapping engine configured to determine that each data storage die of the first group has a first priority and that each data storage die of the second group has a second priority,

wherein the memory device is configured to write data to a first meta-block if a storage size associated with the first group is greater than or equal to a threshold storage size, the first meta-block including a respective block of each data storage die of the first group, and

wherein the memory device is further configured to write the data to a second meta-block if the storage size associated with the first group is less than the threshold storage size, the second meta-block including a respective block of each data storage die of the first group and further including a respective block of each data storage die of the second group.

9. The apparatus of claim 8, wherein the multiple groups of data storage dies include a third group of data storage dies, and wherein each data storage die of the third group is excluded from the first group and from the second group.

10. A method comprising:

in a data storage device that includes a controller coupled to a memory device,

wherein the memory device includes a plurality of memory dies, performing

selecting a first subset of the plurality of memory dies, each memory die of the first subset has a first priority;

if a storage size associated with the first subset is greater than or equal to a threshold storage size, writing data to a first meta-block that includes a respective block of each memory die of the first subset; and

if the storage size is less than the threshold storage size;

selecting a second subset of the plurality of memory dies, each memory die of the second subset has a second priority; and

writing the data to a second meta-block that includes a respective block of each memory die of the first subset and that includes a respective block of each memory die of the second subset.

11. The method of claim 10, wherein the storage size corresponds to a depth of the first meta-block.

12. The method of claim 10, wherein the first priority indicates that each memory die of the first subset has a higher priority for write operations than each memory die of the second subset.

13. The method of claim 10, wherein the second priority indicates that each memory die of the second subset is less healthy than each memory die of the first subset.

14. The method of claim 10, wherein the second priority indicates that each memory die of the second subset is scheduled for a data compaction process or for a data relocation process.

15. The method of claim 10, further comprising excluding memory dies of a third subset of the plurality of memory dies from the first meta-block or from the second meta-block.

16. The method of claim 15, wherein each memory die of the third subset is associated with a third priority.

17. The method of claim 16, wherein the third priority indicates that each memory die of the third subset is busy, closed to write operations, or has a defect.

18. The method of claim 10, wherein the controller stores a status table, and further comprising accessing the status table to determine that each memory die of the first subset is associated with the first priority.

19. The method of claim 18, further comprising updating the status table to indicate that each memory die of the first subset is associated with the second priority after writing the data to either the first meta-block or the second meta-block.

20. The method of claim 10, further comprising:

receiving a first request for write access to the memory device from an accessing device, the first request including first data; and

receiving a second request for write access to the memory device from the accessing device, the second request including second data.

21. The method of claim 20, further comprising aggregating the first data and the second data for a single write process, wherein writing the data to the first meta-block or to the second meta-block includes writing the first data and the second data to the first meta-block or to the second meta-block via the single write process.