IP Library › Granted Patent US 12,619,375
Granted Patent B2
US 12,619,375 · App. 18/760,436 · Granted May 5, 2026

Data storage device and method for accommodating data of a third-party system

Inventor: Ramanathan Muthiah (Bangalore, IN)
Assignee: Sandisk Technologies, Inc.
G06F3/0655G06F3/0604G06F3/0673
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 12,619,375
App. No.
18/760,436
Filed
Jul 1, 2024
Granted
May 5, 2026
Kind
B2
Art Unit
2137
USPC
711/154
Abstract

A data storage device and method are provided for accommodating data of a third-party system. In one embodiment, a data storage device is provided comprising a memory and one or more processors. The one or more processors, individually or in combination, are configured to: receive data from a graphics processing unit (GPU) of a host; segregate the data; determine whether the host is pre-approved for a capacity condition; and in response to determining that the host is pre-approved for the capacity condition: associate the segregated data per a pre-approved destination; and consolidate logical-to-physical address entry updates into a logical-to-physical address data structure. Other embodiments are provided.

Claims (59)

1 . A data storage device comprising:

a memory; and

one or more processors, individually or in combination, configured to:

receive data and a logical address directly from a graphics processing unit (GPU) of a host as opposed to indirectly through a central processing unit (CPU) of the host;

store the data in a location of the memory configured to store only data received from the GPU as opposed to data received from the CPU;

store an entry in a secondary logical-to-physical address data structure to reflect that the data is stored in the location in the memory, wherein the secondary logical-to-physical address data structure stores only entries for the location in the memory as opposed to other locations in the memory that store data received from the CPU;

determine whether the data is pre-approved for a capacity condition;

in response to determining that the data is not pre-approved for the capacity condition:

discard the entry in the secondary logical-to-physical address data structure; and

perform garbage collection only in the location in the memory as opposed to the other locations in the memory; and

in response to determining that the data is pre-approved for the capacity condition: merge the secondary logical-to-physical address data structure into a primary logical-to-physical address data structure that stores entries for the other locations in the memory.

2 . The data storage device of claim 1 , wherein the data is received with a GPU identifier.

3 . The data storage device of claim 1 , wherein the logical address is part of a logical block address (LBA) range associated with the GPU.

4 . The data storage device of claim 1 , wherein the one or more processors, individually or in combination, are further configured to:

move the data to capacity blocks.

5 . The data storage device of claim 1 , wherein the one or more processors, individually or in combination, are further configured to:

monitor input-output data of the GPU and at least one additional GPU; and

route the input-output data based on an instruction from the host.

6 . The data storage device of claim 1 , wherein the one or more processors, individually or in combination, are further configured to:

monitor input-output data of the GPU and at least one additional GPU; and

generate parity for the input-output data based on an instruction from the host.

7 . The data storage device of claim 1 , wherein the one or more processors, individually or in combination, are further configured to:

monitor input-output data of the GPU and at least one additional GPU; and

perform quality-of-service biasing of the input-output data based on an instruction from the host.

8 . The data storage device of claim 1 , wherein the memory comprises a three-dimensional memory.

9 . A method comprising:

performing in a data storage device comprising a memory:

receiving data and a logical address directly from a graphics processing unit (GPU) of a host as opposed to indirectly through a central processing unit (CPU) of the host;

storing the data in a location of the memory configured to store only data received from the GPU as opposed to data received from the CPU;

storing an entry in a secondary logical-to-physical address data structure to reflect that the data is stored in the location in the memory, wherein the secondary logical-to-physical address data structure stores only entries for the location in the memory as opposed to other locations in the memory that store data received from the CPU;

determining whether the host is pre-approved for a capacity condition;

in response to determining that the host is pre-approved for the capacity condition:

discarding the entry in the secondary logical-to-physical address data structure; and

performing garbage collection only in the location in the memory as opposed to the other locations in the memory; and

in response to determining that the data is pre-approved for the capacity condition: merging the secondary logical-to-physical address data structure into a primary logical-to-physical address data structure that stores entries for the other locations in the memory.

10 . The method of claim 9 , wherein the data is received with a GPU identifier.

11 . The method of claim 9 , wherein the logical address is part of a logical block address (LBA) range associated with the GPU.

12 . The method of claim 9 , further comprising:

moving the data to capacity blocks.

13 . The method of claim 9 , further comprising:

monitoring input-output data of the GPU and at least one additional GPU; and

routing the input-output data based on an instruction from the host.

14 . The method of claim 9 , further comprising:

monitoring input-output data of the GPU and at least one additional GPU; and

generating parity for the input-output data based on an instruction from the host.

15 . The method of claim 9 , further comprising:

monitoring input-output data of the GPU and at least one additional GPU; and

performing quality-of-service biasing of the input-output data based on an instruction from the host.

16 . A data storage device comprising:

a memory; and

means for:

receiving data and a logical address directly from a graphics processing unit (GPU) of a host as opposed to indirectly through a central processing unit (CPU) of the host;

storing the data in a location of the memory configured to store only data received from the GPU as opposed to data received from the CPU;

storing an entry in a secondary logical-to-physical address data structure to reflect that the data is stored in the location in the memory, wherein the secondary logical-to-physical address data structure stores only entries for the location in the memory as opposed to other locations in the memory that store data received from the CPU;

determining whether the host is pre-approved for a capacity condition;

in response to determining that the host is pre-approved for the capacity condition:

discarding the entry in the secondary logical-to-physical address data structure; and

performing garbage collection only in the location in the memory as opposed to the other locations in the memory; and

in response to determining that the host is pre-approved for the capacity condition: merging the secondary logical-to-physical address data structure into a primary logical-to-physical address data structure that stores entries for the other locations in the memory.

Assignments (4)
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2024
From: MUTHIAH, RAMANATHAN
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 067886/0203 →
Continuity (1)
Related Publication 20260003538A1 · Jan 1, 2026
References Cited (18)
US 8648867B2 · Gorchetchnikov et al. · 2014 [cited by applicant]
US 10216419B2 · De · 2019 [cited by applicant]
US 11941295B2 · Benisty et al. · 2024 [cited by applicant]
US 20080055322A1 · Ryan et al. · 2008 [cited by applicant]
US 20110292058A1 · Herr et al. · 2011 [cited by applicant]
US 20170147516A1 · De · 2017 [cited by examiner]
US 20190005606A1 · Yang · 2019 [cited by examiner]
US 20200356490A1 · Panesar et al. · 2020 [cited by applicant]
US 20210117333A1 · Qureshi · 2021 [cited by examiner]
US 20210223991A1 · Lee · 2021 [cited by examiner]
US 20230032278A1 · Zhu · 2023 [cited by examiner]
US 20230409217A1 · Ghaly · 2023 [cited by examiner]
US 20230409426A1 · Gurumurthi · 2023 [cited by examiner]
US 20240160376A1 · Ghaly · 2024 [cited by examiner]
US 20250007918A1 · Helmick · 2025 [cited by examiner]
US 20250156314A1 · Langer · 2025 [cited by examiner]
US 20250165182A1 · Subbarao · 2025 [cited by examiner]
Thompson, A. et al.; “GPUDirect Storage: A Direct Path Between Storage and GPU Memory”; Data Science Technical Blog entry; downloaded from the Internet on Jun. 30, 2024 at [cited by applicant]