IP Library Granted Patent US 9,128,826
Granted Patent B2
US 9,128,826 · App. 14/028,292 · Granted Sep 8, 2015

Data storage architecuture and system for high performance computing hash on metadata in reference to storage request in nonvolatile memory (NVM) location

Inventors: Paul Nowoczynski (Brooklyn, NY); Jason Micah Cope (Columbia, MD); Gordon Manning (Ellicott City, MD); Don Molaro (Cupertino, CA); Michael Piszczek (Laurel, MD); Pavan Uppu (Laurel, MD)
Assignee: DataDirect Networks, Inc.
G06F12/0246G06F12/0871G06F17/30067G06F17/30097G06F17/30194
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 9,128,826
App. No.
14/028,292
Granted
Sep 8, 2015
Kind
B2
Abstract

Data storage systems and methods for storing data are described herein. The storage system may be integrated with or coupled with a compute cluster or super computer having multiple computing nodes. A plurality of nonvolatile memory units may be included with computing nodes, coupled with computing nodes or coupled with input/output nodes. The input/output nodes may be included with the compute cluster or super computer, or coupled thereto. The nonvolatile memory units store data items provided by the computing nodes, and the input/output nodes maintain where the data items are stored in the nonvolatile memory units via a hash table distributed among the input/output nodes. The use of a distributed hash table allows for quick access to data items stored in the nonvolatile memory units even as the computing nodes are writing large amounts of data to the storage system quickly in bursts.

Claims (32)

1. A data storage method comprising:

an I/O node receiving a storage request from a computing node of a super computer;

the I/O node computing a hash on metadata for a data item referenced in the storage request to obtain a nonvolatile memory (NVM) location for the data item;

the I/O node creating an entry for the data item with the NVM location in its portion of a distributed hash table;

the I/O node determining if the data item was stored in an expected storage location based on the hash of the metadata of the data item;

if the data item was not stored in the expected storage location,

the I/O node communicating the NVM storage location of the data item to the expected I/O node,

the expected I/O node creating an entry for the data item in its portion of the distributed hash table,

the expected I/O node initiating sending the data item to primary storage,

the I/O node removing the entry for the data item from its portion of the distributed hash table, and

the expected I/O node updating its entry for the data item in its portion of the distributed hash table signifying that the data item has been moved to primary storage;

if the data item was stored in the expected storage location,

the expected I/O node initiating sending the data item to primary storage,

the I/O node updating its portion of the distributed hash table signifying that the data item is available in primary storage.

2. The method of claim 1 wherein the metadata includes a data item identifier and an offset for the data item.

3. The method of claim 1 wherein each entry in the distributed hash table includes either an address of one of the NVM units where the data item is stored or an indication the data item is stored in primary storage.

4. A data retrieval method comprising:

a computing node of a plurality of computing nodes performing a hash on metadata for a data item;

the computing node sending a read request for the data item to an input/output node (I/O node), the read request including the hash result;

the I/O node receiving the read request for the data item from the computing node;

the I/O node looking for an entry for the data item in its portion of a distributed hash table based on the hash result;

the I/O node obtaining the data item from a non-volatile memory location or from a primary storage;

the I/O node providing the data item to the computing node.

5. The method of claim 4 wherein the I/O node obtaining the data item from the primary storage includes reformatting the read request and forwarding the reformatted read request to the primary storage.

6. The method of claim 4 wherein the I/O node obtaining the data item from the non-volatile memory location includes the I/O node obtaining the data from its own non-volatile memory or group of non-volatile memory under its control and management.

7. The method of claim 4 wherein the I/O node obtaining the data item from the non-volatile memory location includes the I/O node forwarding the read request to another I/O node when the data item resides in the other I/O node's non-volatile memory or non-volatile memory under the other I/O node's control and management.

8. The method of claim 4 wherein the I/O node obtaining the data item from the non-volatile memory or from the primary storage comprises:

obtaining the data item from a non-volatile memory location included as the entry in the distributed hash table;

obtaining the data item from the primary storage when no entry for the hash of the metadata for the data item in the distributed hash table can be found.

9. The method of claim 4 wherein the entry in the hash table contains either an address in non-volatile memory of the data item or a flag signifying the data item is located in primary storage.

10. The method of claim 4 wherein the computing nodes form a super computer.

11. The method of claim 4 wherein the computing nodes form a compute cluster.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Jun 15, 2026
From: PREFERRED BANK
To: DATADIRECT NETWORKS, INC.
Reel/Frame 074955/0540 →
RELEASE OF SECURITY INTEREST Recorded Jun 12, 2026
From: TRIPLEPOINT CAPITAL LLC
To: DATADIRECT NETWORKS, INC.
Reel/Frame 075737/0508 →
RELEASE OF SECURITY INTEREST Recorded Apr 21, 2026
From: TRIPLEPOINT CAPITAL LLC
To: DATADIRECT NETWORKS, INC.
Reel/Frame 075478/0178 →
SECURITY INTEREST Recorded Oct 13, 2018
From: DATADIRECT NETWORKS, INC.
To: TRIPLEPOINT CAPITAL LLC
Reel/Frame 047228/0734 →
SECURITY INTEREST Recorded Jan 13, 2015
From: DATADIRECT NETWORKS, INC.
To: PREFERRED BANK, AS LENDER
Reel/Frame 034693/0698 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 17, 2013
From: MANNING, GORDON; PISZCZEK, MICHAEL; UPPU, PAVAN; COPE, JASON MICAH; NOWOCZYNSKI, PAUL; MOLARO, DON
To: DATADIRECT NETWORKS, INC.
Reel/Frame 031221/0887 →
Continuity (2)
Provisional Application 61715243 · Oct 17, 2012
Related Publication 20140108707A1 · Apr 17, 2014