WO2016127291A1

WO2016127291A1 - Memory management device and method

Info

Publication number: WO2016127291A1
Application number: PCT/CN2015/072535
Authority: WO
Inventors: 洪涛
Original assignee: 华为技术有限公司
Priority date: 2015-02-09
Filing date: 2015-02-09
Publication date: 2016-08-18
Also published as: CN107209716B; CN107209716A

Abstract

A memory management device and method, which relate to the technical field of information. The method comprises: acquiring a memory which is to be allocated and is of a predetermined size (S502); creating a shared memory pool according to the memory to be allocated, with the shared memory pool comprising n memory blocks of which the length is a predetermined length and which are obtained by dividing the memory to be allocated, and the shared memory pool being used for a memory application service for providing memory blocks of at least two different lengths (S504); acquiring a demanded length corresponding to a memory application (S506); and acquiring, from the shared memory pool, a memory block of which the length is the demanded length for use in allocation (S508). The technical solution solves the problems in the related art of a serious waste of a memory and a low total utilization rate of the memory. Memory blocks of different lengths share a shared memory pool, so that it cannot only be guaranteed that peak demands of the memory blocks of different lengths are coped with when a memory is allocated, but also the effects of saving a memory and improving a total utilization rate of the memory can be achieved.

Description

Memory management device and method

Technical field

The present invention relates to the field of information technology, and in particular, to a memory management apparatus and method.

Background technique

The Buffer Management Unit (BMU) is a hardware device that is installed inside the processor and used to manage the memory.

The method for managing the memory by the BMU is as follows: The BMU first obtains a memory of a predetermined size to be allocated, and then creates multiple memory pools according to the memory to be allocated. The same memory pool includes several memory blocks of equal length. The number of memory pools created and the length of memory blocks in each memory pool can be configured according to actual needs. For example, suppose the BMU creates three memory pools, namely memory pool 1, memory pool 2, and memory pool 3. The memory pool 1 includes N1 memory blocks of length L1 bytes, and the memory pool 2 includes N2 memory blocks of length L2 bytes, and the memory pool 3 includes N3 memory blocks of length L3 bytes. L1, L2 and L3 are not equal. After that, the BMU manages the memory blocks in each memory pool according to the requirements of memory application and release. For example, when the required length of the memory request is L2 bytes, the BMU detects whether there is a free memory block in the memory pool 2; if it exists, selects a free memory block from the memory pool 2 for allocation and use; If it exists, the memory application fails.

In the process of implementing the present invention, the inventor has found that the above-mentioned technologies have at least the following problems: in order to ensure the reliability of memory allocation, and to cope with the peak usage of memory blocks of different lengths, the BMU needs to separately allocate memory blocks satisfying the peak demand to each memory pool. Quantity. However, in actual use, multiple memory pools do not reach peak usage at the same time. For example, when memory pool 1 reaches the peak usage, memory pool 2 and memory pool 3 do not reach the peak usage; when memory pool 3 reaches the peak usage, memory pool 1 and memory pool 2 do not reach the peak usage. Therefore, the above technology has a problem of serious memory waste and low total memory utilization.

Summary of the invention

In order to solve the problem of serious memory waste and low total memory utilization in the above technology, this issue The embodiment provides a memory management apparatus and method. The technical solution is as follows:

In a first aspect, a memory management device is provided, the device comprising:

a first acquiring unit, configured to acquire a memory of a predetermined size to be allocated;

a creating unit, configured to create a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the to-be-allocated memory, where the shared memory pool is used to provide a memory application service of at least two memory blocks of different lengths, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

a second acquiring unit, configured to acquire a required length corresponding to the memory application, where the required length is one of the at least two different lengths;

And an allocating unit, configured to obtain, from the shared memory pool, a memory block of a length of the required length for allocation.

In a first possible implementation manner of the first aspect, the allocating unit is specifically configured to:

Detecting, in the shared memory pool, whether there is a first memory block that is idle and has a length of the required length;

If the first memory block exists in the shared memory pool, the first memory block is allocated for use.

In conjunction with the first possible implementation of the first aspect, in a second possible implementation of the first aspect, the allocating unit is further configured to:

If the first memory block does not exist in the shared memory pool, select a second memory block that is idle and has a length greater than the required length from the shared memory pool;

Dividing the second memory block into m memory blocks, where the m memory blocks include a memory block having a length of the required length, m≥2 and m is an integer;

And selecting, from the m memory blocks, the memory block whose length is the required length for allocation and use.

In conjunction with the second possible implementation of the first aspect, in a third possible implementation of the first aspect, the allocating unit is further configured to:

When there are at least two different lengths of the second memory block in the shared memory pool, an idle second memory block having a length greater than and closest to the required length is selected from the shared memory pool.

In conjunction with the first aspect, the first possible implementation of the first aspect, the second possible implementation of the first aspect, or the third possible implementation of the first aspect, the fourth possibility in the first aspect In an embodiment, the device further includes:

a third acquiring unit, configured to acquire a memory address and a length corresponding to the memory block that needs to be released;

a detecting unit, configured to detect, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle according to the memory address, when the length of the memory block to be released is less than the predetermined length, The length of the target memory block is one of the at least two different lengths and the length of the target memory block is greater than and closest to the length of the memory block to be released;

a merging unit, configured to merge the memory block to be released and the other memory block into the target memory block when the other memory block is idle, the length of the target memory block being the at least two different One of the lengths.

Combining the first aspect, the first possible implementation of the first aspect, the second possible implementation of the first aspect, the third possible implementation of the first aspect, or the fourth possible aspect of the first aspect In a fifth possible implementation manner of the first aspect, the at least two memory blocks of different lengths include memory blocks of different lengths of w levels, and the length of the i+1th memory block is the i-th level The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.

In a second aspect, a memory management apparatus is provided, the apparatus comprising: a controller and a register;

The register is configured to store one or more instructions for implementing a memory management method;

The method includes:

Obtaining a predetermined size of memory to be allocated;

Creating a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the to-be-allocated memory, where the shared memory pool is used to provide at least two different lengths. Memory application service of the memory block, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

Obtaining a required length corresponding to the memory application, where the required length is one of the at least two different lengths;

Obtaining, by using the shared memory pool, a memory block of a length of the required length for allocation and use;

The controller is operative to execute the instructions.

In a first possible implementation of the second aspect, the register further stores instructions for performing the following operations:

If the first memory block exists in the shared memory pool, the first memory block is allocated for use;

The controller is also operative to execute the instructions.

In conjunction with the first possible implementation of the second aspect, in a second possible implementation of the second aspect, the register further stores instructions for performing the following operations:

When the first memory block does not exist in the shared memory pool, select a second memory block that is idle and has a length greater than the required length from the shared memory pool;

And selecting, from the m memory blocks, the memory block whose length is the required length for allocation and use;

The controller is also operative to execute the instructions.

In conjunction with the second possible implementation of the second aspect, in a third possible implementation of the second aspect, the register further stores instructions for performing the following operations:

When there are at least two different memory blocks of different lengths in the shared memory pool, select a second memory block that is free from the shared memory pool and has a length greater than and closest to the required length;

The controller is also operative to execute the instructions.

With reference to the second aspect, the first possible implementation of the second aspect, the second possible implementation of the second aspect, or the third possible implementation of the second aspect, the fourth possibility in the second aspect In an embodiment, the register further stores instructions for performing the following operations:

Get the memory address and length corresponding to the memory block that needs to be released;

When the length of the memory block to be released is less than the predetermined length, detecting, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle, the length of the target memory block Is one of the at least two different lengths and the length of the target memory block is greater than and closest to the length of the memory block that needs to be released;

If the other memory block is idle, merge the memory block to be released and the other memory block into the target memory block, and the length of the target memory block is one of the at least two different lengths ;

The controller is also operative to execute the instructions.

Combining the second aspect, the first possible implementation of the second aspect, the second possible implementation of the second aspect, the third possible implementation of the second aspect, or the fourth possible aspect of the second aspect The fifth possible implementation manner of the second aspect, the memory block of the at least two different lengths includes a memory block of different lengths of w levels, and the length of the i+1th memory block is the i-th level The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.

In a third aspect, a memory management method is provided, the method comprising:

Obtaining a predetermined size of memory to be allocated;

Obtaining a memory block of the required length from the shared memory pool for allocation.

In a first possible implementation manner of the third aspect, the obtaining, by using the shared memory pool, a memory block of the required length, for use, includes:

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the detecting, in the shared memory pool, whether there is a first one that is idle and has a length of the required length After the memory block, it also includes:

And selecting, from the m memory blocks, the memory block having the length of the required length to be allocated use.

With reference to the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the selecting, from the shared memory pool, the second memory that is idle and has a length greater than the required length Blocks, including:

In combination with the third aspect, the first possible implementation of the third aspect, the second possible implementation of the third aspect, or the third possible implementation of the third aspect, the fourth possibility in the third aspect In an embodiment, the method further includes:

If the other memory block is idle, merge the memory block to be released and the other memory block into the target memory block, and the length of the target memory block is one of the at least two different lengths .

Combining the third aspect, the first possible implementation of the third aspect, the second possible implementation of the third aspect, the third possible implementation of the third aspect, or the fourth possible aspect of the third aspect The fifth possible implementation manner of the third aspect, the memory block of the at least two different lengths includes a memory block of different lengths of w levels, and the length of the i+1th memory block is the i-th level The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.

The beneficial effects of the technical solutions provided by the embodiments of the present invention include:

By creating a shared memory pool, the shared memory pool provides at least two application services for memory blocks of different lengths, and obtains a memory block of a required length from the shared memory pool when the required length of the memory request is obtained. Distribute and use; solve the problem of serious memory waste and low total memory utilization in related technologies; share a shared memory pool through memory blocks of different lengths, which can ensure the peak demand of different length memory blocks in memory allocation , can also achieve the effect of saving memory and improving the total utilization of memory.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic diagram of an implementation environment involved in various embodiments of the present invention;

2 is a block diagram showing the structure of a memory management apparatus according to an embodiment of the present invention;

3 is a block diagram showing the structure of a memory management apparatus according to another embodiment of the present invention;

4 is a schematic structural diagram of a memory management apparatus according to still another embodiment of the present invention;

FIG. 5 is a flowchart of a method for a memory management method according to an embodiment of the present invention; FIG.

6A is a flowchart of a method for a memory management method according to another embodiment of the present invention;

6B is a schematic diagram of a memory pool created by the memory management method provided by the background technology;

FIG. 6C is a schematic diagram of a memory pool created by using the memory management method provided by the embodiment of the present invention; FIG.

FIG. 6D is a flowchart related to step 604 in the memory management method according to another embodiment of the present invention;

6E is a schematic diagram of memory allocation involved in a memory management method provided by an embodiment of the present invention;

7A/7B are flowcharts of a method for a memory management method according to still another embodiment of the present invention;

FIG. 8 is a flowchart of a method for a memory management method according to still another embodiment of the present invention.

detailed description

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

Please refer to FIG. 1 , which is a schematic diagram of an implementation environment involved in various embodiments of the present invention. The implementation environment includes: a processor (English: Central Processing Unit; CPU) 10 and a memory 20, and the processor 10 It can be connected to the memory 20 via a bus. among them:

The processor 10 can be a single core processor or a multi-core processor. The processor 10 is internally provided with a memory management device 11 which is a hardware device for managing a memory, such as a BMU. As shown in FIG. 1, the memory management device 11 includes a controller 11a and a register 11b. Control The controller 11a is electrically connected to the register 11b. The register 11b stores one or more instructions for managing the memory, the instructions being configured to be executed by the controller 11a to implement management of the memory.

Optionally, as shown in FIG. 1 , the processor 10 may further be provided with a cache Cache 12 . The Cache 12 is used to store storage units that are loaded from the memory 20 to meet the processor 10's need for high speed access to data.

It should be noted that the memory management mode adopted by the technical solution provided by the embodiment of the present invention is a block memory management mode. The block memory management mode refers to dividing the memory into several memory blocks during memory initialization, and the granularity of subsequent memory application and memory release is a memory management mode of a memory block. Block memory management can prevent the problem of large memory fragmentation caused by repeated application and release of memory, and improve memory allocation efficiency.

It should be noted that the memory management device provided by the embodiment of the present invention is mainly applied to devices having high-speed access requirements for data, such as base station devices, routers, and switches, because of the above advantages of the block memory management mode. Wait. Taking a base station device as an example, in different communication systems, the base station device may be a base transceiver station (English: Base Transmitter Station, BTS for short), a base station (English: Node Base station, abbreviated as: Node B), and an evolved base station. (English: Evolved Node Base station, referred to as: eNB). Of course, in other possible application scenarios, the memory management device provided by the embodiment of the present invention may also be applied to any electronic device having data access requirements, including but not limited to a terminal device, a server, a transmission device, and the like. The embodiment of the invention is not limited thereto.

The technical solutions provided by the embodiments of the present invention are described and illustrated below.

Please refer to FIG. 2, which is a structural block diagram of a memory management apparatus according to an embodiment of the present invention. The memory management device can be implemented by software, hardware, or a combination of both. The memory management device can be disposed inside the processor for managing the memory. The memory management apparatus may include: a first acquisition unit 210, a creation unit 220, a second acquisition unit 230, and an allocation unit 240.

The first obtaining unit 210 is configured to acquire a memory to be allocated of a predetermined size.

The creating unit 220 is configured to create a shared memory pool according to the to-be-allocated memory acquired by the first obtaining unit 210.

The shared memory pool includes n memory blocks of a predetermined length divided by the memory to be allocated, and the shared memory pool is used to provide a memory application service for at least two memory blocks of different lengths. Each of the at least two different lengths is less than or equal to the predetermined length, n ≥ 2 and n is a positive integer.

The second obtaining unit 230 is configured to obtain a required length corresponding to the memory application, where the required length is one of the at least two different lengths.

The allocating unit 240 is configured to obtain, from the shared memory pool created by the creating unit 220, a memory block whose length is the required length acquired by the second obtaining unit 230 for allocation and use.

In summary, the memory management apparatus provided in this embodiment provides a shared memory pool, and the application memory service of at least two different lengths is provided by the shared memory pool, and when the required length corresponding to the memory application is obtained, Obtaining a memory block of the required length from the shared memory pool for allocation; solving the problem of serious memory waste and low total memory utilization in the related art; sharing a shared memory pool through memory blocks of different lengths, It can guarantee the peak demand of different length memory blocks in memory allocation, and can save memory and improve the total utilization of memory.

Please refer to FIG. 3, which is a structural block diagram of a memory management apparatus according to another embodiment of the present invention. The memory management device can be implemented by software, hardware, or a combination of both. The memory management device can be disposed inside the processor for managing the memory. The memory management apparatus may include: a first acquisition unit 210, a creation unit 220, a second acquisition unit 230, and an allocation unit 240.

The first obtaining unit 210 is configured to apply, to the operating system, a memory of a predetermined size to be allocated.

The shared memory pool includes n memory blocks of a predetermined length divided by the memory to be allocated, and the shared memory pool is used to provide a memory application service of at least two memory blocks of different lengths, in the at least two different lengths. Each length is less than or equal to the above predetermined length, n ≥ 2 and n is a positive integer.

Optionally, the at least two memory blocks of different lengths include memory blocks of different lengths of w, and the length of the i+1th memory block is q times of the length of the i-th memory block, and the The length is a predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.

The allocating unit 240 is specifically configured to:

Detecting whether there is a first memory block that is idle and has a length of required length in the shared memory pool;

Optionally, the allocating unit 240 is specifically configured to:

If the first memory block does not exist in the shared memory pool, the second memory block that is free and longer than the required length is selected from the shared memory pool;

Dividing the second memory block into m memory blocks, where the m memory blocks include memory blocks of a required length, m≥2 and m is an integer;

A memory block of a required length is selected from the m memory blocks for allocation.

Optionally, the allocating unit 240 is specifically configured to:

When there are at least two second memory blocks of different lengths in the shared memory pool, the second memory block having a length greater than and closest to the required length is selected from the shared memory pool.

Optionally, the device further includes: a third obtaining unit 250, a detecting unit 260, and a merging unit 270.

The third obtaining unit 250 is configured to obtain a memory address and a length corresponding to the memory block that needs to be released.

The detecting unit 260 is configured to detect, according to the memory address acquired by the third obtaining unit 250, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle, when the length of the memory block to be released is less than a predetermined length, The length of the target memory block is one of the at least two different lengths described above and the length of the target memory block is greater than and closest to the length of the memory block that needs to be released.

The merging unit 270 is configured to merge the memory block and other memory blocks that need to be released into the target memory block when the other memory blocks are idle, and the length of the target memory block is one of the at least two different lengths.

In addition, in the memory management apparatus provided in this embodiment, when there is no memory block of a required length in the shared memory pool in the memory allocation, the memory of the required length is divided by the memory block whose length is longer than the required length. The block is allocated, and the above-mentioned variable-length block memory allocation mode is adopted, so that the shared memory pool can provide memory application services of a plurality of block memorys of different lengths, and the allocation process is flexible. effect.

In addition, the memory management apparatus provided in this embodiment, when there are at least two second memory blocks of different lengths in the shared memory pool, also selects the idle, longer than, and closest to the required length from the shared memory pool. Two memory blocks can improve the reliability and flexibility of memory allocation to cope with subsequent different memory application requirements.

In addition, the memory management device provided by the embodiment further combines the memory blocks with small length into the memory blocks with large lengths, and ensures that there are sufficient and large free memory blocks in the shared memory pool, so as to be different for subsequent The memory application requirements provide guarantees to ensure the reliability and efficiency of memory allocation.

It should be noted that, when the memory management device provided by the foregoing embodiment performs memory management, only the division of each functional unit described above is used as an example. In actual applications, the function allocation may be completed by different functional units as needed. The internal structure of the device is divided into different functional units to complete all or part of the functions described above. In addition, the memory management device provided by the foregoing embodiment is the same as the method embodiment of the memory management method provided in the following embodiments. For details, refer to the method embodiment, and details are not described herein again.

Please refer to FIG. 4, which is a schematic structural diagram of a memory management apparatus according to still another embodiment of the present invention. The memory management device 400 may be a hardware device, such as a BMU, disposed inside the processor for managing the memory. The memory management device 400 can include a controller 410 and a register 420. among them:

The register 420 is configured to store one or more instructions for implementing a memory management method, the instruction comprising:

Obtaining a predetermined size of memory to be allocated;

Creating a shared memory pool according to the memory to be allocated, where the shared memory pool includes n memory blocks of a predetermined length divided by the memory to be allocated, and the shared memory pool is used for providing memory requests of at least two memory blocks of different lengths Serving, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

Obtaining a length of the requirement corresponding to the memory application, where the required length is one of the at least two different lengths;

Obtaining a memory block of the length of the above requirement from the shared memory pool for allocation;

The controller 410 is configured to execute the above instructions.

In an alternative embodiment provided based on the embodiment illustrated in Figure 4, the register 420 also stores instructions for performing the following operations:

The controller 410 is also operative to execute the above instructions.

When the first memory block does not exist in the shared memory pool, select a second memory block that is free and longer than the required length from the shared memory pool;

Allocating a memory block of a required length from the m memory blocks for allocation and use;

The controller 410 is also operative to execute the above instructions.

When there are at least two second memory blocks of different lengths in the shared memory pool, select a second memory block that is free from the shared memory pool and has a length greater than and closest to the required length;

The controller 410 is also operative to execute the above instructions.

When the length of the memory block to be released is less than a predetermined length, detecting, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are free, and the length of the target memory block is at least two different lengths. And the length of the target memory block is greater than and closest to the length of the memory block that needs to be released;

If other memory blocks are idle, the memory blocks and other memory blocks that need to be released are merged into the target memory block, and the length of the target memory block is one of the at least two different lengths;

The controller 410 is also operative to execute the above instructions.

In an optional embodiment provided by the embodiment shown in FIG. 4, the at least two different lengths of memory blocks include w-level memory blocks of different lengths, and the length of the i+1th-level memory block is the i-th memory block. q times the length, the length of the w-th memory block is a predetermined length, w ≥ 2, 1 ≤ i ≤ w-1, q ≥ 2 and w, i, q are integers.

In summary, the memory management apparatus provided in this embodiment allocates a length to a memory block of a length greater than a required length when a memory block of a required length does not exist in the shared memory pool during memory allocation. The length of the memory block is allocated, and the above-mentioned variable-length block memory allocation mode is adopted, so that the shared memory pool can provide memory application services of a plurality of different lengths of block memory, and the allocation process is flexible and efficient.

The following are embodiments of the method of the present invention, each of which corresponds to the above apparatus embodiment. For details not disclosed in the embodiment of the device of the present invention, please refer to the method embodiment of the present invention.

Please refer to FIG. 5, which is a flowchart of a method for a memory management method according to an embodiment of the present invention. In this embodiment, the memory management method is applied to the memory management device in the implementation environment shown in FIG. 1, and the memory management device may be a BMU provided inside the processor. The memory management method can include the following steps:

Step 502: Acquire a memory of a predetermined size to be allocated.

Step 504: Create a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the memory to be allocated, and the shared memory pool is used to provide at least two memory blocks of different lengths. The memory application service, each of the at least two different lengths being less than or equal to the predetermined length, n ≥ 2 and n being a positive integer.

Step 506: Acquire a required length corresponding to the memory application, where the required length is one of the at least two different lengths.

Step 508: Obtain a memory block with a length of the required length from the shared memory pool for allocation.

In summary, the memory management method provided in this embodiment provides a shared memory pool, and the application memory service of at least two different lengths is provided by the shared memory pool, and when the required length corresponding to the memory application is obtained, Obtaining a memory block of the required length from the shared memory pool for allocation; solving the problem of serious memory waste and low total memory utilization in the related art; sharing a shared memory pool through memory blocks of different lengths, It can guarantee the peak demand of different length memory blocks in memory allocation, and can save memory and improve the total utilization of memory.

Please refer to FIG. 6A, which is a flowchart of a method for a memory management method according to another embodiment of the present invention. In this embodiment, the memory management method is applied to the memory management device in the implementation environment shown in FIG. 1, and the memory management device may be a BMU provided inside the processor. The memory management method can include the following steps:

Step 601: Acquire a memory of a predetermined size to be allocated.

The memory management device initializes the memory through steps 601 and 602.

First, the memory management device itself requests a predetermined size of memory to be allocated to the operating system, or applies a predetermined size of memory to be allocated to the operating system through software. The predetermined size may be an empirical value preset according to actual needs. For example, the predetermined size may be set in advance according to the peak usage of the memory blocks of various lengths required for the memory application; and/or the predetermined size may also be set in advance according to the size of the physical memory managed by the operating system.

In addition, under normal circumstances, the predetermined size corresponding to the memory to be allocated provided by the operating system to the memory management device is smaller than the size of the physical memory managed by the operating system. For example, if the size of the physical memory managed by the operating system is M, the operating system can provide the memory of size N to the memory management device as an allocatable memory, where M>N. The M-N memory reserved by the operating system is the memory required for the operating system to operate normally.

Step 602: Create a shared memory pool according to the memory to be allocated.

After that, the memory management device creates a shared memory pool according to the memory to be allocated obtained by the application. The shared memory pool includes n memory blocks of a predetermined length divided by the memory to be allocated, n≥2 and n is a positive integer. The shared memory pool is used to provide memory for at least two memory blocks of different lengths To apply for a service, each of the at least two different lengths is less than or equal to the predetermined length. For example, when the predetermined length is 4X, the shared memory pool can provide memory application services for memory blocks of different lengths such as X, 2X, and 4X. For another example, when the predetermined length is 5X, the shared memory pool can provide memory application services for memory blocks of different lengths such as X, 2X, 3X, 4X, and 5X.

Different from the memory management method provided by the background art, in the memory management method provided by the background art, when the memory management device needs to provide a memory application service of a memory block of different lengths, it needs to create w Memory pool, w≥2 and w is an integer. For example, as shown in FIG. 6B, if the memory management method provided by the background technology is used, when the memory management device needs to provide a memory application service of three different lengths of memory blocks of length X, 2X, and 4X, it needs to be created. 3 memory pools, such as memory pool 1, memory pool 2, and memory pool 3 in Figure 6B. The memory pool 1 includes n ₁ memory blocks of length X, and the memory pool 2 includes n ₂ memory blocks of length 2X, and the memory pool 3 includes n ₃ memory blocks of length 4X.

In this embodiment, when the memory management device needs to provide the memory application service of the memory blocks of different lengths, it only needs to create a shared memory pool, w≥2 and w is an integer. For example, as shown in FIG. 6C, the memory management device creates a shared memory pool in which the memory management device creates a memory application service with memory modules of different lengths of X, 2X, and 4X. Includes n memory blocks of length 4X. In other words, in the embodiment, when the memory management device needs to provide a memory application service for a plurality of memory blocks of different lengths, the memory management device can present multiple memory pools externally, and only one memory pool needs to be maintained in the pair.

Next, the memory allocation process is introduced through steps 603 and 604:

Step 603: Acquire a required length corresponding to the memory application.

The memory management device provides memory application services of different lengths of block memory to external software and/or hardware. The external software and/or hardware may apply to the memory management device for a memory block of a required length; correspondingly, the memory management device obtains the required length corresponding to the memory application. Wherein, the required length is one of the above two different lengths.

For example, referring to FIG. 6C, the memory management device can externally present three memory pools, which are assumed to be Pool A, Pool B, and Pool C, respectively. Among them, Pool A corresponds to a memory block of length X, Pool B corresponds to a memory block of length 2X, and Pool C corresponds to a memory block of length 4X. When external software and/or hardware needs to apply for a memory block of length X, access Pool A; when external software and/or hardware needs to apply for a memory block of length 2X, access Pool B; when external software and / Or when the hardware needs to apply for a memory block of length 4X, access Pool C. Correspondingly, the memory management device can be based on the outside The memory pool accessed by the software and/or hardware determines the length of the request for the memory request.

Step 604: Obtain a memory block of the length of the required length from the shared memory pool for allocation.

Since only one shared memory pool is maintained in the memory management device, when the memory management device obtains the required length, regardless of the required length, the memory management device obtains a memory block of a required length from the shared memory pool. Assigned for use.

Specifically, as shown in FIG. 6D, this step may include the following sub-steps:

Step 604a: Detect whether there is a first memory block that is idle and has a length of required length in the shared memory pool.

The memory management device can use different identifiers to distinguish whether the memory block is free. When the memory management device obtains the required length corresponding to the memory application, it detects whether there is a first memory block that is free and has a length of required length in the shared memory pool. Referring to FIG. 6C, for example, when the required length is X, the memory management device detects whether there is a free memory block of length X in the shared memory pool; for example, when the required length is 2X, the memory management device detects the shared memory. Whether there is a free 2X memory block in the pool, and so on.

If the first memory block exists in the shared memory pool, the following step 604b is performed; otherwise, the following steps 604c to 604e are performed.

In step 604b, the first memory block is allocated for use.

When there is a first memory block that is free and has a length of required length in the shared memory pool, the memory management device allocates the first memory block. Optionally, when the number of the first memory blocks that meet the foregoing requirements is multiple, the memory management device selects one of the first memory blocks for allocation and use.

Step 604c: Select, from the shared memory pool, a second memory block that is idle and has a length greater than a required length.

When there is no idle first memory block of the required length in the shared memory pool, the memory management device selects a second memory block that is free and longer than the required length from the shared memory pool. Referring to FIG. 6C, for example, when the required length is X, and there is no free memory block of length X in the shared memory pool, the memory management device detects whether there is free and 2X or 4X in the shared memory pool. For example, when the required length is 2X, and there is no free memory block with a length of 2X in the shared memory pool, the memory management device detects whether there is a free memory block of 4X in the shared memory pool. And so on.

Optionally, the memory management device may perform the following steps before performing step 604c above: When there is no idle memory module of the required length in the shared memory pool, it is detected whether there is a second memory block that is free and longer than the required length in the shared memory pool; if there is a requirement in the shared memory pool that meets the above requirements The second memory block executes step 604c above; otherwise, the response to the memory allocation failure is fed back. The reason that the second memory block that meets the foregoing requirement does not exist in the shared memory pool may include: the required length is the maximum length of the memory block that the shared memory pool can provide, and there is no idle in the shared memory pool. And the length is the first memory block of the required length; or, the shared memory pool has a memory block whose length is longer than the required length, but these memory blocks are in use.

Step 604d, the second memory block is divided into m memory blocks, where the m memory blocks include memory blocks of a required length, m≥2 and m is an integer.

The memory management device divides the selected second memory block into m memory blocks, and the m memory blocks include at least one memory block of a required length. For example, referring to FIGS. 6C and 6E, it is assumed that there are n memory blocks of length 4X in the shared memory pool after initializing the configuration. When the required length of the first memory application is X, the memory management device may select a memory block of length 4X and divide it into three memory blocks (including two memory blocks 61 of length X, 62 and 1 memory block 63) of length 2X.

Step 604e: Select a memory block of a required length from the m memory blocks for allocation and use.

The memory management device selects a memory block of a required length from the divided m memory blocks for allocation. Optionally, when there are multiple memory blocks of a required length in the obtained m memory blocks, the memory management device selects a memory block whose length is a required length. For example, for the first memory application of the above example, the memory management device selects one memory block of length X from the three memory blocks obtained by the partitioning (the memory of length X shown by the oblique line in FIG. 6E). Block 61). For example, if the required length of the second memory application is 2X, the memory management device can detect that there is a free memory block with a length of 2X in the shared memory pool, and allocate the memory block of length 2X. (The memory block 63 having a length of 2X as indicated by a hatched line in Fig. 6E).

Optionally, for the foregoing step 604c, when there are at least two second memory blocks of different lengths in the shared memory pool, the memory management device selects, from the shared memory pool, the second, the length that is greater than and closest to the required length. Memory block. For example, when the demand length is X and the second memory block of length 2X and 4X exists in the shared memory pool, the memory management device selects the second memory block of length 2X. By selecting an idle second memory block that is larger than the length and closest to the required length, the reliability and flexibility of the memory allocation can be improved to cope with subsequent different memory application requirements.

For example, when the memory request corresponds to a demand length of X, and the shared memory pool still has an idle 2X memory block and a free 4X memory block. If the memory management device selects a memory block of length 4X for division (assuming that it is divided into two memory blocks of length X and one memory block of length 2X), the remaining free memory in the shared memory pool after this allocation The memory block includes one memory block of length X and two memory blocks of length 2X. Then, without other memory blocks being released, the shared memory pool cannot continue to provide a memory block of length 4X. If the memory management device selects a memory block of length 2X for partitioning (assuming that it is divided into two memory blocks of length X), the remaining free memory blocks in the shared memory pool after the allocation include one length X. The memory block and a memory block of length 4X, then the shared memory pool can continue to provide memory blocks of length X, 2X or 4X without other memory blocks being released.

Optionally, at least two different lengths of memory blocks provided by the memory management device may include memory blocks of different lengths of w levels. The length of the i+1th-level memory block is q times the length of the i-th memory block, and the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 And w, i, q are integers. For example, the at least two different lengths mentioned above include: X, 2X, 4X, 8X, and the like. As another example, the at least two different lengths described above include X, 3X, 9X, and the like.

Of course, this embodiment does not limit other possible implementations. For example, in other possible implementations, the lengths between adjacent levels of memory blocks may not have the same multiple relationship. For example, the at least two different lengths mentioned above include: X, 4X, 7X, and the like. In this way, when a memory block of length 4X needs to be divided, it can only be divided into four memory blocks of length X. When it is necessary to divide the memory block of length 7X, it can only be divided into 1 A memory block of length 4X and three memory blocks of length X will in the long run lead to a large number of memory blocks with a small length (such as a memory block of length X) remaining in the shared memory pool, eventually resulting in a shared memory pool. Respond to the application requirements of larger memory blocks. Therefore, it is only a preferred implementation that the lengths of the adjacent memory blocks have the same multiple relationship, which makes the shared memory pool more reasonable and flexible when partitioning the memory blocks, and prevents memory fragmentation. Subsequent different memory application requirements.

In this embodiment, a shared memory pool is shared by memory blocks of different lengths, which can ensure the peak demand of different length memory blocks in memory allocation, and can save memory and improve the total utilization of memory. Specifically, it is assumed that the memory management device needs to provide a memory application service of a memory block of different lengths. If the memory management method provided by the background technology is used, at least the memory size to be allocated to the operating system is required.

Where L _k represents the length of the kth length of the memory block, and n _k represents the peak demand quantity of the kth length of the memory block, w ≥ 2 and w is an integer. According to the memory management method provided in this embodiment, the size N of the memory to be allocated that the memory management device applies to the operating system is:

In a specific example, referring to FIG. 6B, if the memory management method provided by the background art is adopted, it is assumed that the memory blocks corresponding to the three different lengths of X, 2X, and 4X have Y peaks, and the memory management device needs at least The size of the memory to be allocated to the operating system is N=XY+2XY+4XY=7XY, so as to ensure that the memory allocation can cope with the peak demand of memory blocks of different lengths. Referring to FIG. 6C, if the memory management method provided in this embodiment is used, the memory management device only needs to apply for the memory to be allocated with the size of 4XY~5XY to the operating system, so as to ensure that the memory allocation can cope with the peak demand of the memory blocks of different lengths. . It can be seen that, compared with the memory management method provided by the background technology, the memory management method provided in this embodiment can save about 30% to 40% of memory under the premise of ensuring the same memory allocation requirement. Especially for embedded systems, it can fully meet the memory capacity and cost requirements of embedded systems.

In addition, in the memory management method provided in this embodiment, when there is no memory block of a required length in the shared memory pool in the memory allocation, the memory block of the required length is divided into the memory blocks of the length longer than the required length. The allocation is performed by using the above-mentioned variable-length block memory allocation method, so that the shared memory pool can provide memory application services of a plurality of block memorys of different lengths, and the allocation process is flexible and efficient.

In addition, the memory management method provided in this embodiment, when there are at least two second memory blocks of different lengths in the shared memory pool, also selects the idle, longer than, and closest to the required length from the shared memory pool. Two memory blocks can improve the reliability and flexibility of memory allocation to cope with subsequent different memory application requirements.

Please refer to FIG. 7A/7B, which is a flowchart of a method for a memory management method according to still another embodiment of the present invention. As shown in FIG. 7A, the above step 604a of the embodiment shown in FIG. 6A may include the following sub-steps:

Step 604a1: Detect whether a first memory block exists in a specified memory block set of the shared memory pool.

Step 604a2, if present, selects the first memory block from the specified set of memory blocks for allocation use.

The specified memory block set includes at least one memory block, and the memory block included in the specified memory block set is used to be preferentially selected in the memory allocation. The memory block included in the specified memory block set can be pre-selected, for example, after the shared memory pool is created, several memory blocks are selected, and after the creation of the shared memory pool, a number of memory blocks are selected at the end. Alternatively, the memory blocks included in the specified memory block set can also be determined during the memory allocation process, such as controlling a number of memory blocks to be preferentially selected by means of a stack.

In this embodiment, when the required length corresponding to the memory application is obtained, the memory management apparatus detects whether there is a first memory block that is free and has a length of a required length in the specified memory block set. When there is a first memory block in the specified memory block set that satisfies the above requirement, the memory management device preferentially selects a first memory block from the specified memory block set for allocation. The memory management device allows a certain portion of the memory block to be used at a high frequency by precisely controlling the allocation of the memory block, which is advantageous for improving the read hit rate and system performance.

Similarly, as shown in FIG. 7B, the above step 604c of the embodiment shown in FIG. 6A may include the following sub-steps:

Step 604c1: Detect whether a second memory block exists in the specified memory block set of the shared memory pool.

Step 604c2, if present, selects a second memory block from the specified set of memory blocks for allocation.

In this embodiment, when there is no idle first memory block of the required length in the shared memory pool, the memory management apparatus detects whether there is a second memory block that is idle and has a length greater than the required length in the specified memory block set. . When there is a second memory block in the specified memory block set that satisfies the above requirements, the memory management device preferentially selects a second memory block from the specified memory block set for allocation. The memory management device allows a certain portion of the memory block to be used at a high frequency by precisely controlling the allocation of the memory block, which is advantageous for improving the read hit rate and system performance. In addition, when there is no second memory block in the specified memory block set that satisfies the above requirement, the memory management device acquires a second memory block that satisfies the above requirement from other memory blocks in the shared memory pool for allocation.

It should be noted that when there is no idle first memory block of the required length in the specified memory block set, the memory management device can obtain a first one that satisfies the above requirements from other memory blocks in the shared memory pool. The memory block is allocated for use; or the memory management device can perform the above Step 604c1 is not specifically limited in this embodiment.

In summary, the memory management method provided by the embodiment improves the read hit rate and the system by accurately controlling the allocation and use of the memory block when the memory is allocated, so that a certain portion of the memory block is used at a high frequency. performance.

Next, the memory release process will be described by the embodiment shown in FIG. 8:

Please refer to FIG. 8 , which is a flowchart of a method for a memory management method according to still another embodiment of the present invention. In the memory management method, after step 602 of the embodiment shown in FIG. 6A, the method further includes:

Step 605: Acquire a memory address and a length corresponding to the memory block that needs to be released.

The memory management device obtains the memory address and length corresponding to the memory block that needs to be released. The memory address is used to identify and distinguish different memory blocks, and different memory blocks correspond to different memory addresses.

Step 606: When the length of the memory block to be released is less than a predetermined length, detect, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle.

The length of the target memory block is one of the at least two different lengths, and the length of the target memory block is greater than and closest to the length of the memory block that needs to be released.

Step 607: If other memory blocks are idle, merge the memory blocks and other memory blocks that need to be released into the target memory block.

For example, referring to FIG. 6E, when the memory block to be released is the memory block 61 of length X, the memory management device detects whether other memory blocks in the target memory block to which it belongs are free according to the memory address of the memory block 61. In FIG. 6E, the target memory block is a memory block of length 2X composed of the memory block 61 and the memory block 62. If the memory management device detects that the memory block 62 is free, the memory management device combines the memory block 61 and the memory block 62 into a memory block of length 2X. Further, if the memory management device detects that the memory block 62 is in use, the flow is terminated.

Further, after the memory management device merges the target memory block, it can continue to detect whether the target memory block and other memory blocks can be merged into a higher-level (that is, a longer-length) memory block; if so, continue The memory block merging step is performed until a memory block of the above predetermined length is obtained. For example, in FIG. 6E, if the memory block 63 is also idle, the memory management apparatus may further merge the memory block 63 of the length 2X obtained by the combination into the memory block 63 into a memory block of length 4X.

In addition, when the length of the memory block to be released is equal to the predetermined length, the flow is ended. Since the predetermined length is the maximum length of the memory block that the shared memory pool can provide, the length of the memory block that needs to be freed When equal to the predetermined length, the memory management device does not need to perform the memory block merging step.

In summary, the memory management method provided in this embodiment also combines a memory block with a small length into a memory block with a large length, and tries to ensure that there are sufficient and large free memory blocks in the shared memory pool, so as to Subsequent different memory application requirements provide guarantees to ensure the reliability and efficiency of memory allocation.

It can be understood that the memory management apparatus provided in any of the embodiments of FIG. 2 to FIG. 4 can perform the memory management method provided in any of the embodiments of FIG. 5, FIG. 6A, FIG. 7A, FIG. 7B, and FIG. For example, the specific functions and workflows of the various units or components may be referred to in the related parts of the method embodiments, and the descriptions of the various embodiments provided by the present invention may also be referred to each other.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

A memory management device, characterized in that the device comprises:

a first acquiring unit, configured to acquire a memory of a predetermined size to be allocated;

a creating unit, configured to create a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the to-be-allocated memory, where the shared memory pool is used to provide a memory application service of at least two memory blocks of different lengths, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

a second acquiring unit, configured to acquire a required length corresponding to the memory application, where the required length is one of the at least two different lengths;

And an allocating unit, configured to obtain, from the shared memory pool, a memory block of a length of the required length for allocation.
The device according to claim 1, wherein the allocating unit is specifically configured to:

Detecting, in the shared memory pool, whether there is a first memory block that is idle and has a length of the required length;

If the first memory block exists in the shared memory pool, the first memory block is allocated for use.
The device according to claim 2, wherein the allocating unit is further configured to:

If the first memory block does not exist in the shared memory pool, select a second memory block that is idle and has a length greater than the required length from the shared memory pool;

Dividing the second memory block into m memory blocks, where the m memory blocks include a memory block having a length of the required length, m≥2 and m is an integer;

And selecting, from the m memory blocks, the memory block whose length is the required length for allocation and use.
The device according to claim 3, wherein the allocating unit is further configured to:

When there are at least two different lengths of the second memory block in the shared memory pool, an idle second memory block having a length greater than and closest to the required length is selected from the shared memory pool.
The device according to any one of claims 1 to 4, wherein the device further comprises:

a third acquiring unit, configured to acquire a memory address and a length corresponding to the memory block that needs to be released;

a detecting unit, configured to detect, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle according to the memory address, when the length of the memory block to be released is less than the predetermined length, The length of the target memory block is one of the at least two different lengths and the length of the target memory block is greater than the length of the memory block to be released;

a merging unit, configured to merge the memory block to be released and the other memory block into the target memory block when the other memory block is idle, the length of the target memory block being the at least two different One of the lengths.
The device according to any one of claims 1 to 5, wherein the at least two memory blocks of different lengths comprise memory blocks of different lengths of w levels, and the length of the i+1th memory block is the i-th level. The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.
A memory management device, characterized in that the device comprises: a controller and a register;

The register is configured to store one or more instructions for implementing a memory management method;

The method includes:

Obtaining a predetermined size of memory to be allocated;

Creating a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the to-be-allocated memory, where the shared memory pool is used to provide at least two different lengths. Memory application service of the memory block, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

Obtaining a required length corresponding to the memory application, where the required length is one of the at least two different lengths;

Obtaining, by using the shared memory pool, a memory block of a length of the required length for allocation and use;

The controller is operative to execute the instructions.
The apparatus according to claim 7, wherein said register is further stored for execution The instructions for the following operations:

Detecting, in the shared memory pool, whether there is a first memory block that is idle and has a length of the required length;

If the first memory block exists in the shared memory pool, the first memory block is allocated for use;

The controller is also operative to execute the instructions.
The apparatus of claim 8 wherein said register further stores instructions for performing the following operations:

When the first memory block does not exist in the shared memory pool, select a second memory block that is idle and has a length greater than the required length from the shared memory pool;

Dividing the second memory block into m memory blocks, where the m memory blocks include a memory block having a length of the required length, m≥2 and m is an integer;

And selecting, from the m memory blocks, the memory block whose length is the required length for allocation and use;

The controller is also operative to execute the instructions.
The apparatus of claim 9 wherein said register further stores instructions for performing the following operations:

When there are at least two different memory blocks of different lengths in the shared memory pool, select a second memory block that is free from the shared memory pool and has a length greater than and closest to the required length;

The controller is also operative to execute the instructions.
The apparatus according to any one of claims 7 to 10, characterized in that said register further stores instructions for performing the following operations:

Get the memory address and length corresponding to the memory block that needs to be released;

When the length of the memory block to be released is less than the predetermined length, detecting, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle, the length of the target memory block Is one of the at least two different lengths and the length of the target memory block is greater than a length of the memory block to be released;

If the other memory block is idle, the memory block that needs to be released is combined with the other memory block And for the target memory block, the length of the target memory block is one of the at least two different lengths;

The controller is also operative to execute the instructions.
The device according to any one of claims 7 to 11, wherein the at least two memory blocks of different lengths comprise memory blocks of different lengths of w, and the length of the i+1th memory block is the i-th level. The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.
A memory management method, the method comprising:

Obtaining a predetermined size of memory to be allocated;

Creating a shared memory pool according to the to-be-allocated memory, where the shared memory pool includes n memory blocks of a predetermined length divided by the to-be-allocated memory, where the shared memory pool is used to provide at least two different lengths. Memory application service of the memory block, each of the at least two different lengths being less than or equal to the predetermined length, n≥2 and n being a positive integer;

Obtaining a required length corresponding to the memory application, where the required length is one of the at least two different lengths;

Obtaining a memory block of the required length from the shared memory pool for allocation.
The method according to claim 13, wherein the obtaining, by using the shared memory pool, a memory block of a length of the required length for allocation, comprises:

Detecting, in the shared memory pool, whether there is a first memory block that is idle and has a length of the required length;

If the first memory block exists in the shared memory pool, the first memory block is allocated for use.
The method according to claim 14, wherein after detecting whether the first memory block of the required length is available in the shared memory pool, the method further includes:

If the first memory block does not exist in the shared memory pool, select a second memory block that is idle and has a length greater than the required length from the shared memory pool;

Dividing the second memory block into m memory blocks, where the m memory blocks include a memory block having a length of the required length, m≥2 and m is an integer;

And selecting, from the m memory blocks, the memory block whose length is the required length for allocation and use.
The method according to claim 15, wherein the selecting from the shared memory pool a second memory block that is free and longer than the required length comprises:

When there are at least two different lengths of the second memory block in the shared memory pool, an idle second memory block having a length greater than and closest to the required length is selected from the shared memory pool.
The method according to any one of claims 13 to 16, wherein the method further comprises:

Get the memory address and length corresponding to the memory block that needs to be released;

When the length of the memory block to be released is less than the predetermined length, detecting, according to the memory address, whether other memory blocks in the target memory block to which the memory block to be released belongs are idle, the length of the target memory block Is one of the at least two different lengths and the length of the target memory block is greater than and closest to the length of the memory block that needs to be released;

If the other memory block is idle, the memory block that needs to be released and the other memory block are merged into the target memory block.
The method according to any one of claims 13 to 17, wherein the at least two memory blocks of different lengths comprise memory blocks of different lengths of w, and the length of the i+1th memory block is the i-th level. The length of the memory block is q times, the length of the w-th memory block is the predetermined length, w≥2, 1≤i≤w-1, q≥2 and w, i, q are integers.