WO2012159394A1

WO2012159394A1 - Method and apparatus for managing mobile device memory

Info

Publication number: WO2012159394A1
Application number: PCT/CN2011/079602
Authority: WO
Inventors: 古幼鹏; 徐立锋; 王巍; 胡炜
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-05-23
Filing date: 2011-09-14
Publication date: 2012-11-29
Also published as: CN102226894A; CN106843758A

Abstract

A method and apparatus for managing a mobile device memory. The method comprises: searching for at least one application being independent from an appointed application and conforming to a predetermined algorithm; using the found application as an application to be exchanged; and performing memory exchange according to the application to be exchanged. While the memory exchange is performed, this solution not only considers the search for the predetermined algorithm of the application to be exchanged, but also considers the dependence between applications. This solution eliminates ineffective memory exchange and improves the user experience of using a device.

Description

Mobile device memory management method and device

The present invention relates to memory management, and in particular, to a mobile device memory management method and apparatus. Background technique

With the advent of 3G and smart phones, there are more and more applications on mobile devices such as mobile phones. Mobile devices such as mobile phones use multi-tasking operating systems and can run multiple tasks at the same time. In order to improve the multi-tasking user experience, mobile devices such as mobile phones are equipped with large-capacity memory. However, the increase in memory capacity is limited by cost, power consumption, volume, and the like. Therefore, how to reduce memory usage in multitasking becomes an urgent problem to be solved.

Memory swap is a widely used method for reducing memory usage on PCs and servers. Its basic principle is: When the system is out of memory, some content in the memory is exchanged to the external memory to free up the memory space; when the system needs to run to the content that is exchanged to the external storage, it is exchanged to the external memory. The contents of the content are swapped into memory again; if there is insufficient memory in the process, another exchange process will be involved. Thus, the effective memory space of the system is the sum of the actual memory size plus the space on the external storage that can be used to store the exchanged content. With memory swapping, you can achieve more memory with less memory. Currently, the memory exchange method on PCs and servers is basically implemented as a basic function of the operating system (ie, virtual memory management) in the kernel of the operating system, which uses the LRU (Least Recently Use) algorithm. The content that has not been used for the longest time is preferentially exchanged and exchanged in the smallest unit of memory pages. The memory page is the basic unit of operating system management memory. The size of a memory page of a 32-bit Linux operating system is generally 4 KB.

However, the memory exchange methods used on PCs and servers have the following problems:

1) When swapping out memory pages that have not been used for the longest time, it is possible that the current The running application will use the memory page that has just been swapped out, so the contents of the memory page that is partially exchanged are immediately exchanged into the memory; it should be understood that the swap memory page referred to in this document refers to the exchange. The contents of the memory page;

2) In order to improve the memory usage, the operating system will choose to exchange memory pages as little as possible every time. Therefore, the currently running application may run out of memory during normal operation, and the system will perform memory swapping. In order to let the application run normally.

These two problems cause invalid memory swaps and memory swaps to be too frequent, and the system cannot perform any other operations while memory swapping is in progress. As a result, excessive and frequent memory swaps can slow down applications, run unsmoothly, and cause short pauses from time to time, which can greatly reduce the user experience. Due to the strong CPU performance of PCs and servers, this slower operation and less smooth operation have a relatively minor impact on the user experience, while the CPU performance of mobile devices such as mobile phones is relatively weak, slower and less fluent on the user experience. It will be obvious, resulting in a poor user experience. For this reason, memory swapping is not used on mobile devices such as mobile phones to reduce memory usage. Summary of the invention

The main technical problem to be solved by the present invention is to provide a method and device for memory management in a mobile device, which reduces the memory usage through memory exchange while minimizing the user experience.

According to an embodiment of the present invention, a mobile device memory management method is provided, including: searching for at least one application that is not dependent on a specified application and conforms to a predetermined algorithm as an application to be exchanged; according to the to-be-exchanged The application performs memory swap processing.

Further, the step of searching for at least one application that is not dependent on the specified application and conforms to the predetermined algorithm as the application to be exchanged includes: searching for an application that conforms to the predetermined algorithm from the currently running application; The application that meets the predetermined algorithm finds an application that has no dependencies on the specified application and uses it as the application to be exchanged. In an embodiment, the step of performing a memory swap process according to the application to be exchanged includes: selecting an application to be exchanged, and matching a memory page of the process corresponding to the predetermined algorithm in the process corresponding to the selected application Switching to the external memory; determining whether the sum of the amount of memory occupied by the swapped memory page and the current available memory amount of the system is greater than or equal to a preset threshold; if not, proceeding to select one of the applications to be exchanged One step.

In another embodiment, the step of performing a memory swap process according to the application to be exchanged includes: selecting one of the applications to be exchanged, marking the selected application; determining that the marked application corresponds to Whether the sum of the amount of memory occupied by the memory page that meets the predetermined algorithm in the process and the current amount of available memory of the system is greater than or equal to a preset threshold; if not, proceeding to perform the step of selecting one of the applications to be exchanged; , the memory pages that meet the predetermined algorithm in the processes corresponding to all the marked applications are exchanged into the external memory.

In still another embodiment, the page of performing memory swap processing is exchanged to the external memory according to the application to be exchanged.

Preferably, before the step of searching for at least one application that is not dependent on the specified application and conforms to the predetermined algorithm as the application to be exchanged, the method further includes: determining whether the current available memory amount of the system is greater than or equal to Setting a threshold; if less than the preset threshold, performing the searching for an application that is not dependent on the specified application and conforming to the predetermined algorithm as an application step to be exchanged; otherwise, no processing is performed.

Preferably, the application that conforms to the predetermined algorithm includes an application that the memory page to which the process corresponding to the application belongs is least recently used by the CPU.

Preferably, after the step of performing the memory swap process according to the application to be exchanged, the method further comprises: executing a normal application startup process to start the specified application. According to another embodiment of the present invention, a mobile device memory management apparatus is provided, including: an application management and control module, configured to search for at least one application that is not dependent on a specified application and conforms to a predetermined algorithm as to be exchanged The memory switching module is configured to exchange, according to the indication of the application management and control module, a memory page that meets a predetermined algorithm in a process corresponding to the application to be exchanged into the external memory.

Further, the application program conforming to the predetermined algorithm includes an application program whose memory page belongs to the process corresponding to the application is least used by the CPU.

The invention has the beneficial effects that: in the memory exchange, both the application to be exchanged according to a predetermined algorithm is considered, and the dependency between the applications is taken into consideration, thereby eliminating invalid memory exchange and improving the user experience of using the device. sense. In one embodiment, the relationship between the number of memory pages exchanged at a time and the current maximum memory usage of the system is also considered, thereby solving the problem of too frequent memory exchange and reducing the frequency of memory exchange; in another embodiment, before starting the program The memory exchange is completed to ensure that there is no memory exchange during the running of the application, thus eliminating the impact of memory swapping on the running process of the application. DRAWINGS

1 is a schematic structural diagram of a mobile device memory management apparatus according to an embodiment of the present invention; FIG. 2 is a schematic flowchart of a mobile device memory management method according to an embodiment of the present invention; FIG. 3 is a flow chart of a mobile device memory management method according to Embodiment 2 of the present invention; FIG. 4 is a schematic flowchart of a memory management method for a mobile device according to Embodiment 3 of the present invention; FIG. 5 is a schematic flowchart of a method for managing a memory of a mobile device according to Embodiment 4 of the present invention; FIG. 7 is a schematic flowchart of a method for managing a memory of a mobile device according to Embodiment 6 of the present invention; FIG. 8 is a schematic structural diagram of a memory management device applied to an Android mobile phone according to an embodiment of the present invention;

FIG. 9 is a schematic flowchart of a memory management method in an Android mobile phone corresponding to FIG. 8. detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

The design idea of the embodiment of the present invention is: 1) When selecting a memory page to be exchanged, consider using a predetermined algorithm to select an application, and also considering whether an application to be run may use the selected application, and only satisfy The memory pages of the two conditions (the memory page conforms to the predetermined algorithm and the application corresponding to the memory page has no dependencies on the application to be run) are selected and exchanged; 2) the number of memory pages exchanged is equal to the number of memory pages to be run. The maximum possible memory usage of the application; 3) The memory swap is completed before starting the application that will run. Among them, the idea point 1) eliminates the invalid memory exchange, the idea point 2) reduces the memory exchange frequency to only 1 time, the thought point 3) guarantees that there is no memory exchange during the application running, thus eliminating the memory exchange on the application running process Excuse me. In one embodiment, by combining these three points, it is possible to use both memory swapping to reduce memory usage without slowing down the speed and fluency of the application, and eliminating the traditional memory switching technology on mobile devices such as mobile phones. Disadvantages.

As shown in FIG. 1, a memory management device in a mobile device according to an embodiment of the present invention includes: an application management and control module and a memory switching module. The application management and control module is configured to search for at least one application that is not dependent on the specified application and meets a predetermined algorithm as the application to be exchanged; and the memory switching module is configured to manage and control according to the application. The page is swapped to the external memory. In one embodiment, the memory is RAM (random access memory) and the external memory is FLASH.

An embodiment of the present invention provides a memory management method based on the foregoing memory management apparatus, including: searching for at least one application that is not dependent on a specified application and conforms to a predetermined algorithm as an application to be exchanged; according to the application to be exchanged Perform memory swap processing.

In one embodiment, the predetermined algorithm adopts a least recently used (LRU) algorithm, that is, in this embodiment, the application that conforms to the predetermined algorithm is within the process to which the application corresponds. An application that has been recently used by the CPU at least is stored; other algorithms may be used in other embodiments, and the present invention is not limited to the LRU.

In an embodiment, the step of searching for at least one application that is not dependent on the specified application and conforms to the predetermined algorithm as the application to be exchanged includes: searching for an application that conforms to the predetermined algorithm from the currently running application Find an application that is not dependent on the specified application from the found application that matches the predetermined algorithm, and use it as the application to be exchanged. For this step, an exemplary method is: finding an application that conforms to a predetermined algorithm; determining whether there is a dependency between the found application and the specified application; if there is a dependency, re-finding the next one that meets the predetermined schedule Algorithm application. In an embodiment, the step includes: exchanging, in a memory corresponding to the predetermined algorithm, a memory page of the process corresponding to the application to be exchanged into the external memory.

In another embodiment, the step includes: selecting an application to be exchanged, exchanging a memory page of the process corresponding to the selected application into a foreign memory; and determining the exchanged Whether the sum of the amount of memory occupied by the memory page and the current amount of available memory of the system is greater than or equal to a preset threshold; if not, the step of selecting one of the applications to be exchanged is continued. For implementation efficiency considerations, the embodiment may be optimized, that is, the step includes: selecting one of the applications to be exchanged, marking the selected application; determining that the marked application corresponds to the process Whether the sum of the amount of memory occupied by the memory page of the predetermined algorithm and the current amount of available memory of the system is greater than or equal to a preset threshold; if not, proceeding to perform the step of selecting one of the applications to be exchanged; if yes, The memory pages of the corresponding processes in all the marked applications are exchanged into the external memory. Here, the preset threshold is an experimental value, and the preset threshold in the embodiment is the amount of memory required to run when any one of the mobile devices is running.

In one embodiment, the lookup has no dependencies on the specified application and is in accordance with a predetermined calculation. Before the step of the at least one application of the method as the application to be exchanged, the method further includes: determining whether the current available memory amount of the system is greater than or equal to a preset threshold; if less than the preset threshold, performing the searching and specifying The application has no dependencies and the application conforming to the predetermined algorithm acts as the application step to be exchanged; otherwise it is not processed. Here, the preset threshold is an experimental value, and the preset threshold in the embodiment is an amount of memory required to satisfy any one of the applications in the mobile device.

In one embodiment, after the step of performing a memory swap process according to the application to be exchanged, the method further comprises: executing a normal application startup process to start the specified application.

The mobile device memory management method according to an embodiment of the present invention is described in detail below through several embodiments and in conjunction with FIGS. 2-9. For convenience of description, the predetermined algorithm uniformly used in the following embodiments is the foregoing LRU algorithm, that is, the least recently used algorithm by the CPU; it should be understood that other embodiments of the present invention may be used, and are not limited to the LRU algorithm.

Embodiment 1

As shown in FIG. 2, this embodiment includes the following steps:

Step S201: Find an APP according to a predetermined algorithm;

The LRU algorithm is used to find an application (APP), that is, in the currently running application list, the application that belongs to the application corresponding to the process belongs to the least recently used CPU; it can be understood that the currently running application is not necessarily being The application that occupies the CPU, but the application that the operating system created the process for this application;

Step S202: determining whether the specified application depends on the component of the found application (APP), where the specified application refers to an application other than the currently running application, and an application to be run;

If the specified application has a dependency relationship with the application (APP), the application (APP) is excluded, and the process proceeds to step S201 to find the next application that conforms to the LRU algorithm; Excluding an application (APP) means that the memory page to which the process corresponding to the application (APP) belongs is not a memory page that can be exchanged; Step S203: performing memory exchange, specifically, finding the LRU algorithm that matches the search The memory page to which the process corresponding to the application (APP) belongs is used as a memory page that can be exchanged, and is exchanged into the external memory; wherein, the memory page exchanged refers to a process corresponding to the predetermined algorithm in the process corresponding to the application. Memory page

Step S204: The memory exchange process ends.

This embodiment considers both the advantages of the LRU algorithm and the dependencies of components between applications. Only memory pages that satisfy both conditions are selected for exchange, thereby eliminating invalid memory swapping.

Embodiment 2

As shown in FIG. 3, this embodiment includes the following steps:

Step S301: The same as step S201 of the first embodiment, that is, searching for an application (APP) conforming to the LRU algorithm in the currently running application list;

Step S302: Determine whether the specified application depends on the component of the found application (APP). Similarly, the specified application here is an application other than the currently running application. If there is a dependency relationship, the application (APP) is excluded, and the process goes to step S301 to find the next application that conforms to the LRU algorithm; if there is no dependency, the process goes to step S303; step S303: the matching plan obtained in step S302 is met. The memory page to which the process corresponding to the algorithm and the application corresponding to the dependency does not belong is a memory page that can be exchanged, and the memory exchange module is notified to exchange the memory pages into the external memory; wherein the memory page exchanged refers to the application. a memory page that conforms to a predetermined algorithm among processes corresponding to the program;

Step S304: adding the current available memory amount of the system to the amount of memory exchanged in step S303, and determining whether the sum of the two is greater than or equal to a preset threshold; where the preset threshold value is as described above, If the sum of the two is greater than or equal to the preset threshold, go to step S305; otherwise, go to step S301 to find the next application that conforms to the LRU algorithm;

Step S305: The memory exchange process ends.

This embodiment not only considers the advantages of the LRU algorithm but also considers the dependency relationship of components between applications, and also considers that the amount of memory for memory swapping must satisfy the maximum amount of memory that may be used, thereby eliminating invalid memory swaps; When the amount of memory exchanged for memory meets the maximum amount of memory that can be used, memory swapping is no longer performed, thereby reducing the switching frequency.

Embodiment 3

As shown in FIG. 4, this embodiment includes the following steps:

Step S401: The same as step S201 of the first embodiment, that is, the application (APP) conforming to the LRU algorithm in the currently running application list.

Step S402: Determine whether the specified application depends on the component of the found application (APP). Similarly, the specified application here is an application other than the currently running application. If there is a dependency, the application (APP) is excluded, and step S401 is performed to find the next application that conforms to the LRU algorithm; if there is no dependency, then step S403 is performed; Step S403: marking the matching order obtained in step S402 An application that has an algorithm and does not have a dependency;

Step S404: The amount of available memory of the system is added to the amount of memory occupied by the memory page that meets the predetermined algorithm in the process corresponding to the application marked in step S403, and it is determined whether the sum of the two is greater than or equal to a preset threshold. Here, the preset threshold is an experimental value. In the embodiment, the preset threshold is a quantity that can satisfy the running time of any application in the mobile device; wherein, the memory page that is exchanged refers to the process corresponding to the application. a memory page of a predetermined algorithm;

If the sum of the two is greater than or equal to the preset threshold, go to step S405; otherwise, go to step S401 to find the next application that conforms to the LRU algorithm; Step S405: The memory pages that meet the predetermined algorithm in the processes corresponding to the respective marked applications are used as memory pages that can be exchanged, and notify the memory switching module to exchange the memory pages into the external memory;

Step S406: The memory exchange process ends.

It can be seen that this embodiment considers not only the advantages of the LRU algorithm but also the dependencies of components between applications, and also considers that the amount of memory to be exchanged once for memory must satisfy the maximum amount of memory that can be used, and only three of them are simultaneously satisfied. Conditional memory pages are selected for swapping out, thereby eliminating invalid memory swaps and reducing the switching frequency to only one.

This embodiment is actually an optimization of the execution of the second embodiment. After all the applications that need to be exchanged are found out through the loop, the memory pages that meet the predetermined algorithm in the processes corresponding to the applications are collectively exchanged to the external memory. Medium, thereby optimizing the efficiency of execution.

Embodiment 4

As shown in FIG. 5, this embodiment includes the following steps:

Step S501: Determine whether the current memory available amount of the system is greater than or equal to a preset threshold. If yes, go to step S505; otherwise, go to step S502; Here, the preset threshold value is as described above, and is not described here;

Steps S502, S503, S504, and S505 are the same as steps S201, S202, S203, and S204 in the first embodiment, and are not described here.

In this embodiment, before the memory exchange is performed, the current memory available amount of the system is first considered, and then the memory exchange method as in the first embodiment is performed, thereby further eliminating the invalid memory exchange.

Embodiment 5

As shown in FIG. 6, the embodiment includes the following steps:

Step S601: determining whether the current memory available amount of the system is greater than or equal to a preset threshold, and if yes, proceeding to step S606; otherwise, proceeding to step S602;

Steps S602, S603, S604, S605, and S606 are respectively performed in step S301 in the second embodiment. S302, S303, S304, and S305 are the same, and are not described here.

In this embodiment, before the memory exchange is performed, the current memory available amount of the system is first considered, and then the memory exchange method as in the second embodiment is performed, thereby further eliminating the invalid memory exchange.

Embodiment 6

As shown in Figure 7, the following steps are included:

Step S701: determining whether the current memory available amount of the system is greater than or equal to a preset threshold, and if yes, proceeding to step S707; otherwise, proceeding to step S702;

Steps S702 to S707 are the same as steps S401 to S406 of the third embodiment, and are not described herein again.

In this embodiment, before the memory exchange is performed, the current memory available amount of the system is first considered, and then the memory exchange method as in the third embodiment is performed, thereby further eliminating the invalid memory exchange. Before starting the specified application, the memory exchange process as in the above embodiments is executed, and the specified application is executed after the memory exchange is completed. This approach not only eliminates invalid memory swaps, but also ensures that there is no memory swapping during application running, thus eliminating the memory swapping process that is bothering the application.

According to the above embodiments, in the mobile device memory management device provided by the embodiment of the present invention, the memory switching module is responsible for exchanging the contents of the specified memory page into the external memory, and exchanging the contents of the memory page in the external memory. When it is needed (that is, when the CPU wants to read and write the contents of the address of the memory page), it is automatically read into the specified memory page; and the application management and control module is responsible for selecting the memory page to be exchanged and deciding to swap the memory page. When you go out, you need to pay attention to the fact that in the embodiment, the application management and control module only controls the exchange, and the exchange of the exchanged content is automatically done by the memory exchange module (this function is caused by the missing page of the operating system kernel). The interruption is completed, and those skilled in the art can implement by the prior art). It can be understood that the module division in the present invention is a logical introduction introduced for convenience of description. In the specific implementation, one module can correspond to one independent software module entity (such as function, class, process, thread, etc.), or multiple modules can correspond to one software module entity, or one module corresponds to multiple software module entities.

The mobile phone memory management method provided by an embodiment of the present invention is further described below by taking an Android mobile phone as an example. In the prior art, the Android mobile phone adopts Linux operating system technology and Java technology, which makes the operation of the Android mobile phone very sensitive to the memory size. When the memory ratio is small, the Android phone will run very slowly. For this reason, Android phones are basically equipped with large-capacity memory.

As shown in Figure 8, the application management and control module consists of two classes: ActivityManagerService and PackageManageService. The memory swap module consists of virtual storage management modules in the Linux operating system kernel. In addition, communication between the application management and control module and the memory switch module is accomplished using the virtual device driver, MMUDriver.

As shown in Figure 9, this example contains the following steps:

Step S901: ActivityManagerService opens MMUDriver and prepares for memory exchange processing.

Step S902: The ActivityManagerService checks whether the amount of memory currently available to the system is greater than or equal to a preset threshold. If yes, go to step S909; otherwise, go to step S903. Here, the preset threshold is determined experimentally, in principle, to satisfy the amount of memory required for any application running on the mobile phone;

Step S903: The ActivityManagerService finds an application that conforms to the LRU algorithm from the list of currently running applications;

Step S904: The ActivityManagerService checks the description information of the current application to be started through the PackageManagerService, and looks at the external application component that it depends on, and can describe the information through the Intent method, and further convert the information into the application name to be relied upon; Step S905: The ActivityManagerService queries the currently running application list, sorts the table according to the principle of the LRU algorithm (referred to as an LRU table), and selects the first application that is not in step S904 from the LRU table (that is, Some memory pages to which the application corresponds to the process are most recently used by the CPU and their components are not dependent on) as the application to be exchanged;

Step S906: The ActivityManagerService sends the process number (PID) corresponding to the application selected in step S905 to the MMUDriver driver in the manner of writing the MMUDriver, and then waits for the MMUDriver driver to return the processing result by reading the MMUDriver driver; Step S907: MMUDriver After receiving the process ID sent by ActivityManagerService in step S906, the driver calls the function of the Linux kernel with the process number, so that the virtual storage management module of the kernel exchanges the content of the memory page occupied by the process according to the predetermined algorithm into the external memory. After completing this operation, the MMUDriver driver writes back a status value to the upper layer;

Step S908: ActivityManagerService in step S906 - waiting for the return result of the MMUDriver driver, when the result feedback, the ActivityManagerService cancels the wait, reads the status value of the MMUDriver drive write back, and continues to perform the following operations: Check whether the current free memory of the system is If the value is greater than or equal to the preset threshold, if yes, go to step S909; otherwise, exclude the application just swapped out from the LRU table, go to step S903;

Step S909: The execution application is started, and the process ends.

It can be understood that, as an optimization of execution efficiency, the ActivityManagerService can first loop through all the applications that need to be exchanged, and then notify the MMUDriver driver to exchange the memory pages of the processes corresponding to the predetermined algorithms into the processes corresponding to the predetermined algorithms. In the outer memory.

As can be seen from the above embodiments, the embodiment of the present invention reduces the invalid memory exchange by improving the traditional memory exchange method, and reduces the influence of the traditional memory exchange method on the smoothness of the application running, thereby using the memory on the mobile device such as a mobile phone. The amount is reduced without affecting the user body Test.

The above-described embodiments are merely examples of the invention, and while the preferred embodiments and the accompanying drawings of the invention are disclosed, Within the scope, various substitutions, changes and modifications are possible. Therefore, the invention should not be limited to the details disclosed in the preferred embodiments and the drawings.

Claims

Claim

A mobile device memory management method, comprising:

Finding at least one application that is not dependent on the specified application and that conforms to a predetermined algorithm as the application to be exchanged;

Performing a memory swap process according to the application to be exchanged.

2. The method according to claim 1, wherein the step of searching for at least one application that is not dependent on the specified application and conforms to a predetermined algorithm as the application to be exchanged comprises:

Find an application that matches the predetermined algorithm from the currently running application;

Look for an application that has no dependencies on the specified application from the found application that matches the predetermined algorithm, and use it as the application to be exchanged.

3. The method according to claim 1 or 2, wherein the step of performing a memory swap process according to the application to be exchanged comprises:

Selecting an application to be exchanged, and exchanging, in the process corresponding to the selected application, a memory page that meets a predetermined algorithm into the external storage;

It is judged whether the sum of the amount of memory occupied by the swapped memory page and the current available memory amount of the system is greater than or equal to a preset threshold; if not, the step of selecting one of the applications to be exchanged is continued.

4. The method according to claim 1 or 2, wherein the step of performing a memory swap process according to the application to be exchanged comprises:

Select one of the applications to be exchanged, and mark the selected application;

Determining whether the sum of the amount of memory occupied by the memory page that meets the predetermined algorithm in the process corresponding to the marked application and the current amount of available memory of the system is greater than or equal to a preset threshold; if not, proceeding to select one of the to-be-exchanged The application's step; if it is, swap the memory pages of the process corresponding to all the marked applications to the external memory Medium.

The method according to claim 1 or 2, wherein the step of performing a memory swap process according to the application to be exchanged comprises: matching a process corresponding to the application to be exchanged with a predetermined algorithm The memory pages are swapped into the external memory.

The method according to any one of claims 1 to 5, wherein before the step of searching for at least one application that is not dependent on the specified application and conforms to a predetermined algorithm as the application to be exchanged The method further includes:

Determining whether the current amount of available memory of the system is greater than or equal to a preset threshold; if less than the preset threshold, performing the searching for an application that has no dependencies with the specified application and conforms to the predetermined algorithm as an application step to be exchanged; No treatment.

The method according to any one of claims 1 to 6, wherein the application program conforming to the predetermined algorithm includes an application program to which the memory page to which the process corresponding to the application belongs is least recently used by the CPU.

The method according to any one of claims 1 to 7, wherein after the step of performing a memory swap process according to the application to be exchanged, the method further comprises: performing a normal application startup The process starts the specified application.

9. A mobile device memory management device, comprising:

An application management and control module, configured to find at least one application that is not dependent on the specified application and conforms to the predetermined algorithm as the application to be exchanged;

And a memory switching module, configured to exchange, according to the indication of the application management and control module, a memory page that meets a predetermined algorithm in a process corresponding to the application to be exchanged into the external memory.

10. The apparatus according to claim 9, wherein the application conforming to the predetermined algorithm comprises an application program to which the memory page to which the process corresponding to the application belongs is least recently used by the CPU.