Apparatus, system, and method for a persistent object store

• US 9,026,717 B2
• Filed: 09/30/2011
• Issued: 05/05/2015
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: Sandisk Technologies Incorporated (Western Digital Corporation)
• Inventors: Ludwig, Jonathan, Barnes, Ethan, Dixon, Drex
• Primary Examiner(s): Bradley, Matthew
• Assistant Examiner(s): GOLDSCHMIDT, CRAIG S
• Application Number:
  US13/250,943
• Publication Number:
  US 20130086303A1
• Time in Patent Office: 1,313 Days
• Field of Search: 711/103
• US Class Current: 711/103
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/79 in semiconductor storage media, e.g. directly-addressable memories
• CPC Class Codes: G06F 21/80 in storage media based on magnetic or optical technology, e.g. disks with sectors preventing unauthorised reproduction or copying of disc-type recordable media G11B20/00
• CPC Class Codes: G06F 3/06 Digital input from, or digital output to, record carriers , e.g. RAID, emulated record carriers or networked record carriers

Abstract

An apparatus, system, and method are disclosed for persistently storing data objects. An object store index module maintains an object store. The object store associates each data object of a plurality of data objects with a unique key value. A storage module persists object store data defining the object store to a logical block address of the solid-state storage device in response to an update event. The logical block address is a member of a restricted set of logical block addresses. The logical block address is mapped to a location of the object store data on the solid-state storage device. A read module provides a requested data object from the plurality of data objects to a requesting client in response to receiving a read request for the requested data object from the requesting client. The read request comprises the key value associated with the requested data object.

Claims

1. A method, comprising:

maintaining an object store, the object store associating each data object of a plurality of data objects with a unique key value;

persisting data of the object store to a restricted set of logical block addresses of a logical address space, wherein the logical block addresses are mappable to any of a plurality of physical storage locations of the solid-state storage device, the object store data comprising an object store index;

storing a received data object within the object store index in response to a size of the received data object being less than or equal to a size threshold;

storing the received data object at a logical block address separate from the object store index in response to the size of the received data object being greater than the size threshold, wherein the associated logical block address is a member of the restricted set of logical block addresses; and

providing a requested data object from the plurality of data objects to a requesting client in response to receiving a read request for the requested data object from the requesting client, the read request comprising the key value associated with the requested data object.

2. The method of claim 1, wherein persisting the object store data to the logical block address comprises inserting the object store data into a write path for the solid-state storage device, the write path comprising both the object store data and workload data such that the object store data receives the same data protection characteristics as the workload data.

3. The method of claim 1, wherein persisting the object store data to the logical block address of the solid-state storage device comprises writing the object store data to an append point of a sequential log-based writing structure persisted on the solid-state storage device, the sequential log-based writing structure storing the object store data and workload data.

4. The method of claim 3, wherein the sequential log-based writing structure stores the object store data and the workload data using a mapping structure maintained by a storage controller, the mapping structure associating logical block addresses of a logical address space of the solid-state storage device with physical storage locations of the solid-state storage device for the object store data and the workload data.

5. The method of claim 1, wherein the logical block address for the object store data is a member of a sparse address space that is greater than a physically addressable capacity of the solid-state storage device and the sparse address space comprises a first set of logical block addresses that is available to clients of the solid-state storage device through a block device interface and the restricted set of logical block addresses that is unavailable to clients of the solid-state storage device through the block device interface.

6. The method of claim 1, wherein data stored in the restricted set of logical block addresses is at least one of, available to clients of the solid-state storage device exclusively through an object store interface;

and unavailable to clients of the solid-state storage device through a block device interface.

7. The method of claim 1, further comprising mapping a universal client identifier for the requesting client to an object store client identifier for the requesting client using a known mapping, wherein one or more key values and associated data objects of the object store are associated with the object store client identifier.

8. The method of claim 1, wherein clients of a same client type share a same object store client identifier and are associated with a same set of key values and associated data objects of the object store.

9. The method of claim 1, further comprising adding a received data object to the object store in response to receiving a write request from the requesting client.

10. The method of claim 9, further comprising one of receiving a key value associated with the received data object from the requesting client with the write request;

and generating a key value associated with the received data object in response to receiving the write request and sending the generated key value to the requesting client.

11. The method of claim 1, wherein each key value comprises one or more of a client identifier, a section identifier, and a key identifier, the client identifier associated with the requesting client, the section identifier associated with a group of data objects comprising an associated data object, the group of data objects having a common characteristic, and the key identifier identifying the associated data object.

12. An apparatus, comprising:

an object store index module that maintains an object store comprising an object store index comprising entries that map data objects stored on a solid-state storage medium to respective unique key values;

a storage controller of the solid-state storage medium that stores data of the object store, including the object store index, within a restricted set of logical block addresses of a logical address space;

a write module that stores a received data object within the object store index in response to a size of the received data object satisfying a size threshold, and stores the received data object outside of the object store index at a different logical block address within the restricted set of logical block addresses in response to the size of the received data object exceeding the size threshold; and

a read module that provides a requested data object from the plurality of data objects to a requesting client in response to receiving a read request for the requested data object from the requesting client, the read request comprising the key value associated with the requested data object.

13. The apparatus of claim 12, further comprising an identifier mapping module that maps a universal client identifier for the requesting client to an object store client identifier for the requesting client using a known mapping, wherein one or more key values and associated data objects of the object store are associated with the object store client identifier.

14. The apparatus of claim 12, wherein the storage module intermingles the object store data with the workload data by writing the object store data to an append point of a sequential log-based writing structure persisted on the solid-state storage medium, the sequential log-based writing structure storing the object store data and the workload data.

15. A system, comprising:

a solid-state storage device in communication with a host device;

a device driver for the solid-state storage device, the device driver executing on the host device, the device driver comprising,

an object store index module that maintains an object store, the object store associating each data object of a plurality of data objects with a unique key value by use of an object store index;

a storage module that persists object data including the object store index within a restricted set of logical block addresses of a logical address space of the solid-state storage device;

a write module to store a received data object within the object store index if the received data object satisfies a size threshold, and stores the received data object outside of the object store index at a different logical block address within the restricted set of logical block addresses if the received data object does not satisfy the size threshold; and

a read module that provides a requested data object from the plurality of data objects to a requesting client in response to receiving a read request for the requested data object from the requesting client, the read request comprising the key value associated with the requested data object.

16. The system of claim 15, wherein the device driver for the solid-state storage device provides access to data stored in the restricted set of logical block addresses exclusively through an object store interface.

17. The system of claim 15, wherein the device driver for the solid-state storage device provides access to data stored in logical block addresses associated with a reported capacity of the solid-state storage device through a block device interface for the solid-state storage device, data stored in the restricted set of logical block addresses unavailable through the block device interface.

18. The system of claim 15, further comprising the host device, the requesting client comprising one of a plurality of clients executing on the host device, the plurality of clients in communication with the solid-state storage device through the device driver.