CN114968543A

CN114968543A - Method for processing document page and related device

Info

Publication number: CN114968543A
Application number: CN202110206220.XA
Authority: CN
Inventors: 王阳涛; 袁晓峰; 窦泽飞
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-02-24
Filing date: 2021-02-24
Publication date: 2022-08-30

Abstract

The embodiment of the application provides a method for processing a file page, which comprises the following steps: determining a file page to be recycled from an inactive linked list of a system; acquiring a file identifier corresponding to the file page, and determining the file page type of the file page according to the file identifier; if the file page type is a preset recycled file page type, eliminating the file page from the inactive linked list; if the file page type is not the preset recovery file page type, the file page is reserved in the inactive linked list. The technical scheme of the embodiment of the application is favorable for ensuring that important file pages are not recycled and improving the system performance.

Description

File page processing method and related device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and a related apparatus for processing a document page.

Background

When the application program runs, certain memory is occupied, and the memory resource of the mobile device is limited, so when the memory occupied by the running application exceeds the limit, some memory pages need to be recycled to relieve the memory shortage. In the linux-based system, the recyclable memory pages include file pages, the file pages are memory pages associated with files, the content of the file pages corresponds to the files in the disk, and the file pages can be directly released when being recycled and then read from the disk when needed.

Currently, Least Recently Used (LRU) algorithms are used in mobile devices to reclaim pages of files. Specifically, the LRU algorithm is implemented based on an active (active) link table and an inactive (inactive) link table. The system adds the first accessed pages into the active linked lists from the head, then moves the pages in the two linked lists according to the activity degree of the pages, and adjusts the positions of the pages in the linked lists, so that the most recently used pages are placed in the active linked lists, the less recently used pages are placed in the inactive linked lists, and the least recently used pages are placed at the tail of the inactive linked lists one by one. And when the file page needs to be recycled, preferentially recycling the file page from the tail of the inactive linked list.

The LRU algorithm recycled memory is oriented to all file pages, and sometimes the file pages are recycled and then accessed again, and page recycling reloading (page replay) is triggered. For example, when the activity of the background application increases, and with the read-write access of the background file page, the file page of the foreground application which is not accessed within a period of time reaches the tail of the inactive linked list and is recovered when the memory is in tension. Then, if the user operates the foreground application, the system needs to read the file pages from the disk into the memory again, so that the number of the page failures is increased, and the system performance is affected.

Disclosure of Invention

The application discloses a processing method of document pages, which can ensure that important document pages are not recycled under the condition of limited system memory, reduce the number of page recycling reloading and improve the system performance.

In a first aspect, an embodiment of the present application provides a method for processing a document page, where the method includes: determining a file page to be recycled from an inactive linked list of a system; acquiring a file identifier corresponding to the file page, and then determining the file page type to which the file page belongs according to the file identifier, wherein the file page type is used for indicating the importance degree of the file page in the system; if the file page type to which the file page belongs is a preset recovery file page type, eliminating the file page from the inactive linked list; if the file page type to which the file page belongs is not the preset recycled file page type, the file page is reserved in the inactive linked list.

In the embodiment of the application, the file pages are recovered when the memory is in tension, and the file pages to be recovered are the file pages positioned at the tail part of the inactive linked list. The file page with different importance degrees can be distinguished by acquiring the file identifier corresponding to the file page to be recovered and determining the file page type of the file page according to the file identifier. The file pages belonging to different file page types are processed differently, the file pages belonging to the preset recycled file page type are eliminated, the file pages not belonging to the preset recycled file page type are reserved, and the more important file pages can be reserved in the inactive linked list, so that the important file pages can be guaranteed not to be recycled as far as possible under the condition that the system memory is limited, the times that the important file pages are accessed after being recycled and need to be reloaded are reduced, IO (input/output) operation is reduced, and the system performance is improved.

In one possible implementation manner, the file page type includes one of a system key file page type, a system non-key file page type, a foreground application file page type, an associated application file page type, or a general background application file page type;

the preset recycle file page type comprises a system non-key file page type and a general background application file page type.

Illustratively, if it is determined that the file type to which the file page to be recovered belongs is the foreground application file page type, and it can be determined in advance that the foreground application file page type is not the preset recovery file page type, the file page to be recovered is retained in the inactive linked list and is not recovered.

By implementing the embodiment, the relatively important file pages and the relatively unimportant file pages can be distinguished and divided into different file page types, and the file pages of different file page types are correspondingly and differently processed, namely, are kept in the inactive linked list or eliminated from the inactive linked list, so that the important file pages are not eliminated, and the page reloading quantity is reduced.

In one possible implementation, the file identification may identify the GID for a user group of the file.

In a possible implementation manner, the determining a file page type to which the file page belongs according to the file identifier may include:

determining that the file identifier is smaller than a first threshold value, and acquiring the number of times that the file page is accessed; if the accessed times are larger than or equal to the access threshold, determining the file page type of the file page as a system key file page type; and if the accessed times are less than the access threshold, determining that the file page type to which the file page belongs is a system non-key file page type.

By implementing the embodiment, the file pages with different file attributes can be distinguished according to the file identifiers corresponding to the file pages, and the system file pages are classified according to the frequency of accessing the file pages, so that the file pages with different importance degrees are distinguished, different file page types to which the file pages belong are determined, different processing is performed on the file pages with different types, the important file pages are ensured not to be recycled, the number of page recycling reloads is reduced, and the system performance is improved.

determining that the file identifier is greater than or equal to a first threshold value, and acquiring an application identifier of a currently running foreground application; and if the file identifier and the application identifier of the foreground application meet a preset relationship, determining that the file page type to which the file page belongs is the foreground application file page type.

By implementing the embodiment, the file pages with different file attributes can be distinguished according to the file identifiers corresponding to the file pages, and the more important file pages applied by the foreground can be identified according to the file identifiers corresponding to the files and the application identifiers applied by the foreground, so that the file pages are ensured not to be recycled, the number of page recycling reloads is reduced, and the system performance is improved.

In a possible implementation manner, after determining that the file identifier is greater than or equal to a first threshold and acquiring an application identifier of a currently running foreground application, if the file identifier and the application identifier of the foreground application do not satisfy the preset relationship, acquiring an application identifier of a background application associated with the foreground application; and if the file identifier and the application identifier of the background application meet the preset relationship, determining that the file page type to which the file page belongs is the associated application file page type.

By implementing the embodiment, the file page of the background application associated with the foreground application can be identified, and the importance degree of the file page is higher, so that the file page type to which the file page belongs is determined not to be the preset recovery file page type, the file page is further ensured not to be recovered, the number of page recovery reloading is reduced, and the system performance is improved.

In a possible implementation manner, after determining that the file identifier is greater than or equal to the first threshold, and determining that the file identifier and the application identifier of the foreground application do not satisfy the preset relationship, and acquiring the application identifier of the background application associated with the foreground application, if the file identifier and the application identifier of the background application do not satisfy the preset relationship, determining that the file page type to which the file page belongs is the general background application file page type.

By implementing the embodiment, the file page of the relatively unimportant background application can be identified and recycled, so that the memory recycling is realized.

In a second aspect, an embodiment of the present application provides an apparatus for processing document pages, which may include a first determining unit, a first obtaining unit, a second determining unit, an eliminating unit, and a retaining unit, wherein:

the first determining unit is used for determining a file page to be recycled from an inactive linked list of the system;

the first acquisition unit is used for acquiring a file identifier corresponding to the file page;

a second determining unit, configured to determine, according to the file identifier, a file page type to which the file page belongs, where the file page type is used to indicate an importance degree of the file page in the system;

the eliminating unit is used for eliminating the file page from the inactive linked list if the file page type to which the file page belongs is a preset recovered file page type after the file page type to which the file page belongs is determined;

and the reservation unit is used for reserving the file page in the inactive linked list if the file page type to which the file page belongs is not the preset recovery file page type after the file page type to which the file page belongs is determined.

In a possible implementation, the file identification is a user group identification GID of the file.

In a possible implementation manner, the second determining unit is specifically configured to:

determining that the file identifier is smaller than a first threshold value, and acquiring the number of times that the file page is accessed;

if the accessed times are larger than or equal to the access threshold, determining the file page type of the file page as a system key file page type;

and if the accessed times are less than the access threshold, determining that the file page type to which the file page belongs is a system non-key file page type.

determining that the file identifier is greater than or equal to a first threshold value, and acquiring an application identifier of a currently running foreground application;

and if the file identifier and the application identifier of the foreground application meet a preset relationship, determining that the file page type to which the file page belongs is the foreground application file page type.

In a possible implementation manner, the file page to be recovered is one of N file pages at the tail of the inactive linked list, the access identifier of the file page to be recovered is set as an unaccessed identifier, the number of file pages included in the inactive linked list is greater than N, and the reservation unit is specifically configured to:

and moving the file page to be recycled to the first bit of the inactive linked list.

In one possible implementation, the apparatus further includes:

the second obtaining unit is used for obtaining the application identifier of the background application associated with the foreground application after determining that the file identifier and the application identifier of the foreground application do not meet the preset relationship;

and the third determining unit is used for determining that the file page type to which the file page belongs is the associated application file page type after determining that the file identifier and the application identifier of the background application meet the preset relationship.

In one possible implementation, the apparatus further includes:

and the fourth determining unit is used for determining that the file page type to which the file page belongs is a general background application file page type after determining that the file identifier and the application identifier of the background application do not meet the preset relationship.

In a third aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, so that the processor performs the method described in the first aspect and any possible implementation manner of the first aspect.

In a fourth aspect, the present application provides a readable storage medium storing a computer program (which may also be referred to as code or instructions) which, when executed on a computer, causes the method of the first aspect to be implemented.

It is to be understood that the apparatus of the second aspect, the electronic device of the third aspect, and the readable storage medium of the fourth aspect are all configured to execute the processing method of the document page provided by the first aspect or any one of the possible implementations of the first aspect. Therefore, the beneficial effects achieved by the method can refer to the beneficial effects in the corresponding method, and are not described herein again.

Drawings

The drawings used in the embodiments of the present application are described below.

Fig. 1 is a schematic process diagram of an LRU algorithm provided by an embodiment of the present application;

FIG. 2 is a flowchart of a method for processing document pages according to an embodiment of the present application;

FIG. 3 is a flowchart of file attribute identification provided by an embodiment of the present application;

fig. 4 is a flowchart of foreground application identification and application prediction according to an embodiment of the present disclosure;

FIG. 5 is a block diagram of a method for recycling document pages according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of another document page processing method provided in an embodiment of the present application;

fig. 7 is a schematic diagram of a memory reclamation process according to an embodiment of the present application;

FIG. 8 is a graph comparing the optimization results provided by the embodiments of the present application;

FIG. 9 is a block diagram of a device for processing document pages according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described with reference to the accompanying drawings.

The terms "first" and "second," and the like in the description, claims, and drawings of the present application are used solely to distinguish between different objects and not to describe a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. Such as a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In this application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing an association relationship of associated objects, which means that there may be three relationships, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one item(s) below" or similar expressions refer to any combination of these items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b," a and c, "" b and c, "or" a and b and c.

In order to describe the scheme of the present application more clearly, some related knowledge is introduced below.

Memory recovery: the memory of the electronic device is limited, and therefore, the Linux kernel-based system needs to perform memory management to ensure that the memory is available continuously. The management object of memory management generally refers to a region other than a memory region occupied by kernel code and reserved. Memory management refers to managing these memory areas reasonably, allocating space for drivers and user programs, and recycling unused memory. Typically the granularity of allocation and reclamation is 4k size pages (pages). Pages that can be released at any time are called recyclable pages, and such pages include document pages and anonymous pages. The process of releasing reclaimable physical memory pages is called reclaiming. When the system load increases to a certain level, the kswapd daemon scans the pages of the file, causing the reclaimable pages to be released.

Document page: the file page is a memory page associated with the file, and the content of the file page corresponds to the file in the disk, and may be a code segment of a process. The file pages can be directly released when being recycled and then read from the disk when needed.

LRU algorithm: the LRU algorithm realizes memory recovery based on active and inactive double-chain lists, and continuously updates obsolete file pages mainly according to the principle that the file pages are least recently used. Specifically, the active link list and the inactive link list generally adopt a First-In First-Out (FIFO) form, that is, new elements are added from the head of the link list and gradually move to the tail of the link list. Therefore, the system adds the first accessed page into the active linked list from the head, then moves the pages in the two linked lists according to the activity degree of the pages, and adjusts the positions of the pages in the linked lists, so that the most recently used pages are placed in the active linked list, the least recently used pages are placed in the inactive linked list, and the least recently used pages are placed at the tail of the inactive linked list one by one. When the memory needs to be released, the file pages are preferentially eliminated from the tail of the inactive linked list. In the LRU algorithm, in order to evaluate the activity degree of a file page, two identifiers, namely page _ active and page _ referred, are introduced, and a two-time-of-chance method is realized by using the two identifiers, so that the file page is prevented from moving too frequently in an LRU active chain table and an inactive chain table. The page _ active flag is used to indicate the current activity level of the file page, and the page _ referred flag is used to indicate whether the file page has been accessed recently. As shown in fig. 1, a page _ active flag of a document page is 1, which indicates that the document page is currently located in an active linked list, and a page _ active flag of 0 indicates that the document page is currently located in an active linked list; a page _ referred flag of a file page of 1 indicates that the file page has been recently accessed, and a page _ referred flag of 0 indicates that the file page has not been recently accessed. The specific process of the LRU algorithm is as follows:

(1) when a file page is accessed, the page _ referred flag of the file page is set to 1, indicating that the page has been recently accessed.

(2) When the memory is insufficient to recover the file page, if the page _ referred identifier of the file page is 1 and the page is not accessed within a certain time, the page _ referred identifier is cleared, that is, the page _ referred identifier is set to 0.

(3) And if the page which is positioned in the inactive linked list and has the page _ referred identifier of 1 is accessed, moving the page from the inactive linked list to the active linked list.

(4) When the file page is recycled, the page with the tail of the active linked list and the page _ referred identifier of 0 is moved to the active linked list according to a certain proportion.

The embodiments of the present application will be described below with reference to the drawings.

LRU algorithm recycle memory is oriented to all pages of the file, and does not distinguish the importance of the pages of the file. Memory reclamation is performed using the LRU algorithm, which generally reclaims file pages that have not been accessed recently. Sometimes, the file page is accessed again after being recycled, and page recycling reloading (page replay) is triggered. For example, when the activity of the background application increases, and with the read-write access of the background file page, the file page of the foreground application which is not accessed within a period of time reaches the tail of the inactive linked list and is eliminated when the memory is in tension. Then, if the user operates foreground application, the eliminated file pages are read again with a high probability, and at this time, the system needs to read the file pages into the memory from the disk again, so that the number of page faults is increased, and the system performance is affected. In addition, foreground application response time becomes long for the user, resulting in a poor user experience.

In view of the above problems, embodiments of the present application provide a method for processing a document page, which can ensure that important document pages are not recycled under the condition that a system memory is limited, reduce the number of page recycling reloads, and improve system performance.

Referring to fig. 2, fig. 2 is a flowchart illustrating a method for processing a document page according to an embodiment of the present disclosure. As shown in fig. 2, the method includes, but is not limited to, the following steps:

s110, determining a file page to be recycled from an inactive linked list of a system;

in the embodiment of the present application, the system for recycling the file page may be an operating system that uses an LRU algorithm to recycle memory, for example, an operating system based on a linux kernel, for example, an Android operating system. And the electronic devices using the system include, but are not limited to, mobile phones, tablet computers, palm computers, and the like. Specifically, specific steps of the processing method for the document page provided by the embodiment of the present application are described below by taking an android system as an example.

Determining a file page to be recycled from the inactive linked list may specifically include: scanning a certain number of file pages from the tail of the inactive linked list, acquiring a page _ referred identifier of each file page, if the page _ referred identifier of each file page is 0, indicating that the file page has not been accessed recently and can be recycled, determining the file page as the file page to be recycled, and continuing to execute step S120.

S120, acquiring a file identifier corresponding to the file page, and determining the file page type of the file page according to the file identifier, wherein the file page type is used for representing the importance degree of the file page in the system;

in this embodiment of the application, the file Identifier corresponding to the file page may be a Group Identifier (GID) of the file, where the file GID is used to indicate a Group to which the file belongs, and generally is a Group to which a file owner belongs. Therefore, the process of obtaining the file identifier corresponding to the file page may include: an index node (inode) number of the file is obtained according to a file name corresponding to a file page, the inode of the file can be obtained according to the inode number of the file, the inode includes meta-information of the file, such as byte number of the file, owner of the file, Group ID (i.e., GID) of the file, and the like, that is, the GID of the file can be obtained by obtaining the inode of the file, that is, a file identifier corresponding to the file page is obtained.

After the file identifier is obtained, the file page type to which the file page belongs can be determined according to the file identifier, and the file page type is used for representing the importance degree of the file page.

Optionally, the file page type includes one of a system key file page type, a system non-key file page type, a foreground application file page type, an associated application file page type, or a general background application file page type. That is, the document pages can be divided into the above five different types, and the importance levels of the five types of document pages can be distinguished. The file pages belonging to the system key file page type and the system non-key file page type are system file pages, the file page belonging to the foreground application file page type is a file page of a foreground application, and the file pages belonging to the associated application file page type and the general background application file page type are file pages of a background application.

The process of determining the type of the document page to which the document page belongs may include:

determining the type of the file page to which the file page belongs according to the file attribute corresponding to the file page.

(1) The file attributes corresponding to the file pages are identified, and the file pages corresponding to different file attributes belong to different file page types. The files may include system files and application files, and specifically, after the application installation is completed, files related to each application are stored in the application private directory, so that files in the application private directory are application files, and files not in the application private directory are system files.

In the embodiment of the application, the attribute of the file can be determined through the relation between the file identification and the first threshold value. The first threshold may be a specific value, that is, the first threshold is 10000. According to the size relationship between the GID of the file and 10000, whether the file is a system file can be determined, and the GID of the general system file is less than 10000. Therefore, if the file identifier is determined to be smaller than the first threshold, the file page may be determined to be a system file page; if the file identifier is determined to be greater than or equal to the first threshold, it may be determined that the file page is not a system file page, but a file page of a foreground application or a background application.

(2) Further, in this embodiment of the present application, the file corresponding to the file page is not a system file, and may be a foreground application file or a background application file. Generally, if a file is stored in a private directory of a foreground application, the file is a foreground application file, and if the file is not stored in the private directory of the foreground application, the file is a background application file. As shown in fig. 3, fig. 3 is a flowchart of file attribute identification.

Specifically, the application identifier of the foreground application running in the foreground may be obtained, and the file page is determined to be the file page of the foreground application or the file page of the background application according to whether the application identifier of the foreground application and the file identifier satisfy the preset relationship.

In the Android system, the obtained application Identifier may be a User Identifier (UID) of the obtained application, where the UID of the application is related to the application, and when an application program is installed, the Android system allocates a unique UID to the application to identify the application. The GID of the application program code file generated during the installation of the application has a certain relation with the UID of the application, namely, the preset relation is met, and the preset relation is met, namely the remainder of dividing the GID of the file by 10000 is equal to the remainder of dividing the UID of the application by 10000. Therefore, if it is determined that the file identifier and the application identifier of the foreground application satisfy the preset relationship, it may be determined that the file page is a foreground application file page; if the file identifier and the application identifier of the foreground application do not satisfy the preset relationship, it can be determined that the file page is not the foreground application file page.

In the embodiment of the application, the processing method of the document page is realized by the document page recycling management module and the monitoring module together. The process of acquiring the application UID of the foreground application running in the foreground may include: the monitoring module monitors the application start and exit in real time, determines the foreground application currently running in the foreground, and actively transmits the application identifier of the foreground application to the file page recovery management module, so that the file page recovery management module can acquire the application UID of the foreground application.

And (II) determining the type of the file page to which the file page belongs according to the frequency of the access of the file page.

On the basis that the file page is determined to be the system file page, the type of the file page to which the file page belongs can be determined according to the frequency of the file page being accessed. Specifically, the system sets an access count item for a system file page in advance, and the access count item is used for recording the number of times that the system file page is accessed. After the file page is determined to be the system file page, the accessed times of the file page are obtained, and the importance degree of the file page can be determined according to the relationship between the accessed times and the access threshold, wherein the relatively important file page belongs to the system key file page type, and the relatively unimportant file page belongs to the system non-key file page type.

The access threshold is preset, and there are various methods for setting the access threshold, for example, the access threshold may be set to a floating numerical value, and specifically, the number of times of accessing a plurality of system file pages is obtained, and the value with the largest number of times of accessing the system file pages is denoted as a. An access threshold is then determined based on the maximum number of accesses, for example, 80% a. And after the access threshold is set, determining the system file page with the access frequency greater than or equal to the access threshold as a system key file page, and determining the system file page with the access frequency less than the access threshold as a system non-key file page. In addition, the access threshold may also be set to a fixed value empirically, which is not limited in the embodiment of the present application.

And thirdly, determining the type of the document page to which the document page belongs according to the incidence relation between the document page and the foreground application.

On the basis of determining that the file page is not a system file page and not a foreground application file page, the type of the file page to which the file page belongs can be determined according to the incidence relation between the file page and the foreground application. Specifically, the application use habits of the user can be obtained and recorded in the system in advance, the application transfer relationship is established according to the recorded data, and the associated application of the foreground application is predicted. For example, according to the application use habit of the user, in general, after the user opens the P application in the foreground and uses the P application, the probability of switching to the Q application and using the Q application is the largest, and then the Q application is considered to be the associated application of the P application running in the foreground. If the file page of a certain background application is a file page belonging to the Q application, the user will use the Q application immediately, that is, the system will most likely access the file page, and at this time, if the file page is recycled, pagerefault may be generated later, which affects system performance.

Therefore, the system can utilize the monitoring module to record historical application use data of the user and establish an application transfer relationship updated in real time. The monitoring module is also responsible for monitoring the starting and exiting of the application and determining the application currently running in the foreground. Therefore, the monitoring module can determine the background application associated with the current foreground application according to the foreground running application and the application transfer relation, namely, predict the application to be switched for use next time by the user, and actively transmit the application UID of the application to the file page recovery management module. In this way, the file page recycle management module acquires the application UID of the background application associated with the foreground application. As shown in fig. 4, fig. 4 is a flow chart of foreground application identification and application prediction, which is performed by the monitoring module.

After the application identifier of the background application associated with the foreground application is obtained, whether the file page is the associated application file page or not is determined according to whether the file identifier and the application identifier of the background application meet a preset relation or not. Satisfying the predetermined relationship means that the remainder of dividing the file GID by 10000 is equal to the remainder of dividing the application UID by 10000. If the preset relationship is satisfied, the file page type to which the file page belongs can be determined to be the associated application file page type, and if the preset relationship is not satisfied, the file page type to which the file page belongs can be determined to be the general background application file page type.

S130, if the file page type to which the file page belongs is a preset recycled file page type, eliminating the file page from the inactive linked list;

in the embodiment of the application, after the type of the document page to which the document page belongs is determined, whether the type of the document page is a preset recycle page type is judged, and different processing is performed on the document page according to the judgment result. And if the file page type to which the file page belongs is a preset recycle page type, eliminating the file page from the inactive linked list.

Optionally, the file page type to which the file page belongs includes one of a system key file page type, a system non-key file page type, a foreground application file page type, an associated application file page type, or a general background application file page type, and then the preset recycle page type may include the system non-key file page type and the general background application file page type.

Generally, in the LRU algorithm, when the memory is in short supply and a file page needs to be recovered, the file page is scanned from the tail of the inactive linked list, and if it is determined that the file page has not been accessed recently, that is, the page _ referred flag of the file page is 0, the file page is eliminated from the inactive linked list, and the physical memory corresponding to the file page is recovered. In the embodiment of the application, when the memory is in shortage and the file page needs to be recovered, the file page is scanned from the tail of the inactive linked list, if the file page is judged to be not accessed recently, namely the page _ referred identifier of the file page is 0, the file page is determined to be the file page to be recovered, the type of the file page to which the file page belongs is determined, and if the type of the file page is determined to be the preset type of the recovered file page, the file page is eliminated from the inactive linked list. Therefore, the method and the device can further screen according to the importance degree of the file pages, ensure that the eliminated file pages are relatively unimportant file pages, and reduce the number of page faults as much as possible.

S140, if the file page type to which the file page belongs is not the preset recovery file page type, keeping the file page in the inactive linked list.

In the embodiment of the application, after the file page type to which the file page belongs is determined, whether the file page type is a preset recycle page type is judged. And if the file page type to which the file page belongs is not the preset recycle page type, keeping the file page in the inactive linked list.

Optionally, the file page type to which the file page belongs includes one of a system key file page type, a system non-key file page type, a foreground application file page type, an associated application file page type, or a general background application file page type, and then the preset recycle page type may include the system non-key file page type and the general background application file page type. That is, when it is determined that the type to which the file page belongs is not the system non-key file page type or the general background application file page type but one of the system key file page type, the foreground application file page type or the associated application file page type, the file page is retained in the inactive linked list.

When the file page is recycled, the recycling is preferentially carried out from the tail part of the inactive linked list. Therefore, the file page to be recycled is one of the N file pages located at the tail of the inactive linked list, wherein the number of the file pages contained in the inactive linked list is greater than N. The process of retaining file pages in an inactive linked list may include: and moving the file page to the first position of the inactive linked list, namely removing the file page from the tail part of the inactive linked list, and adding the file page from the head part to the inactive linked list again.

As shown in fig. 5, fig. 5 is a frame diagram of a document page processing method according to an embodiment of the present application, and the method according to the embodiment of the present application mainly includes: determining a file page to be recycled, determining a file page type to which the file page to be recycled belongs, and performing different processing on file pages of different file page types, for example, eliminating a system non-key file page and a general background application file page, and keeping the system key file page, a foreground application file page and a related application file page in a memory.

The system specifically realizes the processing method of the document page in the embodiment of the application through the monitoring module and the document page recycling management module. The monitoring module realizes the functions of the Framework (Framework) layer of the system, and particularly monitors the starting and exiting processes of foreground application on the Framework layer so as to identify the foreground application; recording historical user use habits, establishing a state transition relation between applications, and predicting the associated applications. The file page recovery management module actually realizes the functions of the file page recovery management module on a Kernel (Kernel) layer of the system, and specifically, the Kernel layer identifies a system file page, a foreground application file page and a background application file page by using a file GID and a foreground application UID corresponding to the file page; for a system file page, adding an access counting item, and setting an access threshold value for distinguishing a system key file page and a system non-key file page; comparing the file GID with a background application UID associated with the foreground application, and identifying an associated application file page and a general background application file page; based on the original LRU algorithm, the file page recovery process is modified, the general background application file pages and the system non-key file pages are preferentially recovered, and the foreground application file pages, the system key file pages and the associated application file pages are reserved.

As can be seen from the above, in the scheme of this embodiment, a file page to be recovered is determined from an inactive linked list of a system; acquiring a file identifier corresponding to a file page, and determining the type of the file page to which the file page belongs according to the file identifier; if the file page type of the file page is a preset recycled file page type, eliminating the file page from the inactive linked list; and if the file page type to which the file page belongs is not the preset recovery file page type, keeping the file page in the inactive linked list. The scheme is improved on the basis of the original LRU memory recovery mechanism, the document pages belonging to different document page types can be processed differently according to the importance degree of the document pages, the important document pages are ensured not to be recovered as far as possible under the condition that the system memory is limited, the page recovery reloading quantity is reduced, and the system performance is improved.

A specific flow of a document page processing method using the embodiment of the present application is described below with reference to a specific scenario.

Please refer to fig. 6. Fig. 6 is a flowchart of another document page processing method according to an embodiment of the present application. As shown in fig. 6, the method may include the steps of:

s210, determining a file page to be recycled.

The system can recycle the file pages when the memory is in tension. Specifically, in a linux kernel-based system, three memory water lines of high, low and min are set, when a memory is lower than the low water line, a kswapd process is waken to perform memory recovery, and file pages are eliminated in the memory recovery process until a residual memory value reaches the high water line. As shown in fig. 7, fig. 7 is a schematic diagram of a memory reclamation process. In the memory recovery process, the recovery number of the memory pages is determined according to the difference between the current residual memory value and the high water line value. For example, if the current high water line is 40MB, the low water line is 20MB, and the current remaining memory is 18MB, and the remaining memory value is 18MB < low water line 20MB, kswapd is waken to perform memory reclamation, and 40-18-22 MB of memory needs to be reclaimed, where the memory is reclaimed in units of pages, each page occupies 4KB, and 22 × 1024/4-5632 pages need to be reclaimed in this time of memory reclamation.

And pages of memory include two types: anonymous pages and document pages. File pages are maintained by two LRU linked lists, an active linked list and an inactive linked list. In the memory recovery process, the system can recover anonymous pages and file pages according to a certain proportion. In one possible embodiment, assuming this ratio is 1:1, then 5632/2 is reclaimed as 2816 pages according to the reclamation example above. After the target of 2816 file pages to be recycled is determined, scanning the file pages at the tail part of an active linked list, and putting the file pages which are not accessed recently into an inactive linked list from a head part; and then scanning the file pages at the tail part of the inactive linked list to determine finally eliminated file pages. Assuming that the number of active file pages included in the current active linked list and the number of inactive file pages included in the inactive linked list are 10000 respectively, the system may scan 2816/2 at the tail of the active linked list for 1408 active file pages, place the file page that has not been accessed recently into the inactive linked list, then scan 2816 file pages at the tail of the inactive linked list, eliminate the file pages meeting the conditions, and finally, the number of active file pages included in the active linked list and the number of inactive file pages included in the inactive linked list are in a balanced state. Of course, in the recycling process, the number of the document pages finally recycled may be smaller than 2816. After the recycling process is finished, if the residual memory still does not reach the high waterline, the kswapd process is continuously triggered to recycle the memory.

In the embodiment of the present application, eliminating the document pages meeting the condition may specifically include: and scanning the file page at the tail part of the inactive linked list, starting from the last file page, and determining the file page as the file page to be recycled under the condition that the file page is not accessed recently. Then, according to the subsequent steps of the embodiment of the present application, the document pages of the specific type are eliminated. I.e., the file pages to be recycled, the process proceeds to step S220.

S220, judging whether the file page is a system file page or not.

After determining the document pages to be recycled, the document page types to which the document pages belong need to be determined, and the importance degrees of the document pages belonging to different document page types in the system are different. Specifically, the file attribute corresponding to the file page may be identified first. Therefore, it can be determined whether the document page is a system document page.

If the document page is a system document page, step S230 is executed. If the document page is not a system document page, step S240 is executed.

Specifically, a file identifier GID corresponding to the file page may be obtained, and whether the file GID is less than 10000 is determined. If the GID of the file is less than 10000, determining that the file page is a system file page; if the file GID is greater than or equal to 10000, the file page is determined not to be a system file page. The specific process of acquiring the file GID may refer to the description of the foregoing embodiment, and is not described herein again.

And S230, judging whether the file page is a frequently accessed system file page.

After determining that the file page to be recycled is a system file page, further, the file page may be distinguished according to how frequently the file page is accessed, where more frequent access indicates that the file page is more important. Therefore, it is possible to determine whether the file page is a frequently accessed system file page.

If the file page is a frequently accessed system file page, step S260 is executed. If the file page is not a frequently accessed system file page, step S270 is executed.

Specifically, the number of times that the file page is accessed may be obtained, and whether the number of times that the file page is accessed is greater than the access threshold is determined. If the accessed times are larger than or equal to the access threshold, determining that the file page is a frequently accessed system file page; and if the accessed times are less than the access threshold, determining that the file page is not the frequently accessed system file page. For the specific description of the number of times the file page is accessed, reference may be made to the description of the foregoing embodiment, which is not described herein again.

S240, judging whether the file page is the file page of the foreground application.

After determining that the file page to be recycled is not a system file page, further, it is necessary to distinguish whether the file page is a file page of a foreground application or a file page of a background application. The file pages of the foreground application are more likely to be used by the user, and page replay may be caused if the file pages are directly recycled, so that the fluency of the system is affected. Therefore, it can be determined whether the document page is a document page of the foreground application.

If the document page is the document page of the foreground application, step S260 is executed. If the document page is not the document page of the foreground application, step S250 is executed.

Specifically, the application UID of the foreground application may be acquired, and it may be determined whether the file GID and the application UID of the foreground application satisfy a preset relationship. If the file GID and the application UID of the foreground application meet a preset relationship, determining that the file page is the file page of the foreground application; and if the file GID and the application UID of the foreground application do not meet the preset relationship, determining that the file page is not the file page of the foreground application. Satisfying the predetermined relationship means that the remainder of dividing the file GID by 10000 is equal to the remainder of dividing the application UID by 10000. For specific description of obtaining the application UID of the foreground application, reference may be made to the description of the foregoing embodiments, and details are not repeated here.

S250, judging whether the file page is the file page of the background application associated with the foreground application.

After determining that the file page to be recycled is not the system file page and the file page of the foreground application, further, it is necessary to determine the possibility that the file page is used by the user after the current time, that is, to determine whether the file page is the file page of the background application associated with the foreground application. The file pages of the background application associated with the foreground application are more likely to be used by the user after the current time.

If the document page is a document page of a background application associated with the foreground application, step S260 is executed. If the file page is not the file page of the background application associated with the foreground application, step S270 is executed.

Specifically, the application UID of the background application associated with the foreground application may be acquired, and whether the file GID and the application UID of the background application satisfy a preset relationship may be determined. If the file GID and the application UID of the background application meet the preset relationship, determining that the file page is the file page of the background application associated with the foreground application; and if the file GID and the application UID of the background application do not meet the preset relationship, determining that the file page is not the file page of the background application associated with the foreground application. For a specific description of obtaining the application UID of the background application associated with the foreground application, reference may be made to the description of the foregoing embodiment, and details are not described here.

S260, the file page is reserved in the memory.

After determining the file page type to which the file page belongs, different processing may be performed for file pages of different file page types. In this embodiment, a file page whose file page type is not the preset recycle file page type may be retained in the memory.

Specifically, the file pages are retained in the memory, and the file pages may be located in the linked list by adjusting, for example, the file pages are moved from the tail of the inactive linked list to the head of the inactive linked list. Other methods may also be used to implement the retention of the file page in the memory, for example, a special flag bit is additionally set for the file page, and when the value of the flag bit is set to a specific value, the file page is retained in the memory without being recycled. This is not limited by the present application.

S270, recycling the file pages.

After determining the file page type to which the file page belongs, different processing may be performed for file pages of different file page types. In the embodiment of the present application, a document page of which the document page type is a preset recycle document page type may be recycled.

Specifically, the recycling of the file pages may be to eliminate the file pages from the inactive linked list.

The file page processing method provided by the embodiment of the application is implemented to determine a file page to be recovered, obtain a file identifier corresponding to the file page, determine a file page type to which the file page belongs according to the file identifier, recover the file page aiming at the file page of which the file page type is the preset recovered file page type, and reserve the file page in a memory aiming at the file page of which the file page type is not the preset recovered file page type. By implementing the method, the page replay quantity caused by the obsolescence of the foreground application file pages can be effectively reduced under the condition of limited system memory, so that the IO quantity is reduced, the performance fluctuation phenomenon caused by IO blockage is reduced, and the system performance is improved.

As shown in fig. 8, fig. 8 is a comparison graph of optimization effects after the application is implemented, wherein the ordinate in the graph represents the response delay of application a in the chat session scene. Through tests, it can be found that after the method for processing the document page provided by the embodiment of the application is implemented, the variance of the stable and smooth model of the application A entering the chat session scene is actually measured and reduced by 80%, which shows that the system performance can be improved by the application of the application. The method comprises the steps that a fluency test model is used for repeatedly testing a TOP application scene for 50 times under a heavy load, specific test items comprise TOP application starting and in-application operation, and the average value and variance of response time and completion time of each test item are counted, wherein the smaller the average value is, the better the overall performance is represented, and the smaller the variance is, the better the data fluctuation is represented, and the more stable the performance is.

The foregoing describes the method of embodiments of the present application in detail, and the apparatus of embodiments of the present application is described below.

Referring to fig. 9, fig. 9 is a schematic diagram of a framework of an apparatus for processing document pages according to an embodiment of the present application, where the apparatus may include a first determining unit 301, a first obtaining unit 302, a second determining unit 303, an eliminating unit 304, and a retaining unit 305, where:

a first determining unit 301, configured to determine a file page to be recovered from an inactive linked list of a system;

a first obtaining unit 302, configured to obtain a file identifier corresponding to the file page;

a second determining unit 303, configured to determine, according to the file identifier, a file page type to which the file page belongs, where the file page type is used to indicate an importance degree of the file page in the system;

the eliminating unit 304 is configured to, after determining the file page type to which the file page belongs, eliminate the file page from the inactive linked list if the file page type to which the file page belongs is a preset recycled file page type;

the reserving unit 305 is configured to, after determining the file page type to which the file page belongs, reserve the file page in the inactive linked list if the file page type to which the file page belongs is not the preset recycle file page type.

the preset recycled file page type comprises a system non-key file page type and a general background application file page type.

In a possible implementation manner, the second determining unit 303 is specifically configured to:

In a possible implementation manner, the file page to be recovered is one of N file pages at the tail of the inactive linked list, the access identifier of the file page to be recovered is set as an unaccessed identifier, the number of file pages included in the inactive linked list is greater than N, and the reservation unit 305 is specifically configured to:

and moving the file page to be recycled to the first position of the inactive linked list.

In one possible implementation, the apparatus further includes:

It can be understood that the functions of the functional modules of the apparatus 300 in this embodiment may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.

As can be seen from the above, in the solution of this embodiment, the apparatus 300 determines a document page to be recovered, obtains a document identifier corresponding to the document page, determines a document page type to which the document page belongs according to the document identifier, and eliminates the document page from the inactive linked list if the document page type to which the document page belongs is the preset recovered document page type; and if the file page type to which the file page belongs is not the preset recovery file page type, keeping the file page in the inactive linked list. Because the file page types of different file pages are distinguished according to the importance degree, the file pages of the preset recycled file page type are eliminated, and the elimination of the file page types which are not preset recycled is reserved, the important file pages are not recycled, the number of page recycling reloads is reduced, and the system performance is improved.

Fig. 10 shows a schematic structural diagram of an electronic device 400.

The electronic device 400 may include a processor 410, an external memory interface 420, an internal memory 421, a Universal Serial Bus (USB) interface 430, a charging management module 440, a power management module 441, a battery 442, an antenna 1, an antenna 2, a mobile communication module 450, a wireless communication module 460, an audio module 470, a speaker 470A, a receiver 470B, a microphone 470C, an earphone interface 470D, a sensor module 480, a key 490, a motor 491, an indicator 492, a camera 493, a display 494, a Subscriber Identification Module (SIM) card interface 495, and the like. The sensor module 480 may include a pressure sensor 480A, a gyroscope sensor 480B, an air pressure sensor 480C, a magnetic sensor 480D, an acceleration sensor 480E, a distance sensor 480F, a proximity light sensor 480G, a fingerprint sensor 480H, a temperature sensor 480J, a touch sensor 480K, an ambient light sensor 480L, a bone conduction sensor 480M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 400. In other embodiments of the present application, electronic device 400 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 410 may include one or more processing units, such as: the processor 410 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the time sequence signal to finish the control of instruction fetching and instruction execution.

A memory may also be provided in processor 410 for storing instructions and data. In some embodiments, the memory in the processor 410 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 410. If the processor 410 needs to use the instruction or data again, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 410, thereby increasing the efficiency of the system.

In some embodiments, processor 410 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 410 may include multiple sets of I2C buses. The processor 410 may be coupled to the touch sensor 480K, the charger, the flash, the camera 493, etc. via different I2C bus interfaces. For example: the processor 410 may be coupled to the touch sensor 480K via an I2C interface, such that the processor 410 and the touch sensor 480K communicate via an I2C bus interface to implement touch functionality of the electronic device 400.

The I2S interface may be used for audio communication. In some embodiments, processor 410 may include multiple sets of I2S buses. The processor 410 may be coupled to the audio module 470 via an I2S bus to enable communication between the processor 410 and the audio module 470. In some embodiments, the audio module 470 may communicate audio signals to the wireless communication module 460 through an I2S interface to enable answering a call through a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 470 and the wireless communication module 460 may be coupled by a PCM bus interface. In some embodiments, the audio module 470 may also transmit audio signals to the wireless communication module 460 through the PCM interface, so as to receive phone calls through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 410 with the wireless communication module 460. For example: the processor 410 communicates with the bluetooth module in the wireless communication module 460 through the UART interface to implement the bluetooth function. In some embodiments, the audio module 470 may transmit the audio signal to the wireless communication module 460 through the UART interface, so as to realize the function of playing music through the bluetooth headset.

The MIPI interface may be used to connect the processor 410 with peripheral devices such as the display screen 494 and the camera 493. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 410 and camera 493 communicate over a CSI interface to implement the capture functionality of electronic device 400. The processor 410 and the display screen 494 communicate via the DSI interface to implement display functions of the electronic device 400.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect processor 410 with camera 493, display screen 494, wireless communication module 460, audio module 470, sensor module 480, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 430 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 430 may be used to connect a charger to charge the electronic device 400, and may also be used to transmit data between the electronic device 400 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only an illustration, and does not limit the structure of the electronic device 400. In other embodiments of the present application, the electronic device 400 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 440 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 440 may receive charging input from a wired charger via the USB interface 430. In some wireless charging embodiments, the charging management module 440 may receive a wireless charging input through a wireless charging coil of the electronic device 400. The charging management module 440 may also supply power to the electronic device through the power management module 441 while charging the battery 442.

The power management module 441 is used to connect the battery 442, the charging management module 440 and the processor 410. The power management module 441 receives input from the battery 442 and/or the charging management module 440 and provides power to the processor 410, the internal memory 421, the display screen 494, the camera 493, the wireless communication module 460, and the like. The power management module 441 may also be used to monitor parameters such as battery capacity, battery cycle number, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 441 may be disposed in the processor 410. In other embodiments, the power management module 441 and the charging management module 440 may be disposed in the same device.

The wireless communication function of the electronic device 400 may be implemented by the antenna 1, the antenna 2, the mobile communication module 450, the wireless communication module 460, the modem processor, the baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in electronic device 400 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 450 may provide a solution including 2G/3G/4G/5G wireless communication applied on the electronic device 400. The mobile communication module 450 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 450 may receive the electromagnetic wave from the antenna 1, and filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 450 can also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 450 may be disposed in the processor 410. In some embodiments, at least some of the functional blocks of the mobile communication module 450 may be disposed in the same device as at least some of the blocks of the processor 410.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 470A, the receiver 470B, etc.) or displays images or video through the display screen 494. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be separate from the processor 410, and may be located in the same device as the mobile communication module 450 or other functional modules.

The wireless communication module 460 may provide a solution for wireless communication applied to the electronic device 400, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 460 may be one or more devices integrating at least one communication processing module. The wireless communication module 460 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 410. The wireless communication module 460 may also receive a signal to be transmitted from the processor 410, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 400 is coupled to mobile communication module 450 and antenna 2 is coupled to wireless communication module 460, such that electronic device 400 may communicate with networks and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 400 implements display functions via the GPU, the display screen 494, and the application processor, among other things. The GPU is an image processing microprocessor connected to a display screen 494 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 410 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 494 is used to display images, videos, and the like. The display screen 494 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 400 may include 1 or N display screens 494, N being a positive integer greater than 1.

The electronic device 400 may implement a shooting function through the ISP, the camera 493, the video codec, the GPU, the display screen 494, the application processor, and the like.

The ISP is used to process the data fed back by the camera 493. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 493.

The camera 493 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 400 may include 1 or N cameras 493, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 400 selects at a frequency bin, the digital signal processor is used to perform a fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. Electronic device 400 may support one or more video codecs. In this way, the electronic device 400 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 400 can be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 420 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 400. The external memory card communicates with the processor 410 through the external memory interface 420 to implement data storage functions. For example, files such as music, video, etc. are saved in the external memory card.

The internal memory 421 may be used to store computer-executable program code, which includes instructions. The internal memory 421 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (e.g., audio data, phone book, etc.) created during use of the electronic device 400, and the like. In addition, the internal memory 421 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 410 executes various functional applications of the electronic device 400 and data processing by executing instructions stored in the internal memory 421 and/or instructions stored in a memory provided in the processor.

Electronic device 400 may implement audio functions via audio module 470, speaker 470A, microphone 470C, headset interface 470D, and an application processor, among other things. Such as music playing, recording, etc.

The audio module 470 is used to convert digital audio information into an analog audio signal output and also used to convert an analog audio input into a digital audio signal. The audio module 470 may also be used to encode and decode audio signals. In some embodiments, the audio module 470 may be disposed in the processor 410, or some functional modules of the audio module 470 may be disposed in the processor 410.

The speaker 470A, also called a "horn", is used to convert the audio electrical signals into sound signals. The electronic device 400 may listen to music through the speaker 470A or listen to a hands-free conversation.

Receiver 470B, also referred to as a "handset," is used to convert electrical audio signals into acoustic signals. When the electronic device 400 receives a call or voice information, it can receive voice by placing the receiver 470B close to the ear of the person.

The microphone 470C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal into the microphone 470C by speaking the user's mouth near the microphone 470C. The electronic device 400 may be provided with at least one microphone 470C. In other embodiments, the electronic device 400 may be provided with two microphones 470C to achieve noise reduction functions in addition to collecting sound signals. In other embodiments, the electronic device 400 may further include three, four or more microphones 470C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The earphone interface 470D is used to connect a wired earphone. The headset interface 470D may be the USB interface 430, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 480A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 480A may be disposed on the display screen 494. The pressure sensor 480A may be of a variety of types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 480A, the capacitance between the electrodes changes. The electronic device 400 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 494, the electronic apparatus 400 detects the intensity of the touch operation based on the pressure sensor 480A. The electronic apparatus 400 may also calculate the touched position based on the detection signal of the pressure sensor 480A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 480B may be used to determine the motion pose of the electronic device 400. In some embodiments, the angular velocity of the electronic device 400 about three axes (i.e., the x, y, and z axes) may be determined by the gyroscope sensor 480B. The gyro sensor 480B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 480B detects a shake angle of the electronic device 400, calculates a distance to be compensated for the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 400 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 480B can also be used for navigation and body sensing game scenes.

The air pressure sensor 480C is used to measure air pressure. In some embodiments, electronic device 400 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 480C.

The magnetic sensor 480D includes a hall sensor. The electronic device 400 may detect the opening and closing of the flip holster using the magnetic sensor 480D. In some embodiments, when the electronic device 400 is a flip phone, the electronic device 400 may detect the opening and closing of the flip according to the magnetic sensor 480D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 480E may detect the magnitude of acceleration of the electronic device 400 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 400 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 480F for measuring distance. The electronic device 400 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, the electronic device 400 may utilize the distance sensor 480F to range for fast focus.

The proximity light sensor 480G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 400 emits infrared light to the outside through the light emitting diode. The electronic device 400 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 400. When insufficient reflected light is detected, the electronic device 400 may determine that there are no objects near the electronic device 400. The electronic device 400 can utilize the proximity sensor 480G to detect that the user holds the electronic device 400 close to the ear for talking, so as to automatically turn off the screen to save power. The proximity light sensor 480G may also be used in a holster mode, a pocket mode automatically unlocking and locking the screen.

The ambient light sensor 480L is used to sense the ambient light level. The electronic device 400 may adaptively adjust the brightness of the display screen 494 based on the perceived ambient light level. The ambient light sensor 480L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 480L may also cooperate with the proximity light sensor 480G to detect whether the electronic device 400 is in a pocket to prevent inadvertent contact.

The fingerprint sensor 480H is used to collect a fingerprint. The electronic device 400 may utilize the collected fingerprint characteristics to implement fingerprint unlocking, access an application lock, fingerprint photographing, fingerprint answering, and the like.

The temperature sensor 480J is used to detect temperature. In some embodiments, the electronic device 400 implements a temperature processing strategy using the temperature detected by the temperature sensor 480J. For example, when the temperature reported by the temperature sensor 480J exceeds a threshold, the electronic device 400 performs a reduction in performance of a processor located near the temperature sensor 480J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 400 heats the battery 442 when the temperature is below another threshold to avoid an abnormal shutdown of the electronic device 400 due to low temperatures. In other embodiments, electronic device 400 performs a boost on the output voltage of battery 442 when the temperature is below a further threshold to avoid abnormal shutdown due to low temperature.

The touch sensor 480K is also referred to as a "touch panel". The touch sensor 480K may be disposed on the display screen 494, and the touch sensor 480K and the display screen 494 form a touch screen, which is also referred to as a "touch screen". The touch sensor 480K is used to detect a touch operation applied thereto or thereabout. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 494. In other embodiments, the touch sensor 480K may be disposed on a surface of the electronic device 400 at a different position than the display screen 494.

The bone conduction sensor 480M may acquire a vibration signal. In some embodiments, the bone conduction transducer 480M may acquire a vibration signal of the human voice vibrating a bone mass. The bone conduction sensor 480M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, the bone conduction sensor 480M may also be disposed in a headset, integrated into a bone conduction headset. The audio module 470 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 480M, so as to implement a voice function. The application processor can analyze heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 480M, so as to realize a heart rate detection function.

The keys 490 include a power-on key, a volume key, etc. The keys 490 may be mechanical keys. Or may be touch keys. The electronic device 400 may receive a key input, and generate a key signal input related to user setting and function control of the electronic device 400.

The motor 491 may generate a vibration indication. The motor 491 may be used for both incoming call vibration prompting and touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 491 may also respond to different vibration feedback effects in response to touch operations applied to different areas of the display screen 494. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 492 may be an indicator light, and may be used to indicate a charging status, a change in charge level, or a message, a missed call, a notification, etc.

The SIM card interface 495 is for connecting a SIM card. The SIM card can be attached to and detached from the electronic apparatus 400 by being inserted into the SIM card interface 495 or being pulled out from the SIM card interface 495. The electronic device 400 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 495 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 495 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 495 may also be compatible with different types of SIM cards. The SIM card interface 495 may also be compatible with an external memory card. The electronic device 400 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 400 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 400 and cannot be separated from the electronic device 400.

In the electronic device 400, the processor 410 calls code stored in the internal memory 421 for determining a file page to be recycled from an inactive linked list of the system; acquiring a file identifier corresponding to the file page; determining the type of the file page to which the file page belongs according to the file identifier; after determining the file page type to which the file page belongs, if the file page type to which the file page belongs is a preset recycled file page type, eliminating the file page from the inactive linked list; after determining the file page type to which the file page belongs, if the file page type to which the file page belongs is not the preset recovery file page type, reserving the file page in the inactive linked list.

It can be understood that, when the electronic device 400 of this embodiment adopts the method for processing a document page in the foregoing method embodiment, the specific implementation process thereof may refer to the related description of the foregoing method embodiment, and is not described herein again.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and the program includes, when executed, some or all of the steps of the method for processing a file page described in the foregoing method embodiment.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and these modifications or substitutions do not depart from the spirit of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A method of processing a document page, the method comprising:

determining a file page to be recycled from an inactive linked list of a system;

acquiring a file identifier corresponding to the file page, and determining a file page type to which the file page belongs according to the file identifier, wherein the file page type is used for representing the importance degree of the file page in the system;

if the file page type to which the file page belongs is a preset recycled file page type, eliminating the file page from the inactive linked list;

and if the file page type to which the file page belongs is not the preset recovery file page type, reserving the file page in the inactive linked list.

2. The method of claim 1, wherein the file page type comprises one of a system critical file page type, a system non-critical file page type, a foreground application file page type, an associated application file page type, or a general background application file page type;

the preset recycled file page types comprise system non-key file page types and general background application file page types.

3. Method according to claim 1 or 2, wherein the file identification is a user group identification GID of a file.

4. The method according to any one of claims 1-3, wherein said determining a file page type to which the file page belongs according to the file identifier comprises:

if the accessed times are larger than or equal to an access threshold, determining that the file page type to which the file page belongs is a system key file page type;

5. The method according to any one of claims 1-3, wherein said determining a file page type to which the file page belongs according to the file identifier comprises:

6. The method of claim 5, wherein the method further comprises:

if the file identification and the application identification of the foreground application do not meet the preset relationship, acquiring the application identification of the background application associated with the foreground application;

and if the file identifier and the application identifier of the background application meet the preset relationship, determining that the file page type to which the file page belongs is an associated application file page type.

7. The method of claim 6, wherein the method further comprises:

and if the file identifier and the application identifier of the background application do not meet the preset relationship, determining that the file page type to which the file page belongs is a general background application file page type.

8. The method according to any one of claims 1 to 7, wherein the file page to be recycled is one of N file pages at the tail of the inactive linked list, and the access identifier of the file page to be recycled is set to an unaccessed identifier, the number of file pages included in the inactive linked list is greater than N, and the retaining the file page in the inactive linked list comprises:

9. A device for processing document pages, comprising: a processor that, when invoking a computer program or instructions in a memory, performs the method of any of claims 1-8.

10. An electronic device, characterized in that the electronic device comprises means for performing the method of any of claims 1-8.

11. A computer-readable storage medium, comprising a computer program or instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-8.