# US 11,907,200 B2 · Persistent memory management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,200 B2 - Document ID: US11907200B2 - Status: Granted - Kind: B2 - Application number: 17/037,445 - Filed: 2020-09-29 - Published: 2021-01-28 - Granted: 2024-02-20 - Earliest claimed: 2010-12-13 - Assignees: SanDisk Technologies LLC - Applicants: SanDisk Technologies LLC - Inventors: Nisha Talagala; Swaminathan Sundararaman; David Flynn - Web page: https://patentgrep.com/patent/US11907200B2 ## CPC - G06F 16/2365: {Ensuring data consistency and integrity} - G06F 11/1441: {Resetting or repowering} - G06F 12/0804: with main memory updating (G06F12/0806 takes precedence) - G06F 11/1666: {where the redundant component is memory or memory area} - G06F 11/20: using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements - G06F 12/0238: {Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory} - G06F 2212/202: Non-volatile memory - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Apparatuses, systems, methods, and computer program products are disclosed for persistent memory management. Persistent memory management may include replicating a persistent data structure in volatile memory buffers of at least two non-volatile storage devices. Persistent memory management may include preserving a snapshot copy of data in association with completion of a barrier operation for the data. Persistent memory management may include determining which interface of a plurality of supported interfaces is to be used to flush data from a processor complex. ## Claims ### Claim 1 A method comprising: storing at least a portion of a data structure in a first volatile memory buffer within an isolation zone of a first non-volatile storage device, the first volatile memory buffer comprising a first auto-commit buffer of a first auto-commit memory that is configured to ensure that the data structure is preserved in the first non-volatile storage device in response to a trigger associated with the first auto-commit buffer; copying data of the at least a portion of the data structure stored in the first volatile memory buffer to a second volatile memory buffer within an isolation zone of a second non-volatile storage device such that both the first and second non-volatile storage devices independently ensure persistence of the data structure, the second volatile memory buffer comprising a second auto-commit buffer of a second auto-commit memory; receiving updated data for the at least a portion of the data structure stored in the first volatile memory buffer; and synchronizing, in response to the trigger associated with the first auto-commit buffer, the updated data of the at least a portion of the data structure stored in the first volatile memory buffer and the at least a portion of the data structure stored in the second volatile memory buffer such that the updated data of the data structure is accessible to both an application for the first non-volatile storage device and an application for the second non-volatile storage device. ### Claim 2 (depends on 1) The method of claim 1, wherein copying the data of the data structure is performed over a network interface from the first non-volatile storage device to the second non-volatile storage device. ### Claim 3 (depends on 2) The method of claim 2, wherein the network interface is independent of a processor and a host volatile memory of a host computing device. ### Claim 4 (depends on 2) The method of claim 2, wherein the network interface comprises one or more of a serial bus, a parallel bus, a peripheral component interconnect (PCI) interface, a PCI express (PCIe) interface, a universal serial bus (USB), an Ethernet interface, a small computer system interface (SCSI), and an advance technology attachment (ATA) interface. ### Claim 5 (depends on 1) The method of claim 1, wherein the data structure is accessible as a file associated with a filename. ### Claim 6 (depends on 5) The method of claim 5, wherein: a first portion of the file is stored in the first and second volatile memory buffers; and a second portion of the file is stored on the first and second non-volatile storage devices. ### Claim 7 (depends on 1) The method of claim 1, wherein copying the data of the data structure is performed at a byte granularity, the data of the data structure comprising one or more updates to the data structure. ### Claim 8 An apparatus comprising: a persistent data structure module configured to store at least a portion of a data structure in a first volatile memory buffer within an isolation zone of a first non-volatile storage device, the first volatile memory buffer comprising a first auto-commit buffer of a first auto-commit memory that is configured to ensure that the data structure is preserved in the first non-volatile storage device in response to a trigger associated with the first auto-commit buffer; and a replication module configured to copy data of the at least a portion of the data structure stored in the first volatile memory buffer to a second volatile memory buffer within an isolation zone of a second non-volatile storage device such that both the first and second non-volatile storage devices independently ensure persistence of the data structure, the second volatile memory buffer comprising a second auto-commit buffer of a second auto-commit memory; and a write module configured to receive updated data for the at least a portion of the data structure stored in the first volatile memory buffer, wherein the replication module is configured to synchronize, in response to the trigger associated with the first auto-commit buffer, the updated data of the at least a portion of the data structure stored in the first volatile memory buffer and the at least a portion of the data structure stored in the second volatile memory buffer such that the updated data of the data structure is accessible to both an application for the first non-volatile storage device and an application for the second non-volatile storage device. ### Claim 9 (depends on 8) The apparatus of claim 8, wherein the replication module is further configured to copy the data of the data structure over a network interface from the first non-volatile storage device to the second non-volatile storage device. ### Claim 10 (depends on 9) The apparatus of claim 9, wherein the replication module is further configured to copy the data of the data structure over the network interface independent of a processor of a host computing device. ### Claim 11 (depends on 10) The apparatus of claim 10, wherein the replication module is further configured to copy the data of the data structure over the network interface independent of a host volatile memory of the host computing device. ### Claim 12 (depends on 9) The apparatus of claim 9, wherein the network interface comprises one or more of a serial bus, a parallel bus, a peripheral component interconnect (PCI) interface, a PCI express (PCIe) interface, a universal serial bus (USB), an Ethernet interface, a small computer system interface (SCSI), and an advance technology attachment (ATA) interface. ### Claim 13 (depends on 8) The apparatus of claim 8, wherein the data structure is accessible as a file associated with a filename. ### Claim 14 (depends on 13) The apparatus of claim 13, wherein a first portion of the file is stored in the first and second volatile memory buffers. ### Claim 15 (depends on 14) The apparatus of claim 14, wherein a second portion of the file is stored on the first and second non-volatile storage devices. ### Claim 16 (depends on 8) The apparatus of claim 8, wherein the replication module is further configured to copy the data of the data structure at a byte granularity. ### Claim 17 (depends on 8) The apparatus of claim 8, wherein the data of the data structure comprises one or more updates to the data structure. ### Claim 18 An apparatus comprising: means for storing at least a portion of a data structure in a first volatile memory buffer within an isolation zone of a first non-volatile storage device, the first volatile memory buffer comprising a first auto-commit buffer of a first auto-commit memory that is configured to ensure that the data structure is preserved in the first non-volatile storage device in response to a trigger associated with the first auto-commit buffer; means for copying data of the at least a portion of the data structure stored in the first volatile memory buffer to a second volatile memory buffer within an isolation zone of a second non-volatile storage device such that both the first and second non-volatile storage devices independently ensure persistence of the data structure, the second volatile memory buffer comprising a second auto-commit buffer of a second auto-commit memory; means for receiving updated data for the at least a portion of the data structure stored in the first volatile memory buffer; and means for synchronizing, in response to the trigger associated with the first auto-commit buffer, the updated data of the at least a portion of the data structure stored in the first volatile memory buffer and the at least a portion of the data structure stored in the second volatile memory buffer such that the updated data of the data structure is accessible to both an application for the first non-volatile storage device and an application for the second non-volatile storage device.