METHODS FOR FACILITATING PERSISTENT STORAGE OF IN-MEMORY DATABASES AND DEVICES THEREOF

• US 20150370544A1
• Filed: 06/18/2014
• Published: 12/24/2015
• Est. Priority Date: 06/18/2014
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Santry, Douglas Joseph
• Granted Patent: US 9,934,008 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

A method, non-transitory computer readable medium, and application host computing device that parses assembly language code to identify a transaction block including an assignment to a memory location, the assembly language code associated with an application and output by a compiler. The assembly language code is modified to insert an invocation of a plurality of functions collectively configured to facilitate persistent storage of one or more data updates associated with the assignment at run-time. The assembly language code is assembled to generate object code and the object code is linked with at least a run-time library including a definition for each of the plurality of inserted functions to generate an executable file for the application.

Claims

1. An application host computing device, comprising:

a processor coupled to a memory and configured to execute programmed instructions stored in the memory to;

parse assembly language code to identify a transaction block including an assignment to a memory location, the assembly language code associated with an application and output by a compiler;

modify the assembly language code to insert an invocation of a plurality of functions collectively configured to facilitate persistent storage of one or more data updates associated with the assignment at run-time; and

assemble the assembly language code to generate object code and link the object code with at least a run-time library comprising a definition for each of the plurality of inserted functions to generate an executable file for the application.

2. The device of claim 1, wherein the plurality of functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

3. The device of claim 2, wherein the first function allocates a transaction descriptor data structure and places a pointer to the transaction descriptor data structure on a stack associated with the application, the second function inserts at least a location and a size associated with the assignment into an entry of the transaction descriptor, and the third function replicates data associated with the entry of the transaction descriptor to persistent data storage.

4. The device of claim 2, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

5. The device of claim 3, wherein the second function is further configured to determine whether the memory location is within a range of a mapped region for the application and only insert the location and the size associated with the assignment into the entry of the transaction descriptor when the memory location is determined to be within a range of the mapped region for the application.

6. The device of claim 3, wherein the memory location is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the plurality of functions are collectively further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

7. The device of claim 1, wherein the processor coupled to the memory is further configured to execute programmed instructions stored in the memory to execute the executable file and send the one or more data updates to persistent data storage by invoking the plurality of functions at run-time.

8. A method for facilitating persistent storage of in-memory databases, comprising:

parsing, with an application host computing device, assembly language code to identify a transaction block including an assignment to a memory location, the assembly language code associated with an application and output by a compiler;

modifying, with the application host computing device, the assembly language code to insert an invocation of a plurality of functions collectively configured to facilitate persistent storage of one or more data updates associated with the assignment at run-time; and

assembling, with the application host computing device, the assembly language code to generate object code and link the object code with at least a run-time library comprising a definition for each of the plurality of inserted functions to generate an executable file for the application.

9. The method of claim 8, wherein the plurality of functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

10. The method of claim 9, wherein the first function allocates a transaction descriptor data structure and places a pointer to the transaction descriptor data structure on a stack associated with the application, the second function inserts at least a location and a size associated with the assignment into an entry of the transaction descriptor, and the third function replicates data associated with the entry of the transaction descriptor to persistent data storage.

11. The method of claim 9, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

12. The method of claim 10, wherein the second function is further configured to determine whether the memory location is within a range of a mapped region for the application and only insert the location and the size associated with the assignment into the entry of the transaction descriptor when the memory location is determined to be within a range of the mapped region for the application.

13. The method of claim 10, wherein the memory location is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the plurality of functions are collectively further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

14. The method of claim 8, further comprising executing, with the application host computing device, the executable file and sending the one or more data updates to persistent data storage by invoking the plurality of functions at run-time.

15. A non-transitory computer readable medium having stored thereon instructions for facilitating persistent storage of in-memory databases comprising machine executable code which when executed by a processor, causes the processor to perform steps comprising:

parsing assembly language code to identify a transaction block including an assignment to a memory location, the assembly language code associated with an application and output by a compiler;

modifying the assembly language code to insert an invocation of a plurality of functions collectively configured to facilitate persistent storage of one or more data updates associated with the assignment at run-time; and

assembling the assembly language code to generate object code and link the object code with at least a run-time library comprising a definition for each of the plurality of inserted functions to generate an executable file for the application.

16. The medium of claim 15, wherein the plurality of functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

17. The medium of claim 16, wherein the first function allocates a transaction descriptor data structure and places a pointer to the transaction descriptor data structure on a stack associated with the application, the second function inserts at least a location and a size associated with the assignment into an entry of the transaction descriptor, and the third function replicates data associated with the entry of the transaction descriptor to persistent data storage.

18. The medium of claim 16, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

19. The medium of claim 17, wherein the second function is further configured to determine whether the memory location is within a range of a mapped region for the application and only insert the location and the size associated with the assignment into the entry of the transaction descriptor when the memory location is determined to be within a range of the mapped region for the application.

20. The medium of claim 17, wherein the memory location is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the plurality of functions are collectively further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

21. The medium of claim 15, further having stored thereon instructions comprising machine executable code which when executed by the processor, further causes the processor to perform steps further comprising executing the executable file and sending the one or more data updates to persistent data storage by invoking the plurality of functions at run-time.