# US 2025/0224874 A1 · Dynamic And Shared CMB And HMB Allocation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0224874 A1
- Document ID: US20250224874A1
- Status: Published application
- Kind: A1
- Application number: 19/089,969
- Filed: 2025-03-25
- Published: 2025-07-10
- Earliest claimed: 2022-09-20
- Assignees: SanDisk Technologies LLC
- Applicants: Sandisk Technologies, Inc.
- Inventors: Shay BENISTY
- Web page: https://patentgrep.com/patent/US20250224874A1

## CPC

- G06F 3/0611: {in relation to response time}
- G06F 3/061: {Improving I/O performance}
- G06F 3/0656: {Data buffering arrangements}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 12/0868: Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
- G06F 12/0871: Allocation or management of cache space
- G06F 12/0888: using selective caching, e.g. bypass
- G06F 2212/1016: Performance improvement
- G06F 2212/313: In storage device
- G06F 2212/7203: Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A data storage device includes a controller. The controller includes a controller memory buffer (CMB). The controller is configured to associate both the CMB and a host memory buffer (HMB) of a host device as a single buffer pool with a plurality of CMB buffers and a plurality of HMB buffers. The controller is further configured to allocate either a CMB buffer or a HMB buffer based on a tradeoff between latency and performance between using the CMB or using the HMB to store data. By leveraging the benefits of both the CMB and the HMB to store data, the overall performance of the data storage device may be improved.

## Claims

### Claim 1

A data storage device, comprising:
a controller, wherein the controller comprises a controller memory buffer (CMB), and wherein the controller is configured to:
issue a write command to write data to a host memory buffer (HMB) of a host device;
determine whether a utilization of the CMB is greater than or equal to a threshold utilization;
allocate a buffer of the CMB when the utilization of the CMB is less than the threshold utilization; and
issue a write command to the CMB to cache the write data in the CMB.

### Claim 2 (depends on 1)

The data storage device of claim 1, wherein the write data is not programmed to the HMB.

### Claim 3 (depends on 1)

The data storage device of claim 1, wherein the controller is further configured to:
issue a read command to read the write data from the HMB;
determine whether the write data is cached in the CMB;
find a CMB address of the write data when the write data is cached in the CMB; and
issue a read command to the CMB to read the write data from the CMB.

### Claim 4 (depends on 3)

The data storage device of claim 3, wherein the write data is not read from the HMB.

### Claim 5 (depends on 1)

The data storage device of claim 1, wherein the data storage device does not include dynamic random access memory (DRAM).

### Claim 6 (depends on 1)

The data storage device of claim 1, wherein the controller further comprises a CMB/HMB scheduler, wherein the CMB/HMB scheduler is configured to dynamically allocate either a buffer of the CMB or a buffer of the HMB based on at least one of a latency of accessing either the CMB or the HMB and an availability of capacity of either the CMB or the HMB.

### Claim 7 (depends on 6)

The data storage device of claim 6, wherein the CMB/HMB scheduler is further configured to manage an address translation of the CMB and the HMB and an eviction of data from either the HMB to the CMB or the CMB to the HMB.

### Claim 8 (depends on 1)

The data storage device of claim 1, wherein the controller comprises a CMB-HMB scheduler.

### Claim 9 (depends on 8)

The data storage device of claim 8, wherein the CMB-HMB scheduler is configured to associate both the CMB and an HMB of a host device as a single buffer pool, wherein the single buffer pool comprises a plurality of CMB buffers and a plurality of HMB buffers.

### Claim 10 (depends on 9)

The data storage device of claim 9, wherein the CMB-HMB scheduler is configured to allocate either a CMB buffer from the plurality of CMB buffers or an HMB buffer from plurality of HMB buffers, wherein the allocating is based on a tradeoff between latency and performance between using the CMB or using the HMB to store data.

### Claim 11 (depends on 8)

The data storage device of claim 8, wherein the CMB-HMB scheduler is further configured to:
determine that an access request to write data to the HMB has been initiated;
determine whether a utilization of the CMB is less than a utilization threshold;
allocate the CMB buffer for the access request when the utilization of the CMB is less than the utilization threshold; and
issue a CMB write command to write the data to the CMB instead of the HMB.

### Claim 12 (depends on 11)

The data storage device of claim 11, wherein the CMB-HMB scheduler is further configured to:
determine that the utilization of the CMB is greater than or equal to the utilization threshold; and
issue an HMB write command to write the data to the HMB.

### Claim 13 (depends on 8)

The data storage device of claim 8, wherein the CMB-HMB scheduler is further configured to:
determine that an access request to read data from the HMB has been initiated;
determine whether the data is cached in the CMB buffer;
locate a CMB address of the CMB buffer associated with the data when the data is cached in the CMB buffer; and
issue a CMB read command to read the data using the CMB address from the CMB instead of the HMB.

### Claim 14 (depends on 13)

The data storage device of claim 13, wherein the CMB-HMB scheduler is further configured to:
determine that the data is not cached in the CMB buffer; and
issue an HMB read command to read the data from the HMB.

### Claim 15 (depends on 8)

The data storage device of claim 8, wherein the CMB-HMB scheduler is further configured to:
receive a write command to write data to the CMB from the host device;
determine whether at least a portion of the CMB buffer has been allocated to cache data by the controller; and
halt the write to the CMB when the at least the portion of the CMB buffer has been allocated to cache data by the controller.

### Claim 16 (depends on 15)

The data storage device of claim 15, wherein the CMB-HMB scheduler is further configured to evict at least a portion of the data cached in the CMB to the HMB buffer.

### Claim 17 (depends on 16)

The data storage device of claim 16, wherein the CMB-HMB scheduler is further configured to issue a CMB write command to program the write data to the CMB when the at least a portion of the write data cached in the CMB is evicted to the HMB buffer.

### Claim 18 (depends on 16)

The data storage device of claim 16, wherein the at least a portion of data cached in the CMB is associated with a HMB write command that was programmed to the CMB instead of the HMB.

### Claim 19 (depends on 15)

The data storage device of claim 15, wherein the CMB-HMB scheduler is further configured to:
determine that the at least a portion of the CMB buffer has not been allocated to cache data by the controller; and
issue a CMB write command to program the write data to the CMB.

### Claim 20 (depends on 8)

The data storage device of claim 8, wherein the CMB-HMB scheduler is further configured to move data stored in the CMB to the HMB or data stored in the HMB to the CMB based on an access frequency of the data stored in the CMB or the data stored in the HMB.
