Dissimilar write prioritization in ZNS devices
The present disclosure generally relates to creating new zones in a data storage device in a manner that ensures substantially even workload of the memory device storage locations. When receiving a zone open command in a zone namespace (ZNS) system, rather than randomly selecting an unopen zone, zones may be categorized based upon storage location workload so that any new zone that is opened utilizes the least utilized storage location. In so doing, generally even workload of the memory device storage locations is achieved.
1. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
receive a zone open command;
determine that a tie exists in terms of workload between a first physical block and another physical block,
rank the first physical block and the another physical block based upon a number of program-erase cycles, wherein the first physical block has a fewer number of program-erase cycles; and
create a zone from the first physical block of the memory device, wherein the created zone corresponds to a physical block that has received the least workload in the memory device.
2. The data storage device of claim 1 , wherein the controller is further configured to receive a plurality of zone commands, wherein at least one of the plurality of zone commands is the zone open command.
3. The data storage device of claim 2 , wherein at least a first command of the plurality of commands is a zone read command, wherein the controller is further configured to process the zone read command prior to the zone open command.
4. The data storage device of claim 1 , wherein the workload is based upon amount of read and write activity for the physical block.
5. The data storage device of claim 1 , wherein the zone open command is processed after any zone append or zone read commands have begun executing.
6. The data storage device of claim 1 , wherein the least workload is based upon die workload, flash interface module (FIM) workload, cache workload, and/or parity check engine workload.
7. The data storage device of claim 1 , wherein the controller is configured to determine a plurality of physical blocks have the least workload, wherein the first physical block has a lower number of program-erase cycles as compared to a remainder of the plurality of physical blocks.
8. The data storage device of claim 1 , wherein the controller is further configured to maintain wear leveling across physical blocks of the memory device.
9. The data storage device of claim 1 , wherein the zone open command is received in a submission queue, and wherein the controller is configured to process any zone append commands or zone read commands prior to the zone open command.
10. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
receive a zone open command; and
create a zone from a first physical block of the memory device, wherein the created zone corresponds to a physical block that has received the least workload in the memory device, wherein the controller is further configured to receive a plurality of zone commands, wherein at least one of the plurality of zone commands is the zone open command, wherein at least a first command of the plurality of commands is a zone append command, wherein the controller is further configured to process the zone append command prior to the zone open command.
11. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
evaluate a plurality of commands received in a submission queue;
determine that a command of the plurality of commands is a zone open command;
evaluate a backend of the memory device to determine a workload of available dies of the memory device;
opening a new zone based upon the evaluation of the backend of the memory device; and
route data associated with the zone open command to the new zone.
12. The data storage device of claim 11 , wherein the controller is further configured to update a zone to logical block address table after opening the new zone.
13. The data storage device of claim 11 , wherein the controller is further configured to route zone read commands and zone append commands to the backend prior to opening the new zone.
14. The data storage device of claim 11 , wherein the evaluation occurs at a flash translation layer (FTL).
15. The data storage device of claim 11 , wherein the zone open command is a zone command with zero offset.
16. A data storage device, comprising:
memory means;
a controller coupled to the memory means, wherein the controller is configured to:
receive a zone open command;
determine multiple backend units of the memory means are eligible for a zone open and have a same amount of workload in the backend units;
determine that a first backend unit of the multiple backend units has a lower number of program-erase cycles as compared to a remainder of the multiple backend units eligible; and
open a new zone in the first backend unit.
17. The data storage device of claim 16 , wherein the controller is further configured to direct zone append commands to a second backend unit that is distinct from the first backend unit.
18. The data storage device of claim 17 , wherein the controller is further configured to direct zone read commands to a third backend unit that is distinct from the first backend unit.
19. The data storage device of claim 18 , wherein the controller is further configured to direct the zone append commands and the zone read commands to the second backend unit and the third backend unit respectively prior to determining multiple backend units of the memory means are eligible.
20. The data storage device of claim 16 , wherein the controller is further configured to search a submission queue to find the zone open command and any zone append command or any zone read command.