JP2022540750A - Memory management for computing devices - Google Patents

Abstract

In one embodiment, a method comprises allocating, by an operating system of a computing device, computer-implemented memory into a disposable portion and a durable portion; of the data files, indicating that the particular file is to be stored in the disposable portion of memory; and in response, one or more of the disposable portions of memory. identifying the occurrence of the computing condition; and, in response, one or more specific data files containing the specific data files as invalid for the computer-executable program. marking a page; receiving a request from a computer-executable program for a particular data file; and providing a notice that the program is invalid. [Selection drawing] Fig. 1

Description

The present disclosure relates generally to memory management for computing devices.

A mobile computing device, such as a smartphone, tablet computer, or laptop computer, may include functionality for determining the location, direction, or orientation of the device, such as a GPS receiver, compass, gyroscope, or accelerometer. . Such devices also include functionality for wireless communication, such as BLUETOOTH communication, near-field communication (NFC), or infrared (IR) communication, or communication with wireless local area networks (WLAN) or cellular telephone networks. obtain. Such devices may also include one or more cameras, scanners, touch screens, microphones, or speakers. Mobile computing devices may also run software applications, such as games, web browsers, or social networking applications. Social networking applications allow users to connect, communicate, and share information with other users within their social networks.

Mobile computing devices need to be power efficient and may need to support multiple applications that are active at the same time. Existing mobile platforms only have durable memory, which may not be able to be completely turned off when not in use. Furthermore, reallocation of memory used by computing devices is also more difficult because it is not known whether the data currently stored in memory is suitable for freeing.

This disclosure describes computing devices that support two types of memory: durable memory and disposable memory. APIs/libraries for the computing device's operating system can be used by applications to request storage of some types of data in disposable memory. For example, images (or other types of static content) may be well suited for disposable memory. Based on the memory allocation policy, the computing device either reallocates the disposable memory to other applications or turns off some memory banks containing the disposable memory when the application is inactive be able to. Moreover, rather than having the data in disposable memory swapped to disk, which can require a lot of power, the computing device discards the data stored by the disposable memory. and can notify upper layers (eg, API/library or application) that the memory is now invalid for the data stored in the discarded memory. This memory can then be reallocated. Data stored wholly or partially in reallocated pages will be marked as invalid. This notification mechanism allows higher layers to properly handle invalidated memory.

Inventive aspects of the subject matter described herein involve the allocation of computer-implemented memory into disposable and durable portions by the operating system of a computing device; receiving a designation indicator of a particular data file associated with the executable program indicating that the particular file should be stored in the disposable portion of memory; Storing the particular data file in one or more particular pages of the disposable portion of memory in response to receiving the display indicator and identifying the occurrence of a computing condition. and, in response to identifying the occurrence of the computing condition, marking one or more particular pages containing the particular data file as invalid for the computer-executable program; and in response to receiving the request, providing a notification to the computer-executable program that the particular data file is invalid for the computer-executable program. , can be embodied in a method.

Other embodiments of these aspects include corresponding systems, apparatus, and computer-readable media.

These and other embodiments can each optionally include one or more of the following features. For example, receiving from the computer-executable program an indication indicator of additional data files associated with the computer-executable program that the additional data files should be stored in a durable portion of memory; storing the additional data file in one or more additional pages of the durable portion of the memory in response to receiving the display indicator of the data file; identifying occurrence of the computing condition; maintaining one or more pages containing additional data files as valid for the computer-executable program in response to; A particular data file is an image file, a video file, or an audio file. The storage size of a particular data file is larger than the threshold size. Identifying the occurrence of the computing condition includes identifying an inactive state of the computer-executable program and, in response, determining one or more particular pages containing particular data files as invalid for the computer-executable program. and marking the Powering off a disposable portion of memory in response to identifying an inactive state of a computer executable program. Identifying the occurrence of the computing condition includes identifying further computer-executable program activations and, in response, determining one or more specific pages containing specific data files as invalid for the computer-executable program. and the further computer-executable program has a higher processing priority than the computer-executable program. In response to identifying activation of the additional computer-executable program, one or more specific pages of the disposable portion of memory are transferred to one or more additional data associated with the additional computer-executable program. To reallocate to a file.

storing the particular data file in one or more particular pages of the disposable portion of memory includes storing the particular data file in one particular page of the disposable portion of memory; Marking one or more specific pages containing specific data files as invalid for the computer-executable program refers to marking one specific page containing the specific data files as invalid for the computer-executable program. include. One particular page contains one or more other data files. Storing a particular data file in one or more particular pages of a disposable portion of memory may be performed on two pages of a disposable portion of memory such that a particular data file spans two particular pages of a disposable portion of memory. Marking one or more particular pages containing the particular data file as invalid for the computer-executable program includes storing the particular data file in the particular page; This includes marking two specific pages that contain data files of . The durable portion of memory includes a page table for one or more pages of the disposable portion of memory, and one or more specific pages containing specific data files as invalid for computer-executable programs. Marking includes modifying the page table for one or more particular pages. The computer-executable program is an augmented reality (AR) or virtual reality (VR) computer-executable program.

In some embodiments, a system comprising a processor having access to a memory medium storing instructions that are stored by an operating system of a computing device in computer-implemented memory that is disposable and durable. allocating to a portion and indicating from a computer-executable program that a particular file of a particular data file associated with the computer-executable program is to be stored in a disposable portion of memory receiving the indicator; storing the particular data file in one or more particular pages of the disposable portion of the memory in response to receiving the indication indicator of the particular data file; identifying the occurrence of the computing condition; and responsive to identifying the occurrence of the computing condition, marking one or more particular pages containing the particular data file as invalid for the computer-executable program. , receiving a request from a computer-executable program for a particular data file and, in response to receiving the request, telling the computer-executable program that the particular data file is invalid with respect to the computer-executable program A system is provided executable by a processor to provide a notification.

In some embodiments, the operation is from the computer-executable program to the additional data file associated with the computer-executable program that the additional data file should be stored in the durable portion of memory. receiving the display indicator; and storing the additional data file in one or more additional pages of the durable portion of memory in response to receiving the display indicator of the additional data file. and maintaining one or more pages containing additional data files as valid for the computer-executable program in response to identifying occurrence of the computing condition.

In some embodiments, the particular data file is an image file, video file, or audio file.

In some embodiments, the storage size of a particular data file is larger than the threshold size.

In some embodiments, identifying the occurrence of the computing condition includes identifying an inactive state of the computer-executable program and, in response, the computer-executable program including a particular data file as invalid. and marking one or more particular pages.

In some embodiments, the operations further include powering off the disposable portion of the memory in response to identifying an inactive state of the computer-executable program.

The embodiments disclosed herein are examples only, and the scope of the present disclosure is not limited thereto. Particular embodiments may include all, some, or none of the components, elements, features, functions, acts, or steps of the embodiments disclosed herein . Embodiments in accordance with the present invention are disclosed in the accompanying claims directed, inter alia, to methods, storage media, systems and computer program products, wherein any feature recited in one claim category, e.g. , may also be claimed in another claim category, e.g., the system. Dependencies or references in the appended claims are chosen for formal reasons only. However, subject matter arising from intentional reference (especially multiple subordination) to a previous claim may also be claimed, so that any combination of the claim and its features is disclosed and defined by the appended claims. Claims may be made regardless of any dependencies selected in scope. Claimable subject matter includes not only combinations of the features recited in the appended claims, but also any other combination of the features recited in the claims, wherein each feature recited in a claim comprises: It may be combined with any other feature or combination of features in the claims. Moreover, any of the embodiments and features described or shown herein may appear in a separate claim and/or in conjunction with any embodiment or feature described or shown herein or in an appended claim. may be claimed in any combination with any of the features of the scope of

1 illustrates an example computing environment for memory management of a computing device; FIG. 4 is an exemplary flow chart for memory management of a computing device; 1 illustrates an exemplary computer system; FIG.

FIG. 1 shows a computing system 100 for memory management of computing devices. The computing system 100 includes an operating system (OS) computing module 102, a memory module (or memory) 104, a page table database 106 (collectively referred to as computer executable program modules 108 or computer executable application modules 108). computer-executable program modules 108a, 108b). OS computing module 102 may include memory manager computing module 110 . Memory module 104 can include a disposable portion 112 and a durable portion 114 .

In some examples, disposable portion 112 and durable portion 114 are logical separations of memory 104 and are located within the same memory structure (eg, memory bank). In some examples, disposable portion 112 and durable portion 114 are physically separated into different memory structures (eg, memory banks).

OS computing module 102 may allocate memory module 104 into disposable portion 112 and durable portion 114 . In particular, OS computing module 102 ensures that data stored by disposable portion 112 of memory module 104 may be temporary, such as by deleting or removing such disposable data. Disposable portion 112 can be allocated so that it can be used or, in some cases, overridden. Disposable portion 112 can store data that is or can be reallocated by OS computing module 102 and/or memory manager computing module 110, further described herein. It may contain one or more (memory) pages 116 .

Similarly, OS computing module 102 is configured so that data stored by durable portion 114 of memory module 104 can be persistent, e.g., such durable data can be maintained. , the durable portion 114 can be allocated. Durable portion 114 can store data to be maintained by OS computing module 102 and/or memory manager computing module 110, described further herein. (Memory) pages 118 may be included.

In some examples, the OS computing module 102 configures the memory module 104 into a disposable portion 112 and a durable portion 114 in response to an event or request when the computing system 100 boots. can be assigned to

In some examples, memory modules 104, and in particular pages of memory modules 104, are discarded to define disposable portions 112 (and pages 116) and durable portions 114 (and pages 118). Possible (or durable) additional attributes may be associated. For example, attributes of memory module 104 may include attributes such as read and write, as well as disposable attributes (and/or durable attributes).

In some examples, durable portion 114 may include page table 106 for pages 116 of disposable portion 112 .

In some examples, computer-executable program module 108 may be an augmented reality computer-executable program, a virtual reality (VR) computer-executable program, or a mixed reality computer-executable program.

In some implementations, the memory manager computing module 110 determines that the data file 122a associated with the computer-executable program module 108a should be stored in the disposable portion 112 of the memory 104. An indicating indicator 120a can be received. For example, computer-executable program module 108a can indicate that data file 122a should be stored in disposable portion 122, eg, using an API provided to computer-executable program 108a. . In some examples, data files 122a may include image files, video files, or audio files. In some examples, the storage size of data file 122a is greater than the threshold size.

In some examples, memory manager computing module 110 receives display indicator 120a and data file 122a at substantially the same time from computer executable program module 108a (eg, during one communication cycle). be able to. In some examples, data file 122a includes display indicator 120a, ie, data file 122a may be marked with an attribute (eg, display indicator).

In some implementations, memory manager computing module 110 stores data file 122a in page 116 of disposable portion 112 of memory 104 in response to receiving display indicator 120a for data file 122a. In some examples, data file 122 a is stored within a single page 116 of disposable portion 112 of memory 104 . In some examples, data file 122 a is stored in two or more pages 116 of disposable portion 112 of memory 104 .

In some implementations, memory manager computing module 110 can identify the occurrence of computing condition 130 . In some examples, memory manager computing module 110 may receive an indication of computing conditions 130 automatically or in response to a request. For example, computing conditions 130 may include data that directs the occurrence of computing events, including metadata for such computing events and any associated data for such computing events. For example, identifying the occurrence of computing condition 130 may cause memory manager computing module 110 to identify an inactive state of computer-executable program module 108a (or receive an indication of an inactive state of computer-executable program module 108a). do). In particular, computer-executable program module 108a may enter a low-power idle mode, or inactive state. In some cases, the computer-executable program module 108a enters the inactive state when the computer-executable program module 108a has been inactive for greater than a threshold amount of time (eg, 5 minutes). be able to. To that end, the computer-executable program module 108a can provide such notification of the computing conditions 130 to the memory manager computing module 108a or another computing module monitoring the computer-executable program module 108a. A module may provide such notification of computing conditions 130 to memory manager computing module 108a.

For example, identifying the occurrence of a computing condition may include memory manager computing module 110 identifying activation of additional computer-executable program modules (or receiving an indication of activation of additional computer-executable program modules). can include In particular, computer-executable program module 108a may have a lower computing priority compared to further computer-executable program modules or compared to newly started computer-executable program modules. (Additional computer-executable program modules have a higher processing priority compared to computer-executable program module 108a). For example, additional computer-executable program modules may be running in the foreground, e.g., providing graphical user interface (GUI) elements in the foreground of the display interface of computing system 100, and the computer-executable program modules Module 108 a may be running in the background, eg, providing GUI elements in the background of the display interface of computing system 100 . As a result, the further computer-executable program module (running in the foreground) can have a higher priority compared to computer-executable program module 108a (running in the background). Computing modules that monitor the state of computer-executable program modules 108 can provide such notification of computing conditions 130 to memory manager computing module 108a.

In some examples, memory manager 110 executes computer-executable programs based on one or more computing parameters associated with each computer-executable program module 108 and/or the computing state of computer-executable program module 108 . The relative priority of modules 108 can be determined. Memory manager 110 determines the relative priority of computer-executable program modules 108 based on the state of computing system 100, for example, in light of computing parameters and/or computing states of computer-executable program modules 108. can do.

In some implementations, in response to identifying the occurrence of computing condition 130, memory manager computing module 110 marks page 116 containing data file 122a as invalid for computer-executable program module 108a. can be done. For example, the memory manager computing module 110 determines whether the disposable portion 112 of the memory 104 should be powered off, or the data files of the different computer-executable program modules described further herein. can be determined that it should be reallocated for

In some examples, when the occurrence of computing condition 130 includes an inactive state of computer-executable program module 108a, memory manager computing module 110 renders the page containing data file 122a invalid for computer-executable program module 108a. 116 can be marked. Specifically, the memory manager computing module 110 changes the power state of the disposable portion 112 of the memory 104 to an "off state," a "power "off state" or "low power state". Memory manager computing module 110 can invalidate data file 122 a when data file 122 a is stored by disposable portion 112 of memory 104 . In some examples, memory manager computing module 110 causes data files 122a to be stored by disposable portion 112 of memory 104 independently of action by computer-executable program module 108a (in response to computing condition 130). invalidates the data file 122a. That is, in some examples, computer-executable program module 108a may be used to describe computing conditions 130 and/or computer-executable program module 108a when data file 122a is stored by disposable portion 112 of memory 104. It has no control over invalidation of data file 122a.

In some examples, when occurrence of computing condition 130 includes identifying activation of a further computer-executable program, memory manager computing module 110 registers data file 122a as invalid for computer-executable program module 108a. One or more pages 116 can be marked that contain a . Specifically, in response to identifying activation of the additional computer-executable program module, memory manager computing module 110 copies one or more pages 116 containing data file 122a to the additional computer-executable program module. can be reallocated to additional data files associated with That is, memory manager computing module 110 can invalidate data file 122a and reallocate pages 116 of disposable portion 112 of memory 104 to additional computer-executable program modules. In some examples, memory manager computing module 110 causes data files 122a to be stored by disposable portion 112 of memory 104 independently of action by computer-executable program module 108a (in response to computing condition 130). When done, it invalidates data file 122a and reallocates page 116 to additional computer-executable program modules. That is, in some examples, computer-executable program module 108a may be used to describe computing conditions 130 and/or computer-executable program module 108a when data file 122a is stored by disposable portion 112 of memory 104. It has no control over invalidating data file 122a and/or reallocating pages 116 to further computer-executable program modules.

In some examples, data file 122a may be stored in one particular page 116 of disposable portion 112 of memory 104, as described above. To that end, memory manager computing module 110 may mark one particular page 116 containing data file 122a as invalid for computer-executable program module 108a. That is, the data file 122a is page aligned with the single page 116 and the memory manager computing module 110 invalidates the single page 116. FIG. In some cases, one particular page 116 includes data file 122a and additional data files or portions of additional data files (associated with computer-executable program module 108a or another computer-executable program module). and As such, both of the data files (data file 122a and the additional data file) are marked as invalid by memory manager computing module 110 .

In some examples, data file 122a may be stored in two particular pages 116 of disposable portion 112 of memory 104, as described above. To that end, memory manager computing module 110 may mark two particular pages 116 containing data file 122a as invalid for computer-executable program module 108a. That is, data file 122 a can span two pages 116 and memory manager computing module 110 invalidates both pages 116 . In some cases, one or both of the two pages 116 may include data file 122a and additional data files (associated with computer-executable program module 108a or another computer-executable program module) or additional data files. and a portion of As such, both of the data files (data file 122a and the additional data file) are marked as invalid by memory manager computing module 110 .

In some examples, as described above, durable portion 114 of memory 104 may include page table 106 for pages 116 of disposable portion 112 of memory 104 . To that end, when the memory manager computing module 110 marks a particular page 116 containing the data file 122a as invalid for the computer-executable program module 108a, the memory manager computing module 110 writes the page table for the particular page 116. 106 can be modified. For example, the memory manager computing module 110 removes entries associated with a particular page(s) 116 containing data file 122a, or deletes entries in the page table to invalidate such entries. 106 can be modified.

In some implementations, memory manager computing module 110 may later receive request 140a for data file 122a from computer-executable program module 108a. In response to request 140a, memory manager computing module 110a may provide computer-executable program module 108a with notification 142a indicating that data file 122a is invalid for computer-executable program module 108a. That is, notification 142a is a signal provided to computer-executable program module 108a indicating that page(s) 116 containing data file 122a is now invalid, i.e., memory allocation is no longer valid. can be

In some implementations, the memory manager computing module 110 controls the data file 122b associated with the computer-executable program module 108b that the data file 122b should be stored in the durable portion 114 of the memory 104. A display indicator 120b may be received that indicates the. For example, computer-executable program module 108b indicates that data file 122b should be stored in durable portion 114 of memory 104, eg, using an API provided to computer-executable program 108b. can do. In some examples, data files 122b may include image files, video files, or audio files. In some examples, memory manager computing module 110 receives display indicator 120b and data file 122b at substantially the same time from computer executable program module 108b (eg, during one communication cycle). be able to. In some examples, data file 122b includes display indicator 120b, ie, data file 122b may be marked with an attribute (eg, display indicator).

In some implementations, memory manager computing module 110 stores data file 122b in page 118 of durable portion 114 of memory 104 in response to receiving display indicator 120b for data file 122b. . In some examples, data file 122b is stored within a single page 118 of durable portion 114 of memory 104 . In some examples, data file 122 b is stored in two or more pages 118 of durable portion 114 of memory 104 . As described above, memory manager computing module 110 can identify the occurrence of computing condition 130 . For example, identifying the occurrence of computing condition 130 may cause memory manager computing module 110 to identify an inactive state of computer-executable program module 108a (or receive an indication of an inactive state of computer-executable program module 108a). do). For example, identifying occurrence of computing condition 130 includes memory manager 110 identifying activation of additional computer-executable program modules (or receiving an indication of activation of additional computer-executable program modules). be able to.

In some implementations, in response to identifying the occurrence of computing condition 130, memory manager computing module 110 maintains page 118 containing data file 122b as valid for computer-executable program module 108b. can be done. That is, because data file 122b is maintained in pages 118 in durable portion 114 of memory 104, occurrence of computing condition 130 does not affect data file 122b (eg, storage of data file 122b). do not have.

FIG. 2 illustrates an exemplary method 200 for memory management of a computing device. The method may begin at step 210 where the OS computing module 102 may allocate memory modules 104 into disposable portion 112 and durable portion 114 . At step 220, memory manager computing module 110 may receive display indicator 120a of data file 122a associated with computer-executable program module 108a. At step 230 , memory manager computing module 110 determines that display indicator 120 a indicates storage of data file 122 a in disposable portion 112 of memory 104 . At step 240 , memory manager computing module 110 stores data file 122 a in page 116 of disposable portion 112 of memory 104 . At step 250 , memory manager computing module 110 may identify the occurrence of computing condition 130 . At step 260, in response to identifying the occurrence of computing condition 130, memory manager computing module 110 may mark page 116 containing data file 122a as invalid for computer-executable program module 108a. At step 270, memory manager computing module 110 may receive request 140a for data file 122a from computer-executable program module 108a. At step 280, memory manager computing module 110 may determine that data file 122a is stored in a page marked as invalid. At step 290, memory manager computing module 110a may provide computer-executable program module 108a with notification 142a indicating that data file 122a is invalid for computer-executable program module 108a.

At step 292 , memory manager computing module 110 determines that display indicator 120 b indicates storage of data file 122 a in durable portion 114 of memory 104 . At step 294, memory manager computing module 110 stores data file 122b in page 118 of durable portion 114 of memory 104 in response to receiving display indicator 120b of data file 122b.

Particular embodiments may repeat one or more steps of the method of FIG. 2 where appropriate. Although this disclosure describes and depicts certain steps of the method of FIG. 2 as being performed in a particular order, this disclosure does not imply that any suitable steps of the method of FIG. 2 may be performed in any suitable order. intended to be Moreover, although this disclosure describes and illustrates an exemplary method for memory management of a computing device, including certain steps of the method of FIG. Any suitable method for memory management of a computing device is contemplated, including any suitable steps, which may include all, some, or none of the steps of . Furthermore, although this disclosure describes and shows particular components, devices, or systems for performing particular steps of the method of FIG. Any suitable combination of suitable components, devices or systems is contemplated.

FIG. 3 shows an exemplary computer system 300. As shown in FIG. In particular embodiments, one or more computer systems 300 implement one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems 300 provide the functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems 300 performs one or more steps of one or more methods described or illustrated herein, or It provides the functionality described or illustrated herein. Particular embodiments include one or more portions of one or more computer systems 300 . References herein to computer systems may encompass computing devices, and vice versa, where appropriate. Moreover, references to a computer system may encompass one or more computer systems, where appropriate.

This disclosure contemplates any suitable number of computer systems 300 . This disclosure contemplates computer system 300 taking any suitable physical form. By way of example and not limitation, computer system 300 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (eg, computer-on-module (COM) or system-on-module (SOM)). , desktop computer systems, laptop or notebook computer systems, interactive kiosks, mainframes, mesh computer systems, mobile phones, personal digital assistants (PDAs), servers, tablet computer systems, augmented/virtual reality devices, or any of these can be a combination of two or more of Where appropriate, computer system 300 may include one or more computer systems 300, be single or distributed, span multiple locations, span multiple machines, span multiple data centers, or It may reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 300 perform one or more steps of one or more methods described or illustrated herein without substantial spatial or temporal limitations. obtain. By way of example and not limitation, one or more computer systems 300 may perform, in real time or in batch mode, one or more steps of one or more methods described or illustrated herein. One or more computer systems 300 may perform one or more steps of one or more methods described or illustrated herein at different times or at different locations, where appropriate.

In particular embodiments, computer system 300 includes processor 302 , memory 304 , storage 306 , input/output (I/O) interface 308 , communication interface 310 and bus 312 . Although this disclosure describes and illustrates a particular computer system with a particular number of particular components in a particular arrangement, this disclosure may be applied to any suitable number of any suitable configuration in any suitable arrangement. Any suitable computer system having the components is contemplated.

In particular embodiments, processor 302 includes hardware for executing instructions, such as those that make up a computer program. By way of example and not limitation, to execute instructions, processor 302 retrieves (or fetches) instructions from internal registers, internal cache, memory 304, or storage 306, decodes and executes those instructions, and then , internal registers, internal cache, memory 304 , or storage 306 . In particular embodiments, processor 302 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor 302 including any suitable number of any suitable internal caches, where appropriate. By way of example and not limitation, processor 302 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction cache may be copies of instructions in memory 304 or storage 306, and the instruction cache may speed up retrieval of those instructions by processor 302. FIG. Data in the data cache may be a copy of the data in memory 304 or storage 306 on which instructions executing in processor 302 operate, for access by subsequent instructions executing in processor 302, or in memory 304 or storage 306. It may be the result of a previous instruction executed in processor 302 to write, or other suitable data. A data cache may speed up read or write operations by processor 302 . A TLB may speed up virtual-address translation for processor 302 . In particular embodiments, processor 302 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor 302 including any suitable number of any suitable internal registers, where appropriate. Processor 302 may include one or more arithmetic logic units (ALUs), be a multi-core processor, or include one or more processors 302, where appropriate. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.

In particular embodiments, memory 304 includes main memory for storing instructions for processor 302 to execute or data on which processor 302 operates. By way of example, and not limitation, computer system 300 may load instructions into memory 304 from storage 306 or another source (eg, another computer system 300). Processor 302 may then load the instructions from memory 304 into an internal register or internal cache. To execute instructions, processor 302 may retrieve instructions from internal registers or an internal cache and decode those instructions. During or after execution of an instruction, processor 302 may write one or more results (which may be intermediate or final results) to an internal register or internal cache. Processor 302 may then write one or more of those results to memory 304 . In particular embodiments, processor 302 executes only instructions in one or more internal registers or internal caches, or in memory 304 (as opposed to storage 306 or elsewhere), and one or more It operates only on data in internal registers or caches, or in memory 304 (as opposed to storage 306 or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor 302 to memory 304 . Bus 312 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor 302 and memory 304 and facilitate accesses to memory 304 requested by processor 302 . In particular embodiments, memory 304 includes random access memory (RAM). This RAM may be volatile memory, where appropriate. Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM. Memory 304 may include one or more memories 304, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.

In particular embodiments, storage 306 includes mass storage for data or instructions. By way of example and not limitation, storage 306 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or two or more of these. More combinations may be included. Storage 306 may include removable or non-removable (or non-removable) media, where appropriate. Storage 306 may be internal or external to computer system 300, where appropriate. In particular embodiments, storage 306 is non-volatile solid-state memory. In particular embodiments, storage 306 includes read-only memory (ROM). Where appropriate, this ROM may be mask programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically erasable programmable ROM (EAROM), or flash memory. can be a combination of two or more of This disclosure contemplates mass storage 306 taking any suitable physical form. Storage 306 may include one or more storage control units that facilitate communication between processor 302 and storage 306, where appropriate. Storage 306 may include one or more storages 306, where appropriate. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 308 is hardware, software, or software that provides one or more interfaces for communication between computer system 300 and one or more I/O devices. Including both. Computer system 300 may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between people and computer system 300 . By way of example and not limitation, I/O devices include keyboards, keypads, microphones, monitors, mice, printers, scanners, speakers, still cameras, styluses, tablets, touch screens, trackballs, video cameras, and other suitable devices. I/O devices, or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 308 for those I/O devices. Where appropriate, I/O interface 308 may include one or more device or software drivers that enable processor 302 to drive one or more of these I/O devices. I/O interfaces 308 may include one or more I/O interfaces 308, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.

In particular embodiments, communication interface 310 is a communication interface for communication (eg, packet-based communication, etc.) between computer system 300 and one or more other computer systems 300 or one or more networks. Includes hardware, software, or both that provide one or more interfaces. By way of example and not limitation, communication interface 310 may be a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network, or a wireless NIC for communicating with a wireless network such as a WI-FI network. (WNIC) or wireless adapter. This disclosure contemplates any suitable network and any suitable communication interface 310 for that network. By way of example and not limitation, computer system 300 may be connected to one or more of an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or the Internet. or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. By way of example, computer system 300 may be connected to a wireless PAN (WPAN) (eg, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (eg, a Global System for Mobile Communications (GSM) network). , or other suitable wireless network, or a combination of two or more of these. Computer system 300 may include any suitable communication interface 310 for any of these networks, where appropriate. Communication interface 310 may include one or more communication interfaces 310, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface.

In particular embodiments, bus 312 includes hardware, software, or both coupling components of computer system 300 to each other. By way of example and not limitation, bus 312 may be an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HYPERTRANSPORT (HT) interconnect, an industry Standard Architecture (ISA) Bus, INFINIBAND Interconnect, Low Pin Count (LPC) Bus, Memory Bus, Micro Channel Architecture (MCA) Bus, Peripheral Component Interconnect (PCI) Bus, PCI-Express (PCIe) Bus, Serial Advanced Technology an attachment (SATA) bus, a Video Electronics Standards Board Local (VLB) bus, or another suitable bus, or a combination of two or more of these. Bus 312 may include one or more buses 312, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.

As used herein, one or more computer-readable, non-transitory storage media refers to one or more semiconductor devices (eg, such as field programmable gate arrays (FPGAs) or application specific ICs (ASICs)), as appropriate. base or other integrated circuit (IC), hard disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic including tapes, solid state drives (SSDs), RAM drives, secure digital cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more thereof obtain. Computer-readable non-transitory storage media may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.

As used herein, "or" is inclusive and not exclusive, unless explicitly indicated otherwise or unless otherwise indicated by context. Thus, as used herein, "A or B" means "A, B, or both," unless expressly indicated otherwise or unless indicated otherwise by context. Moreover, “and” is both joint and separate unless clearly indicated otherwise or indicated otherwise by context. Thus, as used herein, "A and B" means "jointly or individually, A and B," unless expressly indicated otherwise or by context.

The scope of the present disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments described or shown herein that a person skilled in the art would comprehend. The scope of this disclosure is not limited to the exemplary embodiments described or shown herein. Moreover, although this disclosure describes and presents each embodiment herein as including particular components, elements, features, functions, acts, or steps, any of these embodiments It may include any combination or permutation of any of the components, elements, features, functions, acts, or steps described or shown anywhere herein that a person skilled in the art would understand. In addition, the A reference in an appended claim to a device or system or component of a device or system operable to or operable to implement means that the device, system, or component is operable to To the extent that the device, system, component or particular function thereof is adapted, arranged, capable, configured, enabled, operable or operable , includes its devices, systems, components, whether activated, turned on, or unlocked. Further, although this disclosure describes or shows certain embodiments as providing certain advantages, certain embodiments may provide none, some, or all of these advantages. , or all.

Claims (15)

allocating computer-implemented memory into disposable and durable portions by an operating system of a computing device;
receiving from a computer-executable program a display indicator of a particular data file associated with said computer-executable program indicating that said particular file should be stored in said disposable portion of said memory; and
Storing the particular data file in one or more particular pages of the disposable portion of the memory in response to receiving the indication indicator of the particular data file;
identifying occurrences of computing conditions;
marking the one or more specific pages containing the specific data file as invalid for the computer-executable program in response to identifying the occurrence of the computing condition;
receiving a request for the particular data file from the computer-executable program;
and responsive to receiving the request, providing a notification to the computer-executable program that the particular data file is invalid for the computer-executable program. receiving from the computer-executable program an indication indicator of an additional data file associated with the computer-executable program that the additional data file should be stored in the durable portion of the memory and
Storing the additional data file in one or more additional pages of the durable portion of the memory in response to receiving the indication indicator of the additional data file;
maintaining said one or more pages containing said additional data files as valid for said computer-executable program in response to identifying said occurrence of said computing condition. A computer-implemented method as described in . 3. The computer-implemented method of claim 1 or 2, wherein the particular data file is an image file, video file, or audio file. 4. The computer-implemented method of any one of claims 1-3, wherein the storage size of the particular data file is greater than a threshold size. identifying said occurrence of said computing condition includes identifying an inactive state of said computer-executable program; or marking a plurality of specific pages, preferably powering off said disposable portion of said memory in response to identifying said inactive state of said computer executable program. 5. The computer-implemented method of any one of claims 1-4, further comprising: wherein identifying said occurrence of said computing condition identifies activation of a further computer-executable program; and, in response, said one or and marking a plurality of specific pages, wherein said further computer-executable program has a higher processing priority than said computer-executable program, preferably said activation of said further computer-executable program. In response to identifying, reallocate the one or more specific pages of the disposable portion of the memory to one or more additional data files associated with the additional computer-executable program. 6. The computer-implemented method of any one of claims 1-5, further comprising: storing the particular data file in the one or more particular pages of the disposable portion of the memory; storing the particular data file in one particular page of the disposable portion of the memory; and marking the one or more specific pages containing the specific data file as invalid with respect to the computer-executable program comprises storing the specific data file as invalid with respect to the computer-executable program. and preferably said one specific page contains one or more other data files. computer-implemented method. Storing the particular data file in the one or more particular pages of the disposable portion of the memory causes the particular data file to span two particular pages of the memory. storing the particular data file in the two particular pages of the disposable portion, and marking the one or more particular pages containing the particular data file as invalid with respect to the computer-executable program. 8. The computer-implemented method of any one of claims 1-7, wherein doing comprises marking the two particular pages containing the particular data file as invalid with respect to the computer-executable program. said durable portion of said memory including a page table for said one or more pages of said disposable portion of said memory and including said particular data file as invalid for said computer-executable program; 9. The computer implementation of any one of claims 1-8, wherein marking one or more particular pages comprises modifying the page table for the one or more particular pages. Method. 10. The computer-implemented method of any one of claims 1-9, wherein the computer-executable program is an augmented reality (AR) or virtual reality (VR) computer-executable program. A system comprising a processor having access to a memory medium storing instructions, the instructions comprising:
allocating computer-implemented memory into disposable and durable portions by an operating system of a computing device;
receiving from a computer-executable program a display indicator of a particular data file associated with said computer-executable program indicating that said particular file should be stored in said disposable portion of said memory; and
Storing the particular data file in one or more particular pages of the disposable portion of the memory in response to receiving the indication indicator of the particular data file;
identifying occurrences of computing conditions;
marking the one or more specific pages containing the specific data file as invalid for the computer-executable program in response to identifying the occurrence of the computing condition;
receiving a request for the particular data file from the computer-executable program;
and responsive to receiving the request, providing a notification to the computer-executable program that the particular data file is invalid for the computer-executable program. there is a system. the behavior is
receiving from the computer-executable program an indication indicator of an additional data file associated with the computer-executable program that the additional data file should be stored in the durable portion of the memory and
Storing the additional data file in one or more additional pages of the durable portion of the memory in response to receiving the indication indicator of the additional data file;
and maintaining the one or more pages containing the additional data files as valid for the computer-executable program in response to identifying the occurrence of the computing condition. The system described in . 13. A method according to claim 11 or 12, wherein said specific data file is an image file, video file or audio file and/or preferably the storage size of said specific data file is larger than a threshold size. system. identifying said occurrence of said computing condition includes identifying an inactive state of said computer-executable program; or marking a plurality of specific pages, and/or preferably said discardable of said memory in response to said action identifying said inactive state of said computer-executable program. 14. The system of any one of claims 11 to 13, further comprising powering off a portion. 1. A non-transitory computer-readable medium storing software containing instructions executable by one or more computers, said instructions, upon such execution, causing said one or more computers to:
allocating computer-implemented memory into disposable and durable portions by an operating system of a computing device;
receiving from a computer-executable program a display indicator of a particular data file associated with said computer-executable program indicating that said particular file should be stored in said disposable portion of said memory; and
Storing the particular data file in one or more particular pages of the disposable portion of the memory in response to receiving the indication indicator of the particular data file;
identifying occurrences of computing conditions;
marking the one or more specific pages containing the specific data file as invalid for the computer-executable program in response to identifying the occurrence of the computing condition;
receiving a request for the particular data file from the computer-executable program;
responsive to receiving the request, causing the computer-executable program to perform an action including providing notification that the particular data file is invalid for the computer-executable program. computer readable medium.

Images