CN117112227A - A memory management method, system, device, storage medium and electronic equipment - Google Patents

Abstract

The present disclosure discloses a memory management method, a system, a device, a storage medium and an electronic device, where after a cache unit determines an acquisition request to be executed, a memory management unit determines a first page table corresponding to the acquisition request to be executed, when the first page table is a page table being acquired by the memory management unit, waiting information is sent to the first cache unit sending the acquisition request to be executed, so as to suspend processing the acquisition request to be executed, and when the first page table is not a page table being acquired by the memory management unit, the acquisition request to be executed is executed according to page table save information stored by the memory management unit itself. Therefore, the memory management unit can process the to-be-executed acquisition requests corresponding to different page tables simultaneously, so that the resource utilization rate of the memory management unit is ensured, and the management efficiency of the memory management system is improved.

Description

A memory management method, system, device, storage medium and electronic equipment

Technical field

This specification relates to the field of caching, and in particular, to a memory management method, system, device, storage medium and electronic device.

Background technique

Generally, in order to improve the processing efficiency of the computer, a cache unit, or even a multi-level cache unit, is usually set up in the computer's memory. The cache unit is used to store the translation relationship between virtual addresses and physical addresses.

When the processor in the computer needs to perform a data processing task, it can determine the virtual address of the data required to perform the data processing task, and based on the virtual address, determine the physical address corresponding to the virtual address from the cache unit, and based on the physical address , obtain the data required for data processing tasks.

During the above process, it may happen that the physical address corresponding to the virtual address is not found in the cache unit, and the cache unit can send an acquisition request to the memory management unit (Memory Management Unit, MMU) based on the virtual address. The memory management unit queries the physical address corresponding to the virtual address from the page table according to the virtual address carried in the acquisition request, and returns the physical address to the cache unit. Therefore, the cache unit can determine the physical address corresponding to the virtual address.

However, due to the limited execution resources of the memory management unit, when a fetch request is received, execution resources need to be allocated to the memory management unit, resulting in a limited number of fetch requests that the memory management unit can handle simultaneously during the same period.

Based on this, in order to ensure the resource utilization of the memory management unit, this specification provides a memory management method.

Contents of the invention

This specification provides a memory management method, system, device, storage medium and electronic device to partially solve the above problems existing in the prior art.

This manual adopts the following technical solutions:

This specification provides a memory management method. The method is applied to a memory management unit. The memory management unit communicates with the cache unit. The method includes:

Receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed;

Determine the first page table corresponding to the virtual address;

In response to the first page table being the second page table, sending waiting information to the first cache unit; wherein the second page table is the page table being acquired by the memory management unit;

In response to the first page table not being the second page table, based on the page table storage information corresponding to the memory management unit, the to-be-executed acquisition request is executed.

Optionally, in response to the first page table being the second page table, sending waiting information to the first cache unit, specifically including:

In response to the first page table being the second page table, wait information is sent to the first cache unit according to the acquisition request to be executed, wherein the wait information is used to cause the first cache unit to wait in advance. After a set period of time, resend the pending acquisition request to the memory management unit;

The method also includes:

Receive the acquisition request to be executed that is resent by the first cache unit after the preset period of time, and determine whether the first page table is a second page table;

If not, execute the resent pending acquisition request.

Optionally, in response to the first page table being the second page table, sending waiting information to the first cache unit, specifically including:

In response to the first page table being the second page table, waiting information is sent to the first cache unit according to the acquisition request to be executed, wherein the waiting information is used to cause the first cache unit to obtain the The status of the pending acquisition request is changed to the waiting status.

Optionally, the method also includes:

Monitor the status of the first page table, and when it is determined that the memory management unit has obtained the first page table, send a retry instruction to the first cache unit, and based on the first page table Update the page table storage information; wherein the retry instruction is used to modify the state of the to-be-executed acquisition instruction to an execution state;

Receive the pending acquisition request resent by the first cache unit according to the retry instruction, and execute the resent pending acquisition request.

Optionally, the page table storage information is used to characterize the page table stored in the memory management unit;

Based on the page table storage information corresponding to the memory management unit, the to-be-executed acquisition request is executed, which specifically includes:

When it is determined that the memory management unit has acquired the first page table based on the page table saving information, the first page table is determined from each page table stored by the memory management unit, and the virtual address is in the corresponding page table according to the virtual address. Determine the corresponding physical address in the first page table, and respond to the to-be-executed acquisition request based on the physical address;

When it is determined that the memory management unit has not acquired the first page table based on the page table storage information, execution resources are allocated to the acquisition request to be executed, and the first page table is executed through the execution resources.

Optionally, executing the first page table through the execution resource specifically includes:

Using the execution resource, mark the first page table as a second page table;

Send an acquisition request corresponding to the first page table to a downstream storage unit of the memory management unit;

Receive the first page table returned by the downstream storage unit according to the acquisition request;

Determine a corresponding physical address in the first page table according to the virtual address, and respond to the to-be-executed acquisition request based on the physical address.

This specification provides a memory management system. The memory management system includes a memory management unit and a cache unit. The memory management unit communicates with the cache unit; wherein:

The first cache unit is used to send a pending acquisition request to the memory management unit;

The memory management unit is used to receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed; determine the first virtual address corresponding to the virtual address. page table; in response to the first page table being the second page table, sending waiting information to the first cache unit; wherein the second page table is the page table being acquired by the memory management unit; in response to The first page table is not the second page table, and the to-be-executed acquisition request is executed based on the page table storage information corresponding to the memory management unit.

This specification provides a memory management device. The device is applied to a memory management unit. The memory management unit communicates with the cache unit. The device includes:

A receiving module, configured to receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed;

Determining module, used to determine the first page table corresponding to the virtual address;

A first response module, configured to send waiting information to the first cache unit in response to the fact that the first page table is a second page table; wherein the second page table is a page being acquired by the memory management unit. surface;

The second response module is configured to respond to the fact that the first page table is not the second page table, and execute the to-be-executed acquisition request based on the page table storage information corresponding to the memory management unit.

This specification provides a computer-readable storage medium. The storage medium stores a computer program. When the computer program is executed by a processor, the above memory management method is implemented.

This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the above memory management method.

At least one of the above technical solutions adopted in this manual can achieve the following beneficial effects:

By determining the first page table corresponding to the acquisition request to be executed when receiving the acquisition request to be executed, when the first page table is the page table being acquired by the memory management unit, sending the acquisition request to be executed to the third page table that sends the acquisition request to be executed. A cache unit sends waiting information to suspend processing of the pending acquisition request. When the first page table is not the page table being acquired by the memory management unit, the cache unit executes the page table storage information based on the page table storage information stored in the memory management unit. Pending fetch request. This ensures that the pending acquisition requests processed by the memory management unit in the same period correspond to different page tables, so that the memory management unit can concurrently process the pending acquisition requests corresponding to different page tables, ensuring that the memory management unit Resource utilization improves the management efficiency of the memory management system.

Description of drawings

The drawings described here are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation of this specification. In the attached picture:

Figure 1 is a schematic diagram of the scene where the memory management unit processes the acquisition request;

Figure 2 is a schematic flow chart of the memory management method provided in this manual;

Figure 3 is a schematic diagram of the scenario for processing the acquisition request provided in this manual;

Figure 4 is a schematic structural diagram of the memory management system provided in this manual;

Figure 5 is a schematic flow chart of the memory management method provided in this manual;

FIG. 6 is a schematic diagram of the electronic device corresponding to FIG. 2 provided in this specification.

Detailed ways

In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this specification.

The technical solutions provided by each embodiment of this specification will be described in detail below with reference to the accompanying drawings.

Generally, the memory management unit can receive the acquisition request sent by the cache unit, and according to the virtual address carried in the acquisition request, query the physical address corresponding to the virtual address from the page table and return it to the cache unit. In order to ensure high utilization of the memory management unit, the memory management unit is usually set to process multiple acquisition requests.

However, for a page table, the page table can only be accessed by one get request at the same time. Take the memory management unit receiving the A acquisition request and the B acquisition request within the same period as an example. If the memory management unit executes the A acquisition request and the B acquisition request, it needs to access a certain page table. Assuming that the memory management unit is executing the A acquisition request, the B acquisition request needs to wait for the memory management unit to process the A acquisition request. When the page table is not accessed, the B acquisition request can be processed by the memory management unit. .

Due to the limited execution resources of the memory management unit, once a fetch request is received, execution resources are allocated to the fetch request. As a result, the memory management unit receives multiple fetch requests that need to access the same page table. In this case, the resource utilization of the memory management unit will inevitably decrease. As shown in Figure 1.

Figure 1 is a schematic diagram of a scenario in which the memory management unit processes an acquisition request. Among them, taking the cache units that send acquisition requests to the memory management unit as cache unit 1 and cache unit 2 as an example, the acquisition requests sent by cache unit 1 to the memory management unit include: acquisition request 1, acquisition request 2, acquisition request Request 3 and get request 4. The acquisition requests sent by the cache unit 2 to the memory management unit include: acquisition request 5, acquisition request 6, acquisition request 7 and acquisition request 8. Among them, the request represented by the white rectangle is a request that needs to access page table 1, and the request represented by the shaded rectangle is a request that needs to access page table 2.

Assuming that the memory management unit first receives each acquisition request sent by cache unit 1, it will appear that the memory management unit needs to execute acquisition request 1, acquisition request 2, acquisition request 3 and acquisition request 4 before it can receive the cache unit. 2. Each acquisition request is sent and processed. However, for Get Request 1, Get Request 2, Get Request 3 and Get Request 4, the page table they need to access is the same page table. Obviously, the memory management unit needs to execute each request sent by the above cache unit 1 in sequence. This results in the memory management unit being able to process only one fetch request at the same time. Resource utilization is low and memory management efficiency is low. For each request, the page table to be accessed by the request is used to represent the correspondence between the virtual address and the physical address to be obtained by the request and is stored in the page table.

Based on this, in order to improve the resource utilization of the memory management unit, this specification provides a memory management method by determining the first page table corresponding to the acquisition request to be executed when receiving the acquisition request to be executed. When the first page table is being acquired by the memory management unit, waiting information is sent to the first cache unit that sends the acquisition request to be executed, so as to suspend processing of the acquisition request to be executed. When the first page table is not the page table being acquired by the memory management unit, the pending acquisition request is executed according to the page table storage information corresponding to the memory management unit. This ensures that the page tables accessed by the acquisition requests to be executed processed by the memory management unit in the same period are different, ensuring the resource utilization of the memory management unit and improving memory management efficiency. The page table storage information is used to represent the page table stored in the memory management unit.

Figure 2 is a schematic flow chart of the memory management method provided in this manual, which specifically includes the following steps:

S100: Receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed.

This specification provides a memory management method. The execution process of the memory management method can be executed by a memory management unit used for memory management.

Based on the above brief description of the memory management method in this specification, it can be seen that the memory management method in this specification can first determine the acquisition request to be executed.

Specifically, the processor in the computer communicates with the cache unit. When the processor needs to obtain corresponding data for data processing, it can send the virtual address to the cache unit. Then the cache unit can determine the data corresponding to the virtual address according to the virtual address, and return the data to the processor. Alternatively, the cache unit can also determine the physical address corresponding to the virtual address based on the virtual address, and return the physical address to the processor, and the processor obtains corresponding data based on the physical address.

When the cache unit does not find corresponding data based on the virtual address or does not find the physical address corresponding to the virtual address, it may send an acquisition request to the memory management unit based on the virtual address.

Therefore, the memory management unit can receive the acquisition request sent by the first cache unit, and use the acquisition request as the acquisition request to be executed. Wherein, the first cache unit is the cache unit that sends the acquisition request to be executed.

At the same time, the memory management unit needs to determine the physical address corresponding to the virtual address based on the virtual address included in the acquisition request to be executed, and return it to the first cache unit. Therefore, after receiving the acquisition request to be executed, the memory management unit can parse the acquisition request to be executed and determine the virtual address included in the acquisition request to be executed.

Of course, the above-mentioned acquisition request to be executed can also be only a virtual address, that is, the first cache unit directly sends the virtual address for which the physical address needs to be determined to the memory management unit, and the memory management unit directly determines the corresponding virtual address based on the virtual address. physical address. The specific content contained in the acquisition request to be executed and how to determine the acquisition request to be executed can be set as needed, and this specification does not limit this.

S102: Determine the first page table corresponding to the virtual address.

In one or more embodiments provided in this specification, usually, the page table is stored in the main memory of the computer, and the memory management unit obtains the page table from the main memory according to the virtual address, and obtains the page table from the main memory according to the virtual address. Determine its corresponding physical address in the page table. Therefore, the memory management unit may first determine the first page table corresponding to the virtual address.

Specifically, the memory management unit stores the corresponding relationship between each page table and its corresponding virtual address range.

Therefore, the memory management unit can determine, from each page table, the page table that stores the correspondence between the virtual address and its corresponding physical address as the first page table based on the virtual address.

Furthermore, when the memory management unit accesses the page table based on the virtual address, it usually needs to retrieve the page table entry based on the high bits of the virtual address, so that in the first page table retrieved, the physical address is determined based on the low bits of the virtual address. The offset of the address in the first page table, and then locates the physical address in the first page table. It can be seen that for each virtual address, the high bits of the virtual address can be used to retrieve the first page table.

Therefore, the memory management unit can directly determine the high bit of the virtual address, and determine the identifier of the first page table corresponding to the virtual address based on the high bit. The high bits can be the first 10 bits, the first 20 bits, etc. of the virtual address, and the low bits can be the last 10 bits, the last 20 bits, etc. of the virtual address. Then the memory management unit can directly store the high bits of the virtual address. As an identifier of the first page table, it indicates that the acquisition request to be executed requires access to the page table corresponding to the high bit of the virtual address.

Then the memory management unit can perform subsequent steps based on the identification of each page table.

S104: In response to the first page table being the second page table, send waiting information to the first cache unit; wherein the second page table is the page table being acquired by the memory management unit.

S106: In response to the first page table not being the second page table, execute the pending acquisition request based on the page table storage information corresponding to the memory management unit.

The memory management method in this specification can determine whether the pending acquisition request will be executed immediately after receiving the pending acquisition request based on whether the first page table corresponding to the pending acquisition request is accessed. Among them, for each page table, there are two situations when the page table is accessed: one is that the page table is being obtained by the memory management unit, and the other is that the memory management unit has obtained the page table, but the page table is being accessed. Before receiving the pending acquisition request, the memory management unit has received other acquisition requests that need to access the page table.

For the second case, since it only needs to query the page table stored in the memory management unit to determine the physical address corresponding to the acquisition request, it requires less computing resources. Therefore, the memory management unit can be used in a short time. Process it within time. The A page table is stored in the memory management unit, and the memory management unit has received the pending acquisition request 1 and the pending acquisition request 2 in a short period of time. Both the pending acquisition request 1 and the pending acquisition request 2 need to access the A page table. Then when the memory management unit processes the pending acquisition request 2, the pending acquisition request A has already been processed by the memory management unit. This leads to the fact that when determining whether the page table is accessed, it is usually only necessary to consider whether the page table is being obtained by the memory management unit.

Specifically, for each acquisition request being executed by the memory management unit, the memory management unit may use the page table corresponding to the acquisition request as the second page table, and store the page table identifier of the second page table. In other words, the memory management unit can use the page table it is acquiring as the second page table, and store the identifier of the second page table.

Therefore, the memory management unit can determine whether the first page table exists in each second page table according to the identifier of the first page table and the page table identifier of each second page table, that is, determine whether the first page table The page table being acquired by this memory management unit.

If so, it means that the first page table is being acquired, that is, the first page table has been occupied. Therefore, the memory management unit may not execute the pending acquisition request temporarily.

If not, it means that the first page table is not the page table being acquired by the memory management unit, that is, the first page table is not occupied. Then the memory management unit executes the pending acquisition request.

It should be noted that the first page table in this specification is a page table that stores the correspondence between the virtual address in the acquisition request to be executed and its corresponding physical address. That is, the first page table is executed by the memory management unit. The page table that needs to be accessed by this pending fetch request. The second page table in this manual is the page table that the memory management unit is acquiring.

Further, in this specification, when the first page table is occupied, the pending acquisition request needs to wait until the first page table is not occupied before the memory management unit can execute the pending acquisition request. . In this case, if the memory management unit stores the acquisition requests to be executed and executes the acquisition requests to be executed sequentially according to the storage time of the acquisition requests to be executed, the corresponding execution efficiency will be poor. Therefore, when the first page table is occupied, the memory management unit can send waiting information to the first cache unit that sends the first page table,

Specifically, when the first page table is occupied, the memory management unit may determine the first cache unit that sends the acquisition request to be executed based on the acquisition request to be executed.

Therefore, the memory management unit may send wait information to the first cache unit. The waiting information is used to cause the first cache unit to re-send the pending acquisition request to the memory management unit after a preset period of time.

Then the first cache unit can receive the waiting information, and according to the waiting information, re-send the pending acquisition request to the memory management unit after a preset period of time.

The memory management unit can receive the acquisition request and determine the first page table corresponding to the resent acquisition request, and then when the first page table is not the second page table, that is, the first page table is not used. When occupied, execute the memory management unit that resends. That is to say, after receiving the resent pending acquisition request, the memory management unit can determine whether the first page table is the second page table. If so, continue to send waiting information to the first cache unit that sends the acquisition request to be executed. If not, the memory management unit can directly execute the pending acquisition request.

At the same time, the memory management unit can delete the pending acquisition requests received by itself, and continue to receive pending acquisition requests sent by other cache units.

Through the above embodiment, the memory management unit itself may not store the acquisition request to be executed, but sends the waiting information to the first cache unit, so that the first cache unit stores the acquisition request to be executed and subsequently stores the acquisition request to be executed. The execution acquisition request is resent to the memory management unit, thereby ensuring that the page tables corresponding to the acquisition requests to be executed in the memory management unit are different, so that the memory management unit can concurrently process multiple acquisition requests to be executed, improving resource utilization. Rate.

Furthermore, in this specification, when the first page table is not occupied, it means that the memory management unit can occupy the page table according to the acquisition request to be executed, that is, according to the virtual acquisition request in the acquisition request to be executed. address to access the first page of the table. Therefore, when the first page table is not the second page table, the memory management unit can execute the pending acquisition request.

Specifically, the memory management unit itself may store page table storage information. The page table storage information is used to represent the page table stored by the memory management unit itself.

Therefore, the memory management unit can determine the first page table based on the page table storage information corresponding to the memory management unit itself, query the physical address corresponding to the virtual address from the first page table, and return the physical address to the first cache unit.

Based on the memory management method shown in Figure 2, when receiving the acquisition request to be executed, the first page table corresponding to the acquisition request to be executed is determined. When the first page table is the page table being acquired by the memory management unit, , sending waiting information to the first cache unit that sends the pending acquisition request to suspend the processing of the pending acquisition request. When the first page table is not the page table being acquired by the memory management unit, according to the memory management unit The stored page table holds information to execute the pending fetch request. This ensures that the page tables accessed by the acquisition requests to be executed processed by the memory management unit in the same period are different, ensuring the resource utilization of the memory management unit and improving memory management efficiency.

In addition, the memory management unit may have its corresponding execution resources, and the execution resources of the memory management unit are limited. The execution resources may be used to characterize the upper limit of acquisition requests that the memory management unit can handle simultaneously. Taking the execution resource of the memory management unit as 4 as an example, the memory management unit can process 4 acquisition requests at the same time. Of course, the execution resources may also be computing resources, that is, the memory management unit stores computing resources that are occupied by both the acquisition request and the execution of the acquisition request. The specific definition and representational meaning of the execution resource can be set as needed, and this specification does not limit this.

In this case, if the first page table is in an occupied state, allocating execution resources for the pending acquisition request will cause the limited execution resources in the memory management unit to be occupied, thereby causing the resource utilization of the memory management unit to be occupied. lower. Therefore, when the first page table is the second page table, the memory management unit may first not allocate execution resources for the pending acquisition request, and when the first page table is not the second page table, then allocate execution resources for the pending acquisition request. The get request allocates execution resources to execute the pending get request.

Specifically, when the first page table is in the second page table, the memory management unit may return waiting information to the first cache unit according to the acquisition request to be executed. The waiting information may be used to prompt that the first page table corresponding to the pending acquisition request has been occupied, and to prompt the first cache unit to resend the pending acquisition request after a preset period of time.

Therefore, the first cache unit can re-send the pending acquisition request to the memory management unit after a preset period of time based on the received waiting information.

Then the memory management unit can receive the re-sent pending acquisition request from the first cache unit, and determine whether the first page table is the second page table based on the first page table corresponding to the re-sent pending acquisition request.

If so, the memory management unit can continue to repeat the above steps. That is, continue to send waiting information to the first cache unit, and receive the pending acquisition request resent by the first cache unit according to the waiting information until the pending acquisition request is executed.

If not, the memory management unit may allocate execution resources for the pending acquisition request, and execute the pending acquisition request according to the execution resources. That is, according to the virtual address corresponding to the acquisition request to be executed, the first page table is determined, the physical address corresponding to the virtual address is queried from the first page table, and the physical address is returned to the first cache unit.

Further, as mentioned above, when the first page table is not the second page table, it means that the first page table has not been accessed. At this time, there are two situations. One is that the first page table is accessed. The memory management unit obtains and stores it. The other is that the first page table has not been obtained by the memory management unit.

Therefore, the memory management unit can determine the page table identifier of each third page table it has obtained based on the page table storage information used to represent each page table stored by itself, and based on the page table identifier of the first page table and The page table identifier of each third page table is used to determine whether the memory management unit has obtained the first page table. The third page table is a page table that has been obtained by the memory management unit and stored in the memory management unit.

If so, it means that the memory management unit can directly determine the physical address corresponding to the virtual address in the acquisition request to be executed from the page table stored by itself. Therefore, the memory management system can determine the first page table from the page tables stored in the memory management unit itself according to the page table identifier of each third page table and the page table identifier of the first page table. Then, according to the virtual address in the acquisition request to be executed, the physical address corresponding to the virtual address is determined from the first page table. Finally, the memory management unit can respond to the pending acquisition request based on the physical address.

Wherein, the memory management unit can directly return the physical address to the first cache unit according to the pending acquisition request, or can determine the data stored at the physical address based on the physical address, and return the data stored at the physical address to the first cache unit. First cache unit. How the memory management unit responds to the request to be executed based on the physical address can be set as needed, and this specification is not restrictive.

If not, it means that the memory management unit needs to obtain the first page table before it can determine the physical address of the response from the first page table and respond to the acquisition request to be executed. Therefore, the memory management unit can allocate execution resources for the pending acquisition request, and execute the first page table through the execution resources.

The memory management unit executes the first page table to represent a process in which the memory management unit converts the physical address corresponding to the acquisition request to be executed into a virtual address according to the execution resource.

Specifically, the memory management unit can mark the first page table as the second page table through execution resources, and send the first page table to the downstream storage unit of the memory management unit according to the page table identifier of the first page table. Get request corresponding to the page table. The acquisition request of the first page table is used to acquire the first page table from the downstream storage unit. Specifically, the downstream storage unit may be a storage unit used by other memory management units or disks to store page tables.

The downstream storage unit can determine the first page table from each data stored in itself according to the received acquisition request, and return the first page table to the memory management unit.

Finally, the memory management unit can receive the first page table sent by the downstream storage unit, and determine the physical address corresponding to the virtual address in the first page table according to the virtual address in the acquisition request to be executed, and according to the physical address The address responds to the pending fetch request.

Further, in order to prevent the memory management unit from being unable to perform pending acquisition requests or other tasks due to excessive data stored in the memory management unit, the memory management unit can also be directly accessed from the downstream storage unit of the memory management unit. The first page table determines the physical address corresponding to the virtual address, and responds to the acquisition request to be executed based on the determined physical address.

Specifically, the memory management unit may send an acquisition request to the downstream storage unit. The acquisition request includes the virtual address, and the acquisition request is used to determine the physical address corresponding to the virtual address.

Therefore, the downstream storage unit can determine the first page table based on the virtual address, query the physical address corresponding to the virtual address from the first page table, and return the physical address to the memory management unit according to the acquisition request.

Then the memory management unit can receive the physical address returned by the downstream storage unit, and respond to the pending acquisition request according to the physical address.

Of course, the memory management unit can also directly pull the physical address corresponding to the virtual address or the first page table from the downstream storage unit. Specifically, how the memory management unit executes the first page table can be set as needed. This manual explains There is no restriction on this.

In addition, when obtaining the first page table through the above execution resource, the memory management unit can also determine the storage location of the first page table according to the page table identifier of the first page table through the execution resource, and obtain the storage location from the first page table. The storage location of the one-page table determines the first page table. Afterwards, the first page table is marked as a second page table, and the second page table is obtained until the memory management unit obtains the first page table. Finally, the memory management unit can execute the pending acquisition request, query the physical address corresponding to the virtual address from the acquired first page table, and return the physical address to the first cache unit.

Based on the same idea, this specification also provides a schematic diagram of a scenario in which the memory management unit processes an acquisition request, as shown in Figure 3.

Figure 3 is a schematic diagram of a scenario for processing an acquisition request provided in this specification. Similarly, taking the cache units that send acquisition requests to the memory management unit as cache unit 1 and cache unit 2 as an example, the acquisition requests sent by cache unit 1 to the memory management unit include: acquisition request 1, acquisition request 2, Get request 3 and get request 4. The acquisition requests sent by the cache unit 2 to the memory management unit include: acquisition request 5, acquisition request 6, acquisition request 7 and acquisition request 8. Among them, the request represented by the white rectangle is a request that needs to access page table 1, and the request represented by the shaded rectangle is a request that needs to access page table 2.

Therefore, based on the memory management method in this specification, after receiving the acquisition request 1, the memory management unit can determine the first page table corresponding to the acquisition request 1: page table 1. It can be seen that page table 1 is not occupied, so the memory management unit can execute the acquisition request 1. Later, when the memory management unit receives the acquisition request 2, it can determine the first page table corresponding to the acquisition request 2: page table 1. It can be seen that the page table 1 is the page table being acquired by the memory management unit, so the memory management unit may not allocate execution resources for the acquisition request 2. Similarly, after receiving acquisition request 3 and acquisition request 4, the memory management unit may not allocate execution resources to acquisition request 3 and acquisition request 4.

And if the memory management unit receives the acquisition request 5, it determines the first page table corresponding to the acquisition request 5: page table 2. It can be seen that page table 2 is not occupied, so the memory management unit can execute the acquisition request 5. Similarly, after receiving acquisition request 6, acquisition request 7 and acquisition request 8, the memory management unit can respectively determine the page table corresponding to acquisition requests 6, 7 and 8: page table 2. When the page table 2 is being acquired by the memory management unit, the memory management unit may not allocate execution resources for the acquisition request 6, the acquisition request 7 and the acquisition request 8.

Therefore, within the same period of time, the memory management unit can process two acquisition requests at the same time, and when receiving acquisition requests corresponding to other page tables, the memory management unit can also execute them. It can be seen that the memory management unit can concurrently process acquisition requests corresponding to different page tables, ensuring the resource utilization and memory management efficiency of the memory management unit.

In addition, if the first cache unit directly resends the pending acquisition request to the memory management unit after a preset period of time after receiving the waiting information, there may be a situation where the first cache unit does not completely obtain the information within the preset period. The first page table causes the first page table to still be acquired by the memory management unit. In order to avoid the above situation from happening, the memory management unit can also monitor the status of the first page table, and when it is determined that the first page table has been obtained, send a retry instruction to the first cache unit.

Specifically, the memory management unit can monitor the status of the first page table.

When it is determined according to the monitoring data that the memory management unit has obtained the first page table, the memory management unit can send a retry instruction to the first cache unit. At the same time, the memory management unit can also update the first page table according to the first page table. Page tables hold information.

Wherein, the retry instruction is used to modify the state of the to-be-executed acquisition instruction to the execution state. Taking the information stored in the page table as the identification of the third page table that has been obtained by the memory management unit and stored in the memory management unit as an example, the memory management unit can mark the first page table as the third page table, And add the identifier of the first page table to the page table storage information. Taking the information stored in the page table as the page table identifier corresponding to each third page table and the address translation relationship corresponding to each third page table as an example, the memory management unit can directly mark the first page table as the third page. table, and add the identifier of the first page table and the address translation relationship of the first page table to the page table storage information. The specific method of updating the page table storage relationship based on the first page table can be set as needed, and this manual does not limit this.

Therefore, the first cache unit can receive the retry instruction sent by the memory management unit, and according to the retry instruction, modify the state of the pending acquisition request from the waiting state to the execution state, and resend it to the memory management unit. The pending get request.

Then the memory management unit can receive the pending acquisition request resent by the cache unit, and directly determine the first page table from each page table obtained by itself, and execute the pending acquisition request according to the first page table.

Further, there may be multiple acquisition requests to be executed in a waiting state stored in the memory management unit, and the first page table corresponding to each acquisition request to be executed in a waiting state may not be the same page table. In this case, in order to avoid the situation that the first page table corresponding to the acquisition request to be executed re-sent by the first cache unit to the memory management unit is different from the first page table corresponding to the retry instruction, the memory management unit sends The retry instruction sent by the first cache unit may also carry an identifier of the target acquisition request.

Specifically, the memory management unit may store the correspondence between each acquisition request to be executed in the waiting state and each page table, and according to the first page table, from each acquisition request to be executed in the waiting state, Determine the pending acquisition request corresponding to the first page table as the target acquisition request.

Then, the memory management unit may determine a retry instruction including the identification of the target acquisition request according to the target acquisition request, and send the retry instruction to the first cache unit.

The cache unit may receive the retry instruction, determine the identifier of the target acquisition request contained in the retry instruction, and resend the target acquisition request to the memory management unit according to the identifier of the target acquisition request.

The memory management unit can receive the target acquisition request, determine the first page table corresponding to the target acquisition request from each page table obtained by itself, and then execute the target acquisition request according to the first page table, and determine the execution result.

In this specification, it may also occur that the memory management unit receives at the same time the pending acquisition request sent by the cache unit A according to the retry instruction, and the pending acquisition request sent directly by the cache unit B. If the above two pending acquisition requests are If the page table to be accessed by executing the acquisition request is the same, the memory management unit needs to first execute the pending acquisition request sent according to the retry instruction, and then execute the pending acquisition request sent by the cache unit B. In order to avoid the situation where it is difficult for the memory management unit to distinguish the above pending acquisition requests, the pending acquisition requests sent by the cache unit to the memory management unit according to the retry instruction may also be pending acquisition requests in a waiting state.

Specifically, after receiving the retry instruction, the cache unit may also send a pending acquisition request in a waiting state to the memory management unit.

The memory management unit may receive a pending acquisition request in a waiting state that is resent by the cache unit, and modify the state of the pending acquisition request to an execution state. Therefore, the memory management unit can allocate execution resources for the pending acquisition request of the execution status.

In addition, the computer may be provided with a storage unit for storing acquisition requests to be executed. That is, the cache unit sends the acquisition request to be executed to the storage unit for storage, and the memory management unit pulls the acquisition request to be executed from the storage unit and executes it. However, typically, storage units have limited resources, and the number of pending get requests that can be stored therein is also limited. Once the storage unit stores a certain acquisition request to be executed, storage resources are allocated to the acquisition request to be executed.

In this case, if each of the pending acquisition requests stored in the storage unit includes pending acquisition requests that need to access the same page table, it will inevitably affect the resource utilization of the memory management unit. Based on this, in this specification, the storage resources of the above-mentioned storage unit can also be used as the execution resources.

Specifically, when a pending acquisition request is received in the storage unit, the memory management unit may pull the pending acquisition request and determine the first page table that needs to be accessed to execute the pending acquisition request.

When the page table being acquired by the memory management unit includes the first page table, the memory management unit may send waiting information to the first cache unit that sends the acquisition request to be executed, and no longer stores the acquisition request to be executed. to this storage unit. That is, the retrieved request to be executed is deleted from the storage unit.

When the page table being acquired by the memory management unit does not include the first page table, the memory management unit may store the pending acquisition request into the storage unit.

Based on the same idea, this manual also provides a memory management system, as shown in Figure 4.

Figure 4 is a schematic structural diagram of the memory management system provided in this specification. The memory management system includes a memory management unit and a cache unit. The memory management unit communicates with the cache unit, where:

The first cache unit may send a pending fetch request to the memory management unit. The first cache unit is a cache unit that sends the acquisition request to be executed, and the first cache unit can be any cache unit in the memory management system.

The memory management unit can receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed.

Afterwards, the memory management unit can determine the first page table corresponding to the virtual address, and when the first page table is the second page table, send waiting information to the first cache unit that sent the first page table, wherein, The second page table is the page table being acquired by the memory management unit. When the first page table is a second page table, the memory management unit can execute the pending acquisition request based on its own corresponding page table storage information.

In or in multiple embodiments, for the first cache unit in the memory management system, reference may be made to the description of the cache unit and the first cache unit in the above steps S100-S106. Similarly, for the memory management unit in the memory management system, reference can be made to the description of the memory management unit in the above steps S100-S106. This application will not go into details here.

Based on the memory management system shown in Figure 4, after the cache unit determines the acquisition request to be executed, the memory management unit can determine the first page table corresponding to the acquisition request to be executed. When the first page table is the memory management unit When the page table is being acquired, wait information is sent to the first cache unit that sends the acquisition request to be executed to suspend processing of the acquisition request to be executed. When the first page table is not the page table being acquired by the memory management unit, , execute the pending acquisition request according to its own corresponding page table storage information. This ensures that the pending acquisition requests processed by the memory management unit in the same period correspond to different page tables, so that the memory management unit can concurrently process the pending acquisition requests corresponding to different page tables, ensuring that the memory management unit Resource utilization improves the management efficiency of the memory management system.

Based on the same idea, this specification also provides a memory management device, as shown in Figure 5.

Figure 5 is a schematic structural diagram of a memory management device provided in this specification. The device is applied to a memory management unit, and the memory management unit communicates with the cache unit, wherein:

The receiving module 200 is configured to receive the acquisition request to be executed sent by the first cache unit, and determine the virtual address corresponding to the acquisition request to be executed.

Determining module 202 is used to determine the first page table corresponding to the virtual address.

The first response module 204 is configured to send waiting information to the first cache unit in response to the fact that the first page table is a second page table; wherein the second page table is the one being acquired by the memory management unit. Page table.

The second response module 206 is configured to respond to the fact that the first page table is not the second page table, execute the pending acquisition request, and query the physical address corresponding to the virtual address from the first page table. , and returns the physical address to the first cache unit.

Optionally, the first response module 204 is configured to respond to the first page table being the second page table and send waiting information to the first cache unit according to the acquisition request to be executed, wherein the waiting The information is used to cause the first cache unit to re-send the acquisition request to be executed to the memory management unit after a preset period; to receive the acquisition request to be executed re-sent by the first cache unit after the preset period, And determine whether the first page table is the second page table; if not, execute the resent acquisition request to be executed.

Optionally, the first response module 204 is configured to respond to the first page table being the second page table and send waiting information to the first cache unit according to the acquisition request to be executed, wherein the waiting The information is used to cause the first cache unit to modify the state of the pending acquisition request to a waiting state.

Optionally, the first response module 204 is configured to monitor the status of the first page table, and when it is determined that the memory management unit has acquired the first page table, send a message to the first cache unit. Retry the instruction and update the page table storage information based on the first page table; wherein the retry instruction is used to modify the state of the fetch instruction to be executed to the execution state; receive the first cache unit The re-sent pending acquisition request is executed according to the retry instruction, and the re-sent pending acquisition request is executed.

Optionally, the second response module 206 is configured to determine, from each page table stored by the memory management unit, that the memory management unit has acquired the first page table based on the page table saving information. The first page table determines the corresponding physical address in the first page table according to the virtual address, and responds to the to-be-executed acquisition request based on the physical address; when it is determined based on the page table storage information When the memory management unit does not obtain the first page table, it allocates execution resources to the acquisition request to be executed, and executes the first page table through the execution resources; wherein the page table saves information for characterizing The page table stored in the memory management unit.

Optionally, the second response module 206 is configured to utilize the execution resources, mark the first page table as a second page table, and send the corresponding information of the first page table to the downstream storage unit of the memory management unit. an acquisition request, receiving the first page table returned by the downstream storage unit according to the acquisition request, determining the corresponding physical address in the first page table according to the virtual address, and based on the physical address The fetch request is to be executed for response.

This specification also provides a computer-readable storage medium that stores a computer program. The computer program can be used to execute the memory management method provided in Figure 2 above.

This specification also provides a schematic structural diagram of the electronic device shown in Figure 6. As shown in Figure 6, at the hardware level, the electronic device includes a processor, internal bus, network interface, memory and non-volatile memory, and of course may also include other hardware required for business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the memory management method described in Figure 2 above. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logical unit, and may also be hardware or logic device.

In the 1990s, improvements in a technology could be clearly distinguished as hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit, and its logic function is determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. Before compiling, The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL). There is not only one type of HDL, but many types, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., the most commonly used ones currently are VHDL (Very-High-SpeedIntegrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and/or hardware.

Those skilled in the art will understand that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of other programmable lesion detection devices to produce a machine such that the instructions executed by the processor of the computer or other programmable lesion detection device generate a A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable lesion detection device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable lesion detection device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

Those skilled in the art will appreciate that embodiments of the present specification may be provided as methods, systems, or computer program products. Thus, the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through communications networks. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The above descriptions are only examples of this specification and are not intended to limit this specification. Various modifications and variations may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims of this specification.

Claims (10)

1. A memory management method, wherein the method is applied to a memory management unit, the memory management unit communicates with a cache unit, and the method comprises:

receiving an acquisition request to be executed, which is sent by a first cache unit, and determining a virtual address corresponding to the acquisition request to be executed;

determining a first page table corresponding to the virtual address;

responding to the first page table as a second page table, and sending waiting information to the first cache unit; the second page table is a page table which is being acquired by the memory management unit;

And responding to the first page table not being a second page table, and executing the acquisition request to be executed based on page table storage information corresponding to the memory management unit.

2. The method of claim 1, wherein sending wait information to the first cache unit in response to the first page table being a second page table, comprises:

responding to the first page table as a second page table, and sending waiting information to the first cache unit according to the acquisition request to be executed, wherein the waiting information is used for enabling the first cache unit to send the acquisition request to be executed to the memory management unit again after a preset period of time;

the method further comprises the steps of:

receiving an acquisition request to be executed which is resent after the first cache unit is spaced by the preset period, and judging whether the first page table is a second page table or not;

and if not, executing the retransmitted acquisition request to be executed.

3. The method of claim 1, wherein sending wait information to the first cache unit in response to the first page table being a second page table, comprises:

and responding to the first page table as a second page table, and sending waiting information to the first cache unit according to the to-be-executed acquisition request, wherein the waiting information is used for enabling the first cache unit to modify the state of the to-be-executed acquisition request into a waiting state.

4. A method as claimed in claim 3, wherein the method further comprises:

monitoring the state of the first page table, when the memory management unit is determined to acquire the first page table, transmitting a retry instruction to the first cache unit, and updating the page table storage information based on the first page table; the retry instruction is configured to modify a state of the to-be-executed acquisition instruction into an execution state;

and receiving an acquisition request to be executed, which is resent by the first cache unit according to the retry instruction, and executing the resent acquisition request to be executed.

5. The method of claim 1 wherein the page table save information is used to characterize a page table stored in the memory management unit;

based on page table storage information corresponding to the memory management unit, executing the to-be-executed acquisition request specifically includes:

when the memory management unit is determined to acquire the first page table based on page table storage information, determining the first page table from all page tables stored by the memory management unit, determining a corresponding physical address in the first page table according to the virtual address, and responding to the acquisition request to be executed based on the physical address;

And when the memory management unit does not acquire the first page table based on the page table storage information, allocating execution resources for the acquisition request to be executed, and executing the first page table through the execution resources.

6. The method of claim 5, wherein executing the first page table by the execution resource, comprises:

marking the first page table as a second page table using the execution resource;

sending an acquisition request corresponding to the first page table to a downstream storage unit of the memory management unit;

receiving a first page table returned by the downstream storage unit according to the acquisition request;

and determining a corresponding physical address in the first page table according to the virtual address, and responding to the acquisition request to be executed based on the physical address.

7. The memory management system is characterized by comprising a memory management unit and a cache unit, wherein the memory management unit and the cache unit are communicated; wherein:

the first cache unit is used for sending an acquisition request to be executed to the memory management unit;

the memory management unit is used for receiving the to-be-executed acquisition request sent by the first cache unit and determining a virtual address corresponding to the to-be-executed acquisition request; determining a first page table corresponding to the virtual address; responding to the first page table as a second page table, and sending waiting information to the first cache unit; the second page table is a page table which is being acquired by the memory management unit; and responding to the first page table not being a second page table, and executing the acquisition request to be executed based on page table storage information corresponding to the memory management unit.

8. A memory management device, wherein the device is applied to a memory management unit, the memory management unit communicates with a cache unit, the device comprising:

the receiving module is used for receiving an acquisition request to be executed, which is sent by the first cache unit, and determining a virtual address corresponding to the acquisition request to be executed;

the determining module is used for determining a first page table corresponding to the virtual address;

the first response module is used for responding to the first page table as a second page table and sending waiting information to the first cache unit; the second page table is a page table which is being acquired by the memory management unit;

and the second response module is used for responding to the fact that the first page table is not the second page table, and executing the acquisition request to be executed based on page table storage information corresponding to the memory management unit.

9. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the method of any of the preceding claims 1-6.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of the preceding claims 1-6 when executing the program.