IP Library Granted Patent US 11,537,303
Granted Patent B1
US 11,537,303 · App. 17/338,487 · Granted Dec 27, 2022

Dissimilar write prioritization in ZNS devices

Inventors: Ramanathan Muthiah (Bangalore, IN); Rakesh Balakrishnan (Bangalore, IN); Eldhose Peter (Bangalore, IN); Judah Gamliel Hahn (Ofra, IL)
Assignee: Western Digital Technologies, Inc.
G06F3/0635G06F3/0619G06F3/0625G06F3/0652G06F3/0659G06F3/0679G06F12/0246G06F2212/403G06F2212/7201G06F2212/7211
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,537,303
App. No.
17/338,487
Granted
Dec 27, 2022
Kind
B1
Abstract

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. The data storage device can guide a host device to select a particular zone to open in zone namespace (ZNS) systems where the host device selects which zone to open. The data storage device tracks the workload of the various storage locations and create zones. The data storage device then provides selected zones having the least used storage locations with the idea of guiding the host device to select the zone having the least used storage locations. Thus, rather than utilizing a randomly selected unopened zone, the host will select, based upon guidance from the data storage device, zones that contain the least utilized storage location. In so doing, generally even workload of the memory device storage locations is achieved.

Claims (45)

1. A data storage device, comprising:

a memory device; and

a controller coupled to the memory device, wherein the controller is configured to:

create an empty zone map, wherein the empty zone map ranks zones within the empty zone map from least utilized to most utilized;

send the empty zone map to a host device;

receive a zone open command from the host device; and

receive a set of priorities and expected workloads from a host device.

2. The data storage device of claim 1 , wherein the empty zone map comprises at least one zone that has die interleaving.

3. The data storage device of claim 1 , wherein the empty zone map comprises zones made from worn-out blocks of the memory device.

4. The data storage device of claim 1 , wherein the controller is further configured to exclude one or more potential zones that can be created in the zone map.

5. The data storage device of claim 1 , wherein the controller is further configured to create the empty zone map after receiving the set of priorities and expected workloads from the host device.

6. The data storage device of claim 1 , wherein the empty zone map is additionally ranked based upon number of program-erase cycles for memory blocks within the memory device.

7. A data storage device, comprising:

a memory device; and

a controller coupled to the memory device, wherein the controller is configured to:

create a plurality of zones in a backend of the memory device;

rank the zones in a list from least utilized area of the backend to most utilized area of the backend;

forward at least a part of the list to a host device;

receive a zone open command from the host device; and

receive a set of priorities and expected workloads from the host device.

8. A data storage device, comprising:

a memory device; and

a controller coupled to the memory device, wherein the controller is configured to:

create a plurality of zones in a backend of the memory device;

rank the zones in a list from least utilized area of the backend to most utilized area of the backend;

forward at least a part of the list to a host device;

receive a zone open command from the host device; and

receive zone append commands, zone read commands, and the zone open command, wherein the commands are evaluated for priority of processing.

9. The data storage device of claim 8 , wherein the evaluation occurs at a flash translation layer (FTL).

10. The data storage device of claim 7 , wherein the zone open command is a zone command with zero offset.

11. The data storage device of claim 8 , wherein the controller is further configured to update a zone to logical block address table after opening a new zone.

12. The data storage device of claim 7 , wherein the controller is further configured to route zone read commands and zone append commands to the backend prior to opening a new zone.

13. The data storage device of claim 7 , wherein the part of the list comprises a zone from the least utilized area of the backend.

14. A data storage device, comprising:

memory means;

a controller coupled to the memory means, wherein the controller is configured to:

recommend a zone to be opened to a host device, wherein recommending a zone comprises providing a list of zones that can be opened to the host device, wherein the list comprises the recommended zone and other zones;

receive a zone open command from the host device to open the recommended zone; and

receive a set of priorities and expected workloads from the host device.

15. The data storage device of claim 14 , wherein the recommended zone has a lower workload history compared to the other zones.

16. The data storage device of claim 15 , wherein the lower workload history is based upon die workload, flash interface module (FIM) workload, cache workload, and/or parity check engine workload.

17. The data storage device of claim 14 , wherein the recommended zone has a same workload history compared to at least one other zone of the other zones.

18. The data storage device of claim 17 , wherein the recommended zone has undergone a fewer program-erase cycles compared to the at least one other zone.

19. The data storage device of claim 14 , wherein the controller is further configured to maintain wear leveling across physical blocks of the memory means.

20. The data storage device of claim 14 , wherein the recommending occurs prior to the receiving.

Assignments (10)
PARTIAL RELEASE OF SECURITY INTERESTS Recorded Apr 25, 2025
From: JPMORGAN CHASE BANK, N.A., AS AGENT
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 071382/0001 →
SECURITY AGREEMENT Recorded Apr 25, 2025
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 071050/0001 →
PATENT COLLATERAL AGREEMENT Recorded Aug 23, 2024
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS THE AGENT
Reel/Frame 068762/0494 →
CHANGE OF NAME Recorded Jun 27, 2024
From: SANDISK TECHNOLOGIES, INC.
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 067982/0032 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2024
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 067567/0682 →
PATENT COLLATERAL AGREEMENT - DDTL LOAN AGREEMENT Recorded Aug 21, 2023
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 067045/0156 →
PATENT COLLATERAL AGREEMENT - A&R LOAN AGREEMENT Recorded Aug 21, 2023
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 064715/0001 →
RELEASE OF SECURITY INTEREST AT REEL 057651 FRAME 0296 Recorded Feb 8, 2022
From: JPMORGAN CHASE BANK, N.A.
To: WESTERN DIGITAL TECHNOLOGIES, INC.
Reel/Frame 058981/0958 →
SECURITY INTEREST Recorded Sep 17, 2021
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS AGENT
Reel/Frame 057651/0296 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 3, 2021
From: MUTHIAH, RAMANATHAN; BALAKRISHNAN, RAKESH; PETER, ELDHOSE; HAHN, JUDAH GAMLIEL
To: WESTERN DIGITAL TECHNOLOGIES, INC.
Reel/Frame 056434/0631 →