# US 2018/0322067 A1 · Persistent virtual address spaces

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0322067 A1
- Document ID: US20180322067A1
- Status: Published application
- Kind: A1
- Application number: 15/774,233
- Filed: 2016-01-29
- Published: 2018-11-08
- Earliest claimed: 2016-01-29
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Izzat El Hajj; Alexander Merritt; Gerd Zellweger; Dejan S. Milojicic
- Web page: https://patentgrep.com/patent/US20180322067A1

## CPC

- G06F 12/109: for multiple virtual address spaces, e.g. segmentation (G06F12/1036 takes precedence)
- G06F 9/4493: {Object persistence}
- G06F 12/0238: {Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory}
- G06F 2212/1016: Performance improvement
- G06F 2212/1032: Reliability improvement, data loss prevention, degraded operation etc
- G06F 2212/502: using adaptive policy
- G06F 2212/657: Virtual address space management
- G06F 2212/7202: Allocation control and policies
- G06F 2212/7207: management of metadata or control data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Example implementations relate to persistent virtual address spaces. In one example, persistent virtual address spaces can employ a non-transitory processor readable medium including instructions to receive a whole data structure of a virtual address space (VAS) associated with a process, where the whole data structure includes data and metadata of the VAS, and store the data and the metadata of the VAS in a non-volatile memory to form a persistent VAS (PVAS).

## Claims

### Claim 1

A non-transitory processor readable medium including instructions to form a persistent virtual address space, wherein the instructions when executed by a processor cause the processor to:
receive a whole data structure of a virtual address space (VAS) associated with a process, wherein the whole data structure includes data and metadata of the VAS; and
store the data and the metadata of the VAS in a non-volatile memory to form a persistent VAS (PVAS).

### Claim 2 (depends on 1)

The medium of claim 1, wherein the instructions to receive include instructions to receive metadata that includes virtual address mappings of the process to a page.

### Claim 3 (depends on 1)

The medium of claim 1, including instructions to store the PVAS along with a plurality of PVAS to form a persistent store.

### Claim 4 (depends on 1)

The medium of claim 1, including instructions to disassociate the VAS from the process.

### Claim 5 (depends on 4)

The medium of claim 4, including instructions to maintain the stored data and the stored metadata in the PVAS in response to disassociation of the VAS from the process.

### Claim 6 (depends on 5)

The medium of claim 5, including instructions to use the stored data and the stored metadata to associate a process with the PVAS.

### Claim 7 (depends on 1)

The medium of claim 1, wherein the instructions to receive include instructions to receive the whole data structure of the VAS that includes the data and the metadata of the VAS from volatile memory.

### Claim 8

A device comprising:
a non-volatile memory;
a process executing on a processor;
a virtual memory system including a plurality of virtual address spaces, wherein a virtual address space (VAS) of the plurality of VASs is associated with the process; and
a non-transitory processor readable medium including instructions executable by the processor to store a whole data structure of the VAS in the non-volatile memory to form a PVAS maintained in the non-volatile memory in response to powering off the device.

### Claim 9 (depends on 8)

The device of claim 8, wherein the PVAS is included in a plurality of PVASs, wherein each of the plurality of PVASs includes a respective whole data structure of a VAS that remains in the non-volatile memory across a system boot.

### Claim 10 (depends on 9)

The device of claim 9, including instructions to delete a PVAS of the plurality of PVASs in response to the PVAS reaching a predetermined threshold time.

### Claim 11 (depends on 8)

The device of claim 8, including instructions to deduplicate a VAS of the plurality of VASs.

### Claim 12 (depends on 8)

The device of claim 8, wherein the whole data structure includes pages, translation structures, data, and description information of the VAS.

### Claim 13

A method comprising:
storing data and metadata of a virtual address space (VAS) associated with a first process of a device in non-volatile memory to form a PVAS;
disassociating the VAS from the first process;
maintaining the stored data and the stored metadata in the PVAS across a system boot of the device; and
associating a VAS with a process using the stored data and the stored metadata maintained in the PVAS.

### Claim 14 (depends on 13)

The method of claim 13, wherein associating comprises re-associating the VAS with the first process using the stored data and the stored metadata.

### Claim 15 (depends on 13)

The method of claim 13, wherein associating includes associating the VAS with a second process using the stored data and the stored metadata, and wherein the second process is different than the first process.
