Low Level Object Version Tracking Using Non-Volatile Memory Write Generations
AssigneeSanDisk Enterprise IP LLC
InventorsJames M. Bodwin, Darpan Dinker, Andrew D. Eckhardt, Carryl M. Ouye
Life of this patent
Estimating the term…
Abstract
A method for retrieving versioned data in a non-volatile memory is provided. The method includes: (1) receiving a read request for a data object, (2) in response to the request, determining, via an object table, whether one or more versions of the data object exist in memory, (3) in accordance with a determination that one or more versions exist in memory, obtaining, via the object table, a respective location where each of the one or more versions of the data object are stored, and (4) reading at least one of the one or more versions of the data object from the respective location into volatile memory.
Claims18
A method for retrieving versioned data in a non-volatile memory, the method comprising:
- receiving a read request for a data object;
- in response to the request, determining, via an object table, whether one or more versions of the data object exist in memory;
- in accordance with a determination that one or more versions exist in memory, obtaining, via the object table, a respective location where each of the one or more versions of the data object are stored;
- and
- reading at least one of the one or more versions of the data object from the respective location into volatile memory.
A system for retrieving versioned data, the system comprising:
- non-volatile memory configured to store one or more data objects;
- and
- one or more non-volatile memory controllers configured to:
- receive a read request for a data object;
- in response to the request, determine, via an object table, whether one or more versions of the data object exist in the non-volatile memory;
- in accordance with a determination that one or more versions exist in the non-volatile memory, obtain, via the object table, a respective location where each of the one or more versions of the data object are stored;
- and
- read at least one of the one or more versions of the data object from the respective location into volatile memory.
Dependencies are inferred from the claim text.