Purgeable memory mapped files

Patent metadata

Field	Value
Publication number	US-2020105331-A1
Application number	US-201916522578-A
Country	US
Kind code	A1
Filing date	Jul 25, 2019
Priority date	Sep 28, 2018
Publication date	Apr 2, 2020
Grant date	—

Abstract

A device implementing purgeable memory mapped files includes at least one processor configured to receive a first request to store a first data object in volatile memory in association with a copy of the first data object stored in non-volatile memory, the first request indicating to lock the copy in the non-volatile memory. The processor is further configured to provide for storing the first data object in the volatile memory, and lock the copy stored in the non-volatile memory. The processor is further configured to receive a second request associated with clearing a portion of the non-volatile memory, provide an indication that a second data object is available for deletion from the non-volatile memory when the first data object is locked, and provide an indication that the first data object is available for deletion from the non-volatile memory when the first data object has been unlocked.

First claim

What is claimed is:

1 . A method, comprising:
receiving, from an application, a first request to store a first data object in volatile memory in association with a copy of the first data object stored in non-volatile memory, the first request indicating to lock the copy stored in the non-volatile memory; responsive to receiving the first request,
providing for storing the first data object in the volatile memory, and
locking the copy stored in the non-volatile memory;
receiving a second request associated with clearing a portion of the non-volatile memory; and responsive to receiving the second request,
providing an indication that a second data object is available for deletion from the non-volatile memory when the first data object is locked in the non-volatile memory, and
providing an indication that the first data object is available for deletion from the non-volatile memory when the first data object has been unlocked in the non-volatile memory.

2 . The method of claim 1 , further comprising:
receiving, from the application, a third request to retrieve the first data object; and responsive to receiving the third request,
retrieving, in accordance with a determination that the first data object is stored in the volatile memory, the first data object from the volatile memory, and
retrieving, in accordance with a determination that the first data object is not included in the volatile memory, the first data object from the non-volatile memory.

3 . The method of claim 1 , further comprising:
receiving, from the application, a third request to retrieve the first data object; and responsive to receiving the third request, providing, to the application, an indication that the first data object is not available.

4 . The method of claim 1 , wherein the second request is associated with an amount of space remaining in the non-volatile memory.

5 . The method of claim 1 , wherein the second request is a request for at least one of freeing up memory, storing data in the portion of the non-volatile memory, or releasing memory held by an application that has terminated.

6 . The method of claim 1 , wherein the copy of the first data object is stored in the non-volatile memory prior to receiving the first request.

7 . The method of claim 1 , wherein the copy of the first data object is not stored in the non-volatile memory prior to receiving the first request, the method further comprising:
responsive to receiving the first request, providing for storing the copy in the non-volatile memory.

8 . The method of claim 1 , wherein locking the copy comprises storing an indication to lock the copy in the non-volatile memory.

9 . A device, comprising:
at least one processor; and a memory including instructions that, when executed by the at least one processor, cause the at least one processor to:
receive, from an application, a first request to store a first data object in volatile memory in association with a copy of the first data object stored in non-volatile memory, the first request indicating to lock the copy stored in the non-volatile memory;
responsive to receiving the first request,
provide for storing the first data object in the volatile memory, and
store an indication to lock the copy stored in the non-volatile memory;

receive a second request associated with clearing a portion of the non-volatile memory; and
responsive to receiving the second request,
provide an indication that a second data object is available for deletion from the non-volatile memory when the first data object is locked in the non-volatile memory, and
provide an indication that the first data object is available for deletion from the non-volatile memory when the first data object has been unlocked in the non-volatile memory.

10 . The device of claim 9 , wherein the instructions further cause the at least one processor to:
receive, from the application, a third request to retrieve the first data object; and responsive to receiving the third request,
retrieve, in accordance with a determination that the first data object is not included in the volatile memory, the first data object from the non-volatile memory, and
retrieve, in accordance with a determination that the first data object is stored in the volatile memory, the first data object from the volatile memory.

11 . The device of claim 9 , wherein the instructions further cause the at least one processor to:
receive, from the application, a third request to retrieve the first data object; and responsive to receiving the third request, provide, to the application, an indication that the first data object is not available.

12 . The device of claim 9 , wherein the second request is associated with an amount of space remaining in the non-volatile memory.

13 . The device of claim 9 , wherein the second request is a request for at least one of freeing up memory, storing data in the portion of the non-volatile memory, or releasing memory held by an application that has terminated.

14 . The device of claim 9 , wherein the copy of the first data object is stored in the non-volatile memory prior to receiving the first request.

15 . The device of claim 9 , wherein the copy of the first data object is not stored in the non-volatile memory prior to receiving the first request, and
wherein the instructions further cause the at least one processor to, responsive to receiving the first request, provide for storing the copy in the non-volatile memory.

16 . A computer program product comprising code stored in a tangible computer-readable storage medium, the code comprising:
code to receive, from an application, a first request to store a first data object in a first type of memory in association with a copy of the first data object stored in a second type of memory; code to, responsive to receiving the first request, provide for storing the first data object in the first type of memory; code to lock a copy of the first data object stored in the second type of memory; code to receive a second request associated with clearing a portion of the second type of memory; and code to, responsive to receiving the second request,
provide an indication that a second data object is available for deletion from the second type of memory when the first data object is locked in the second type of memory, and
provide an indication that the first data object is available for deletion from the second type of memory when the first data object has been unlocked in the second type of memory.

17 . The computer program product of claim 16 , wherein the locking is performed in response to receiving the first request, and
wherein the first request indicates to lock the copy stored in the second type of memory.

18 . The computer program product of claim 16 , wherein the locking is performed in response to receiving an indication to lock the copy stored in the second type of memory, and
wherein the indication is sent separate from the first request.

19 . The computer program product of claim 16 , wherein providing the indication causes the second data object to be deleted from the second type of memory.

20 . The computer program product of claim 16 , the code further comprising:
code to receive, from the application, a third request to retrieve the first data object; and code to, responsive to receiving the third request,
retrieve, in accordance with a determination that the first data object is not included in the first type of memory

Assignees

• Apple Inc

Inventors

• Pauley Mark A

Classifications

• G11C7/10

  Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers · CPC title

• G11C11/005 Primary

  comprising combined but independently operative RAM-ROM, RAM-PROM, RAM-EPROM cells · CPC title

• G06F3/0643

  Management of files · CPC title

• G11C11/409

  Read-write [R-W] circuits · CPC title

• G11C11/4072 Primary

  Circuits for initialization, powering up or down, clearing memory or presetting · CPC title