Fast garbage collection in zoned namespaces SSDs
A data storage device includes a memory device and a controller coupled to the memory device. The data storage device supports zoned namespace. The controller is configured to maintain a zone timestamp table that includes a corresponding timestamp for each zone and add a timestamp to each garbage collection block of the memory device. The controller is further configured to scan a garbage collection block from a last physical block address (PBA) entry to a first PBA entry, determine a zone timestamp for the scanned PBA entry, and compare the zone timestamp to a timestamp of the garbage collection block. The controller is further configured to create and maintain a zone timestamp table and create and maintain a zone based defragmentation table.
1. A data storage device supporting zoned namespace, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
maintain a zone timestamp table that includes a corresponding timestamp for each zone; and
add a timestamp to each garbage collection block of the memory device.
2. The data storage device of claim 1 , wherein the controller is configured to determine that the corresponding timestamp for a zone is greater than the timestamp for a garbage collection block, wherein the zone has data in the garbage collection block, and wherein the data for the zone is invalid.
3. The data storage device of claim 1 , wherein the controller is configured to determine that the corresponding timestamp for a zone is less than the timestamp for a garbage collection block, wherein the zone has data in the garbage collection block, and wherein the data for the zone is valid.
4. The data storage device of claim 1 , wherein the controller is configured to determine that the corresponding timestamp for a zone is equal to the timestamp for a garbage collection block, wherein the zone has data in the garbage collection block, and wherein the data for the zone is valid.
5. The data storage device of claim 1 , wherein maintaining the zone timestamp table comprises updating a zone timestamp for a zone when the zone is reset and new data is written to a first logical block address (LBA) of the zone.
6. The data storage device of claim 1 , wherein maintaining the zone timestamp table comprises changing a timestamp for a zone from invalid to a timestamp that matches a timestamp of a corresponding garbage collection block in which a first logical block address (LBA) of the zone is written.
7. The data storage device of claim 1 , wherein adding a timestamp to each garbage block comprises adding the timestamp when the garbage collection block is allocated.
8. A data storage device supporting zoned namespace, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
scan a garbage collection block from a last physical block address (PBA) entry backwards to a first PBA entry, wherein each PBA entry comprises a logical block address (LBA) and data;
determine which zone a scanned PBA entry corresponds to;
check a zone timestamp table for a valid or invalid indication for the zone;
check the zone timestamp table for a zone timestamp corresponding to a LBA of the scanned PBA entry; and
compare the zone timestamp to a timestamp of the garbage collection block.
9. The data storage device of claim 8 , wherein determining which zone comprises shifting an LBA a number of bits to the right.
10. The data storage device of claim 8 , wherein the controller is configured to initialize all zones to valid prior to host write commands.
11. The data storage device of claim 8 , wherein the controller is configured to change a zone to invalid after determining a first LBA of the zone has been found to be valid.
12. The data storage device of claim 8 , wherein after comparing the zone timestamp to the timestamp of the garbage collection block, the controller is configured to indicate the data is invalid when the zone timestamp is greater than the timestamp of the garbage collection block.
13. The data storage device of claim 8 , wherein after comparing the zone timestamp to the timestamp of the garbage collection block, the controller is configured to indicate the data is valid when the zone timestamp is equal to or less than the timestamp of the garbage collection block.
14. The data storage device of claim 8 , wherein the controller is configured to update a zone defragmentation table with a beginning PBA for each zone and number of consecutive PBAs.
15. The data storage device of claim 14 , wherein the zone defragmentation table is updated prior to performing a garbage collection operation.
16. A data storage device, comprising:
a memory means; and
a controller coupled to the memory means, wherein the controller is configured to:
create and maintain a zone timestamp table;
create and maintain a zone-based defragmentation table; and
add a timestamp to each garbage collection block of the memory means.
17. The data storage device of claim 16 , wherein the zone-based defragmentation table comprises:
an indication of a number of zones moved;
a zone index;
an indication of a number of fragments of data pairs; and
an index of the data pairs that are fragmented.
18. The data storage device of claim 17 , wherein the index of the data pairs that are fragmented comprises a physical block address (PBA) starting location and a run length for the PBA.
19. The data storage device of claim 16 , wherein the zone timestamp table comprises a timestamp corresponding to each zone.
20. The data storage device of claim 19 , wherein the zone timestamp table comprises an indication of whether the zone in the garbage collection block is valid.