WO2021254200A1

WO2021254200A1 - Page thrashing protection method and apparatus for memory reclaim of operating system

Info

Publication number: WO2021254200A1
Application number: PCT/CN2021/098652
Authority: WO
Inventors: 黄朝阳
Original assignee: 北京紫光展锐通信技术有限公司
Priority date: 2020-06-16
Filing date: 2021-06-07
Publication date: 2021-12-23
Also published as: CN111666227B; CN111666227A

Abstract

A page thrashing protection method and apparatus for reclaiming the memory of an operating system. The method comprises: a UE performing data collection on a plurality of application scenarios so as to obtain a thrashing page data set (S201); the UE solving intersections of each element in the thrashing page data set so as to obtain a set list_thrashing_common of pages that have been thrashed in all the plurality of application scenarios, and solving collections of each element in the thrashing page data set so as to obtain a set list_thrashing_all of all the pages that have been thrashed (S202); and the UE protecting list_thrashing_common and list_thrashing_all by using a block as a basic unit (S203). The method has the advantage of a good user experience.

Description

Method and device for page bumping protection of operating system memory recovery

Technical field

This application relates to the field of communication technology, and in particular to a page thrashing protection method and device for operating system memory recovery.

Background technique

The android system (linux kernel) adopts the principle of "usable and usable, recycling when busy" for memory. The recycling of memory caused some frequently used file pages to be scanned twice in succession, and the activity was quickly reduced to INACTIVE, which was finally recycled to the buddy system. Subsequent applications access the corresponding location of the file, so that the action of allocating physical pages/reading file content occurs again, and this process is generally referred to as page thrashing.

Too many page bumps will cause the performance of the system to decline, affect the use of users, and reduce user experience.

Summary of the invention

The embodiment of the present application discloses a page thrashing protection method for operating system memory recovery, which can reduce the physical memory protection capacity of thrashed pages, improve system performance, and improve user experience.

The first aspect of the embodiments of the present application provides a page thrashing protection method for operating system memory recovery. The method is applied to a user equipment UE, and the method includes the following steps:

UE performs data collection on multiple application scenarios to obtain a bump page data set;

The UE calculates the intersection of each element in the thrashing page data set to obtain the page set list_thrashing_common in the multiple application scenarios where thrashing occurs; and obtains the collection of all the elements in the thrashing page data set to obtain a set of all thrashing pages list_thrashing_all ；

The UE protects the list_thrashing_common and the list_thrashing_all with block as the basic unit

The second aspect of the embodiments of the present application provides a page thrashing protection device for operating system memory recovery. The device is applied to user equipment UE, and the device includes:

The collection unit is used to collect data from multiple application scenarios to obtain a set of bumpy page data;

A processing unit, configured to intersect each element in the bumpy page data set to obtain a page set list_thrashing_common in which bumps have occurred in the multiple application scenarios; obtain a collection of all elements in the bumpy page data set to obtain all bumps that have occurred The page set list_thrashing_all; the list_thrashing_common and the list_thrashing_all are protected with block as the basic unit.

In a third aspect, a terminal is provided, including a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor, The program includes instructions for executing the steps in the method described in the first aspect.

A fourth aspect of the embodiments of the present application discloses a computer-readable storage medium, which is characterized by storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute the method described in the first aspect.

The fifth aspect of the embodiments of the present application discloses a computer program product, wherein the above-mentioned computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the above-mentioned computer program is operable to cause a computer to execute operations as in the embodiments of the present application. Some or all of the steps described in the first aspect. The computer program product may be a software installation package.

By implementing the embodiments of the present application, the technical solution provided by the present application is that the UE collects data from multiple application scenarios to obtain a bumpy page data set; the UE calculates the intersection of each element in the bumpy page data set to obtain all of the multiple application scenarios. The thrashing page set list_thrashing_common; all elements in the thrashing page data set are collected to obtain all the thrashing page sets list_thrashing_all; the UE protects the list_thrashing_common and the list_thrashing_all using block as a basic unit. Since the basic unit of protection in this application is a block, the granularity of block protection is smaller compared to the protection of a page as the basic unit, so that multiple bumped pages can have the same block, and because the capacity of the block is smaller than the capacity of the page, The memory capacity of the physical memory lock is smaller, which prevents excess physical memory from being locked, improves system performance, and improves user experience.

Description of the drawings

The following describes the drawings used in the embodiments of the present application.

FIG. 1 is a schematic structural diagram of a terminal provided by an embodiment of the present application;

2 is a schematic flowchart of a page thrashing protection method for operating system memory recovery provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a page thrashing protection device for operating system memory recovery provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a terminal provided by an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a device provided by an embodiment of the present application.

detailed description

The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

The term "and/or" in this application is only an association relationship that describes associated objects, indicating that there can be three types of relationships. For example, A and/or B can mean: A alone exists, and both A and B exist at the same time. There are three cases of B. In addition, the character "/" in this document indicates that the associated objects before and after are in an "or" relationship.

The "plurality" appearing in the embodiments of the present application refers to two or more than two. The descriptions of the first, second, etc. appearing in the embodiments of this application are only used for illustration and distinguishing the description objects, and there is no order, and it does not mean that the number of devices in the embodiments of this application is particularly limited, and does not constitute a reference to this application. Any limitations of the embodiment. The "connection" appearing in the embodiments of this application refers to various connection modes such as direct connection or indirect connection to realize communication between devices, which is not limited in the embodiments of this application.

The terminal in the embodiments of this application may refer to various forms of UE, access terminal, user unit, user station, mobile station, MS (English: mobile station, Chinese: mobile station), remote station, remote terminal, mobile device, User terminal, terminal equipment (English: terminal equipment), wireless communication equipment, user agent, or user device. Terminal devices can also be cellular phones, cordless phones, SIP (English: session initiation protocol, Chinese: Session Initiation Protocol) phones, WLL (English: wireless local loop, Chinese: wireless local loop) stations, PDA (English: personal digital) assistant, Chinese: personal digital processing), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network or future evolution of PLMN (English : Public land mobile network, Chinese: public land mobile communication network), which is not limited in the embodiment of the present application.

Operating systems (such as Android, UNIX in enhanced mode, Windows) use virtual memory. Actual memory is a technology that simulates RAM (random access memory) by using disk space to make the machine behave as if it has more memory than it actually is. In the terminal, there is a kind of hardware called a memory management unit (MMU).

MMU treats memory as a series of "pages" composed of continuous bytes of a certain size, usually 4096 or 8192 bytes. The operating system sets up and maintains a table called Process Memory Map (PMM) for each running program. The PMM contains all the memory pages that the program can access, as well as the actual location of each memory page.

Each time a program accesses any part of the memory, the MMU will process the address (called a "virtual address"). MMU finds the actual location of the memory in the PMM (called "physical address"). The physical address can be any location in the memory or disk allocated by the operating system. If the location to be accessed by the program is on the disk, it must contain Its pages are read from disk into memory, and the PMM must be updated to reflect this operation (this is called a "page fault").

Because access to disk is much slower than access to RAM, the operating system tries to store as much virtual memory as possible in RAM. If you are running a large enough program (or running several small programs at the same time), you may not have enough RAM to hold all the memory used by the program, so some of it must be moved out of RAM and to disk (this operation is called "Paging").

The operating system guesses which memory areas are unlikely to be used in a period of time (usually based on the past memory usage), if it guesses wrong, or if the current program accesses a large amount of memory in many places, it is called out in order to read in Page, there will be many page errors. Because all RAM is in use, to access each page read in, another page must be called out, which may cause more page faults, because another page of memory has now been moved to disk, in a short time There are many page faults in the system, called "page jitter", which will greatly reduce the performance of the system.

The operating system will reclaim the memory that is being used due to the size of the physical memory. If the recovered target page is a frequently used document page (the so-called hot page), it will be read again quickly due to abnormal page faults. This situation is called "page thrashing" or "page jitter". It will greatly reduce system performance.

Please refer to FIG. 1, which is a schematic structural diagram of a terminal disclosed in an embodiment of the present application. The terminal 100 includes a storage and processing circuit 110, and a sensor 170 connected to the storage and processing circuit 110. The sensor 170 may include a camera, Distance sensor, gravity sensor, etc., the electronic device of the present application may include two transparent display screens, which are arranged on the back and front of the electronic device, and some or all of the parts between the two transparent display screens may also be Transparent, so the electronic device can be a transparent electronic device in terms of visual effects. If some parts are transparent, the electronic device can be a hollowed-out electronic device. in:

The terminal 100 may include a control circuit, and the control circuit may include a storage and processing circuit 110. The storage and processing circuit 110 can be memory, such as hard disk drive memory, non-volatile memory (such as flash memory or other electronic programmable read-only memory used to form a solid-state drive, etc.), volatile memory (such as static or dynamic random access memory). Access to memory, etc.), etc., are not limited in the embodiment of the present application. The processing circuit in the storage and processing circuit 110 may be used to control the operation of the terminal 100. The processing circuit can be implemented based on one or more microprocessors, microcontrollers, digital signal processors, baseband processors, power management units, audio codec chips, application specific integrated circuits, display driver integrated circuits, etc.

The storage and processing circuit 110 can be used to run software in the terminal 100, such as Internet browsing applications, Voice over Internet Protocol (VOIP) phone call applications, email applications, media playback applications, operating system functions, etc. . These software can be used to perform some control operations, for example, camera-based image capture, ambient light measurement based on ambient light sensors, proximity sensor measurement based on proximity sensors, and information based on status indicators such as the status indicator of light-emitting diodes. Display functions, touch event detection based on touch sensors, functions associated with displaying information on multiple (for example, layered) display screens, operations associated with performing wireless communication functions, associated with collecting and generating audio signals Operations, control operations associated with the collection and processing of button press event data, and other functions in the terminal 100 are not limited in the embodiment of the present application.

The terminal 100 may include an input-output circuit 150. The input-output circuit 150 can be used to enable the terminal 100 to input and output data, that is, to allow the terminal 100 to receive data from an external device and also allow the terminal 100 to output data from the terminal 100 to an external device. The input-output circuit 150 may further include a sensor 170. The sensor 170 vein recognition module may also include an ambient light sensor, a proximity sensor based on light and capacitance, a fingerprint recognition module, and a touch sensor (for example, a light-based touch sensor and/or a capacitive touch sensor, where the touch sensor may It is a part of the touch screen, and can also be used independently as a touch sensor structure), acceleration sensor, camera, and other sensors, etc. The camera can be a front camera or a rear camera, and the fingerprint recognition module can be integrated under the display , Used to collect fingerprint images, the fingerprint recognition module can be: optical fingerprint module, etc., which is not limited here. The aforementioned front camera can be arranged below the front display screen, and the aforementioned rear camera can be arranged below the rear display screen. Of course, the foregoing front camera or rear camera may not be integrated with the display screen. Of course, in practical applications, the foregoing front camera or rear camera may also have a lifting structure. The specific embodiments of this application do not limit the foregoing front camera. Or the specific structure of the rear camera.

The input-output circuit 150 may also include one or more display screens. In the case of multiple display screens, for example, two display screens, one display screen may be set in front of the electronic device, and the other display screen may be set in the electronic device. , Such as the display screen 130. The display screen 130 may include one or a combination of a liquid crystal display screen, a transparent display screen, an organic light emitting diode display screen, an electronic ink display screen, a plasma display screen, and a display screen using other display technologies. The display screen 130 may include a touch sensor array (ie, the display screen 130 may be a touch display screen). The touch sensor can be a capacitive touch sensor formed by an array of transparent touch sensor electrodes (such as indium tin oxide (ITO) electrodes), or it can be a touch sensor formed using other touch technologies, such as sonic touch, pressure-sensitive touch, and resistance. Touch, optical touch, etc., are not limited in the embodiment of the present application.

The terminal 100 may also include an audio component 140. The audio component 140 may be used to provide audio input and output functions for the terminal 100. The audio component 140 in the terminal 100 may include a speaker, a microphone, a buzzer, a tone generator, and other components for generating and detecting sounds.

The communication circuit 120 may be used to provide the terminal 100 with the ability to communicate with external devices. The communication circuit 120 may include analog and digital input-output interface circuits, and wireless communication circuits based on radio frequency signals and/or optical signals. The wireless communication circuit in the communication circuit 120 may include a radio frequency transceiver circuit, a power amplifier circuit, a low noise amplifier, a switch, a filter, and an antenna. For example, the wireless communication circuit in the communication circuit 120 may include a circuit for supporting Near Field Communication (NFC) by transmitting and receiving near-field coupled electromagnetic signals. For example, the communication circuit 120 may include a near field communication antenna and a near field communication transceiver. The communication circuit 120 may also include a cellular phone transceiver and antenna, a wireless local area network transceiver circuit and antenna, and so on.

The terminal 100 may further include a battery, a power management circuit, and other input-output units 160. The input-output unit 160 may include buttons, joysticks, click wheels, scroll wheels, touch pads, keypads, keyboards, cameras, light emitting diodes, and other status indicators.

The user can control the operation of the terminal 100 by inputting commands through the input-output circuit 150, and can use the output data of the input-output circuit 150 to receive status information and other outputs from the terminal 100.

Referring to Figure 2, Figure 2 provides a page thrashing protection method for operating system memory recovery. This method can be applied to the user equipment UE shown in Figure 1, and the specific structure of the UE may be the terminal structure shown in Figure 1. , The method is shown in Figure 2 and includes the following steps:

Step S201: The UE performs data collection on multiple application scenarios to obtain a bumpy page data set;

The multiple application scenarios in step S201 can be implemented in multiple ways. For example, in an alternative embodiment, one application can correspond to one application scenario, and multiple application scenarios can correspond to multiple applications, for example, Multiple apps, each app running corresponds to an application scenario. In another optional scheme, multiple applications can correspond to one application scenario. Of course, in the actual implementation, other methods may correspond to an application scenario, for example, different network connection methods correspond to one application scenario, for example, the wifi mode corresponds to one application scenario, and the 5G mode corresponds to one application scenario. etc.

The implementation method of the foregoing step S201 may specifically include:

Extract pagecache add/delete records in the ftrace information in multiple application scenarios, and find out the add/delete records that meet the principle of equality from the add/delete records as an element in the bump page data set;

The principle of equality is: add records and delete records of the same type and the same page in the add/delete records.

The method of its realization may specifically include:

UE runs multiple application scenarios. For each application scenario, the system extracts pagecache addition records and pagecache deletion records in the ftrace information, so that multiple pagecache addition records and multiple pagecache deletion records are obtained, and records are added from multiple pagecaches. A pagecache delete record searches for the same page of the same type. The same page is included in multiple pagecache addition records and multiple pagecache delete records.

The same types mentioned above include: pid, time, dev, ino, or ofs.

Step S202: The UE intersects each element in the bumpy page data set to obtain a page set list_thrashing_common that has bumps in the multiple application scenarios; obtains a collection of all elements in the bumpy page data set to obtain all bumps that have occurred. Page collection list_thrashing_all;

In an optional solution, the implementation method of step S202 may specifically include:

The UE calculates the intersection of the elements in the thrashing page data set, and has the ability to gather the thrashing pages in all application scenarios into list_thrashing_common. For the elements in list_thrashing_common, that is, pages where thrashing occurs in all application scenarios.

The UE sums up each element in the thrashing page data set, and has the ability to aggregate the thrashing pages (the thrashing pages that have occurred one or more times) in all application scenarios into list_thrashing_all. For the elements in list_thrashing_all, that is, the page where thrashing occurs in at least one application scenario.

Step S203: The UE protects the list_thrashing_common and the list_thrashing_all by using a block as a basic unit.

The implementation method of the above step S203 may specifically include:

The UE protects each element in the list_thrashing_common and the list_thrashing_all with a block as a basic unit.

For the elements of the list_thrashing_common and the list_thrashing_all, a bump page is the basic element. Each bump page may contain one or more blocks. In one solution, if all the bump pages contain a small number of blocks (for example, less than Quantity threshold), all blocks are protected (that is, the UE locks all blocks in the physical memory). In another alternative, if the number of blocks contained in all bump pages is large (for example, greater than or equal to the number threshold), some blocks are protected. For example, blocks with a large number of bumps are protected, that is, the UE is in Blocks with more lock bumps in physical memory.

In the technical solution provided by this application, the UE performs data collection on multiple application scenarios to obtain a bumpy page data set; UE takes the intersection of each element in the bumpy page data set to obtain a page set list_thrashing_common in which bumps occur in the multiple application scenarios; Collect all elements in the thrashing page data set to obtain all thrashing page sets list_thrashing_all; the UE protects the list_thrashing_common and the list_thrashing_all using block as a basic unit. Since the basic unit of protection in this application is a block, the granularity of block protection is smaller compared to the protection of a page as the basic unit, so that multiple bumped pages can have the same block, and because the capacity of the block is smaller than the capacity of the page, The memory capacity of the physical memory lock is smaller, which prevents excess physical memory from being locked, improves system performance, and improves user experience.

In an optional solution, the above UE protecting the list_thrashing_common and the list_thrashing_all using a block as a basic unit specifically includes:

The UE extends the PinnerService function of the operating system, and the extended PinnerService function is used for block-wise protection in the list_thrashing_common and the list_thrashing_all.

In an optional solution, after step S203, the above method may further include:

Update the list_thrashing_common or the list_thrashing_all to the device resource file of the operating system for compilation.

In an optional solution, after step S203, the above method may further include:

The UE starts the dumpsys pinner to view the file page that has been locked in the physical memory, and if the file page contains a block to be protected, it is determined that the file page is locked.

Referring to FIG. 3, FIG. 3 provides a page bump protection device for operating system memory recovery, the device is applied to user equipment UE, and the device includes:

The collection unit 301 is configured to collect data from multiple application scenarios to obtain a set of bumpy page data;

The processing unit 302 is configured to intersect each element in the bumpy page data set to obtain a page set list_thrashing_common in which thrashing occurs in the multiple application scenarios; and obtain a collection of all the elements in the bumpy page data set to obtain all occurrences. The thrashing page set list_thrashing_all; the list_thrashing_common and the list_thrashing_all are protected with block as the basic unit.

The technical solution provided by the present application is the page bump protection device recovered by operating system memory to collect data from multiple application scenarios to obtain a bump page data set; the page bump protection device recovered by operating system memory obtains the intersection of each element in the bump page data set Obtain the page set list_thrashing_common where thrashing occurs in the multiple application scenarios; collect all the elements in the thrashing page data set to obtain all the page set list_thrashing_all that has experienced thrashing; use the block block as the list_thrashing_common and the list_thrashing_all The basic unit is protected. Since the basic unit of protection in this application is a block, the granularity of block protection is smaller compared to the protection of a page as the basic unit, so that multiple bumped pages can have the same block, and because the capacity of the block is smaller than the capacity of the page, The memory capacity of the physical memory lock is smaller, which prevents excess physical memory from being locked, improves system performance, and improves user experience.

In an alternative scheme,

The processing unit 302 is specifically configured to extend the PinnerService function of the operating system, and the extended PinnerService function is used to protect the list_thrashing_common and the list_thrashing_all block by block.

In an alternative scheme,

The processing unit 302 is further configured to update the list_thrashing_common or the list_thrashing_all to the device resource file of the operating system for compilation.

In an alternative scheme,

The processing unit 302 is also configured to start dumpsys pinner to view the file page that has been locked in the physical memory, and if the file page contains a block to be protected, it is determined that the file page is locked.

In an alternative scheme,

The collection unit 301 is specifically used to extract pagecache add/delete records in the ftrace information in multiple application scenarios, and find the add/delete records that meet the principle of equality from the add/delete records as one of the bumped page data sets element;

In the embodiment shown in FIG. 3, the detailed solution of the processing unit and the acquisition unit can be referred to the description of the embodiment shown in FIG. 2, which will not be repeated here.

Referring to Figure 4, Figure 4 provides a terminal, including:

The collection module 401 is configured to perform data collection on multiple application scenarios to obtain a bump page data set;

The processing module 402 is configured to intersect each element in the bumpy page data set to obtain a page set list_thrashing_common in which bumps have occurred in the multiple application scenarios; and obtain a collection of all the elements in the bumpy page data set to obtain all occurrences. The thrashing page set list_thrashing_all; the list_thrashing_common and the list_thrashing_all are protected with block as the basic unit.

For the specific processing methods of the processing module and the collection module in the terminal shown in FIG. 4, reference may be made to the description of the embodiment shown in FIG. 2, which will not be repeated here.

Please refer to FIG. 5, which is a device 70 provided by an embodiment of the present application. The device 70 includes a processor 701, a memory 702, and a communication interface 703. The processor 701, the memory 702, and the communication interface 703 communicate with each other through a bus 704. connect.

The memory 702 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or Portable read-only memory (compact disc read-only memory, CD-ROM), the memory 702 is used for related computer programs and data. The communication interface 703 is used to receive and send data.

The processor 701 may be one or more central processing units (CPU). In the case where the processor 701 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 701 in the device 70 is configured to read the computer program code stored in the memory 702, and perform the following operations:

Perform data collection on multiple application scenarios to obtain a data set of bumpy pages;

Calculating the intersection of each element in the bumping page data set obtains a page set list_thrashing_common in the multiple application scenarios where thrashing occurs; calculating a collection of each element in the bumping page data set obtains a set of all thrashing pages list_thrashing_all;

The list_thrashing_common and the list_thrashing_all are protected with a block as a basic unit.

In an optional solution, the above-mentioned stored computer program code may also perform the following operations:

Expand the PinnerService function of the operating system, and the expanded PinnerService function is used to protect the list_thrashing_common and the list_thrashing_all in blocks.

The UE extracts pagecache add/delete records in the ftrace information in multiple application scenarios, and finds the add/delete records that meet the principle of equality from the add/delete records as an element in the bump page data set;

An embodiment of the present application also provides a chip system. The chip system includes at least one processor, a memory, and an interface circuit. The memory, the transceiver, and the at least one processor are interconnected by wires, and the at least one memory A computer program is stored therein; when the computer program is executed by the processor, the method flow shown in FIG. 2 is realized.

The embodiment of the present application also provides a computer-readable storage medium in which a computer program is stored. When the computer program is run on a network device, the method flow shown in FIG. 2 is implemented.

The embodiment of the present application also provides a computer program product. When the computer program product runs on a terminal, the method flow shown in FIG. 2 is realized.

An embodiment of the present application also provides a terminal, including a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor The program includes instructions for executing the steps in the method of the embodiment shown in FIG. 2.

The foregoing mainly introduces the solution of the embodiment of the present application from the perspective of the execution process on the method side. It can be understood that, in order to implement the above-mentioned functions, the electronic device includes a hardware structure and/or software template corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments provided herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application may divide the electronic device into functional units according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that this application is not limited by the described sequence of actions. Because according to this application, some steps can be performed in other order or at the same time. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and templates involved are not necessarily required by this application.

In the above-mentioned embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in an embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the above-mentioned units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable memory. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory. A number of instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the foregoing methods of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable memory, and the memory can include: a flash disk , Read-only memory (English: Read-Only Memory, abbreviation: ROM), random access device (English: Random Access Memory, abbreviation: RAM), magnetic disk or optical disc, etc.

The embodiments of the application are described in detail above, and specific examples are used in this article to illustrate the principles and implementation of the application. The descriptions of the above examples are only used to help understand the methods and core ideas of the application; at the same time, for Persons of ordinary skill in the art, based on the idea of the application, will have changes in the specific implementation and the scope of application. In summary, the content of this specification should not be construed as limiting the application.

Claims

A page thrashing protection method for operating system memory reclamation is characterized in that the method is applied to user equipment UE, and the method includes the following steps:

UE performs data collection on multiple application scenarios to obtain a bump page data set;

The UE calculates the intersection of each element in the thrashing page data set to obtain the page set list_thrashing_common in the multiple application scenarios where thrashing occurs; and obtains the collection of all the elements in the thrashing page data set to obtain a set of all thrashing pages list_thrashing_all ；

The UE protects the list_thrashing_common and the list_thrashing_all with a block as a basic unit.
The method according to claim 1, wherein the UE protecting the list_thrashing_common and the list_thrashing_all using a block as a basic unit specifically comprises:

The UE extends the PinnerService function of the operating system, and the extended PinnerService function is used for block-wise protection in the list_thrashing_common and the list_thrashing_all.
The method according to claim 1, wherein the method further comprises:

Update the list_thrashing_common or the list_thrashing_all to the device resource file of the operating system for compilation.
The method according to claim 1, wherein the method further comprises:

The UE starts the dumpsys pinner to view the file page that has been locked in the physical memory, and if the file page contains a block to be protected, it is determined that the file page is locked.
The method according to any one of claims 1 to 4, wherein the data collection performed by the UE on multiple application scenarios to obtain the bump page data set specifically comprises:

The UE extracts pagecache add/delete records in the ftrace information in multiple application scenarios, and finds the add/delete records that meet the principle of equality from the add/delete records as an element in the bump page data set;

The principle of equality is: add records and delete records of the same type and the same page in the add/delete records.
The method of claim 5, wherein:

The same types include: pid, time, dev, ino or ofs.
A page thrashing protection device for operating system memory recovery, characterized in that the device is applied to user equipment UE, and the device includes:

The collection unit is used to collect data from multiple application scenarios to obtain a set of bumpy page data;

A processing unit, configured to intersect each element in the bumpy page data set to obtain a page set list_thrashing_common in which bumps have occurred in the multiple application scenarios; obtain a collection of all elements in the bumpy page data set to obtain all bumps that have occurred The page set list_thrashing_all; the list_thrashing_common and the list_thrashing_all are protected with block as the basic unit.
The device according to claim 7, wherein:

The processing unit is specifically used to extend the PinnerService function of the operating system, and the extended PinnerService function is used to protect the list_thrashing_common and the list_thrashing_all block by block.
The device according to claim 7, wherein:

The processing unit is also used to update the list_thrashing_common or the list_thrashing_all to the device resource file of the operating system for compilation.
The device according to claim 7, wherein:

The processing unit is also used to start dumpsys pinner to view the file page that has been locked in the physical memory, and if the file page contains a block to be protected, it is determined that the file page is locked.
The device according to any one of claims 7-10, characterized in that:

The collection unit is specifically configured to extract pagecache add/delete records in the ftrace information in multiple application scenarios, and find the add/delete records that meet the principle of equality from the add/delete records as the bump page data set An element

The principle of equality is: add records and delete records of the same type and the same page in the add/delete records.
The device according to claim 11, wherein:

The same types include: pid, time, dev, ino or ofs.
A terminal, characterized by comprising a processor, a memory, a communication interface, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the processor. The program includes instructions for executing the steps in the method according to any one of claims 1-6.
A computer-readable storage medium, characterized by storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute the method according to any one of claims 1-6.
A computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute any one of claims 1 to 6 The method described.
A network device, characterized in that the network device is used to execute the terminal to execute the method according to any one of claims 1-6.