Auto-commit memory

• US 9,218,278 B2
• Filed: 03/15/2013
• Issued: 12/22/2015
• Est. Priority Date: 12/13/2010
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: Sandisk Technologies Incorporated (Western Digital Corporation)
• Inventors: Talagala, Nisha, Sundararaman, Swaminathan, Sridharan, Srinath
• Primary Examiner(s): PEUGH, BRIAN R
• Application Number:
  US13/838,070
• Publication Number:
  US 20130212321A1
• Time in Patent Office: 1,012 Days
• Field of Search: 711/103
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/554 involving event detection and direct action
• CPC Class Codes: G06F 21/56 Computer malware detection or handling, e.g. anti-virus arrangements
• CPC Class Codes: G06F 21/562 Static detection
• CPC Class Codes: G06F 21/563 by source code analysis
• CPC Class Codes: G06F 21/564 by virus signature recognition
• CPC Class Codes: G06F 21/565 by checking file integrity
• CPC Class Codes: G06F 21/566 Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
• CPC Class Codes: G06F 21/567 using dedicated hardware
• CPC Class Codes: G06F 2212/202 Non-volatile memory
• CPC Class Codes: G06F 2212/7203 Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
• CPC Class Codes: G06F 2212/7207 management of metadata or control data
• CPC Class Codes: H04L 63/14 for detecting or protecting against malicious traffic
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/1441 : Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/145 : the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
• CPC Class Codes: H04L 63/1458 : Denial of Service
• CPC Class Codes: H04L 63/1466 : Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
• CPC Class Codes: H04L 63/1475 : Passive attacks, e.g. eavesdropping or listening without modification of the traffic monitored
• CPC Class Codes: H04L 63/1483 : service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12
• CPC Class Codes: H04L 63/1491 : using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment

Abstract

Apparatuses, systems, methods, and computer program products are disclosed. A method includes processing metadata for data saved from a volatile memory buffer to a non-volatile storage medium. The data may be saved in response to a trigger event for a volatile memory buffer. A method includes locating saved data on a non-volatile storage medium. A method includes providing access to saved data after a trigger event based on processed metadata.

Claims

1. A method comprising:

processing metadata for data saved from a volatile memory buffer to a non-volatile storage medium, the data saved in response to a trigger event for the volatile memory buffer;

locating the saved data on the non-volatile storage medium; and

providing access to the saved data after the trigger event based on the processed metadata.

2. The method of claim 1, wherein providing access to the saved data comprises loading the saved data into the volatile memory buffer and mapping the volatile memory buffer into virtual memory of a client on a host computing device.

3. The method of claim 1, wherein providing access to the saved data comprises writing the saved data to a predefined location.

4. The method of claim 3, wherein the predefined location comprises one or more of a logical address of a block storage volume, an offset within a file, an application specific persistent object, a database record, and a volatile memory buffer.

5. The method of claim 1, further comprising providing the metadata to a different entity for additional processing.

6. The method of claim 5, wherein the metadata comprises multiple subsets for processing by multiple entities and the multiple subsets of the metadata comprise one or more of block metadata, file metadata, application metadata, process execution point metadata, and callback metadata for the saved data.

7. The method of claim 1, further comprising authenticating a recipient of the saved data, wherein the metadata comprises security data and access to the saved data is provided in response to valid authentication of the recipient of the saved data based on the security data.

8. The method of claim 1, wherein the metadata is processed in response to recovery from the trigger event for the volatile memory buffer, the trigger event comprising a restart event.

9. The method of claim 1, wherein the metadata comprises one or more of an identifier of an agent for processing the saved data and computer executable code for processing the saved data.

10. The method of claim 1, wherein access to the saved data is provided using a persistent unique identifier for the saved data, the metadata indicating the persistent unique identifier.

11. The method of claim 10, wherein the persistent unique identifier is a member of one or more of a file system namespace, a logical unit number (LUN) namespace, and a persistent memory namespace for the volatile buffer.

12. The method of claim 1, wherein the metadata identifies a location of the saved data in the non-volatile storage medium.

13. The method of claim 1, wherein access to the saved data is provided by one or more of:

automatically providing access after the trigger event; and

providing access in response to a client request after the trigger event.

14. An apparatus comprising:

a volatile memory buffer within an isolation zone of a non-volatile memory device, the memory buffer configured to store data in the non-volatile memory device in response to a trigger event; and

a commit agent configured to provide access to the data from the non-volatile memory device in response to recovery from the trigger event.

15. The apparatus of claim 14, further comprising one or more secondary commit agents configured to process at least a portion of the data, the commit agent configured to provide the data to the one or more secondary commit agents based on auto-commit metadata associated with the data.

16. The apparatus of claim 14, wherein the commit agent is configured to execute a triggered commit action for the data such that the data remains accessible after the trigger event, the triggered commit action identified in auto-commit metadata for the data.

17. An apparatus comprising:

an auto-commit memory configured to present one or more volatile auto-commit buffers to a host computing device, the one or more auto-commit buffers configured to write data from the one or more auto-commit buffers to a non-volatile recording medium;

a storage management layer configured to allocate the one or more auto-commit buffers to a user; and

a commit agent configured to provide the user with access to the data from the non-volatile recording medium after the data has been written to the non-volatile recording medium.

18. The apparatus of claim 17, wherein the storage management layer is configured to allocate the one or more auto-commit buffers to the user in response to a map request from the user.

19. The apparatus of claim 17, wherein the storage management layer is configured to reallocate the one or more auto-commit buffers in response to an unmap request from the user.

20. The apparatus of claim 17, wherein the storage management layer is configured to map the one or more auto-commit buffers into a virtual address space for the user on the host computing device.

21. The apparatus of claim 17, wherein the storage management layer is configured to dynamically reallocate the one or more auto-commit buffers to a different user based on a predefined memory management policy.

22. The apparatus of claim 17, wherein the auto-commit memory is configured to present the one or more volatile auto-commit buffers to the host computing device as non-volatile storage.