# Heap Memory Management - [Basic Concepts](#section449414395916) - [Working Principles](#section465085575911) - [Development Guidelines](#section577019272015) - [When to Use](#section326917198583) - [Available APIs](#section1032331584) - [How to Develop](#section07271773592) - [Development Example](#section84931234145913) - [Verification](#section165233233917) ## Basic Concepts Memory management module, one of the core modules of the OS, manages the memory resources of the system. Memory management involves memory initialization, allocation, and release. The heap memory management of the OpenHarmony LiteOS-A provides functions such as memory initialization, allocation, and release. While the OS is running, the heap memory management module manages the memory usage of users and the OS by allocating and releasing memory. This helps achieve the optimal memory usage and usage efficiency and minimize memory fragments. ## Working Principles Heap memory management allows memory blocks of any size to be allocated from a large contiguous memory \(memory pool or heap memory\) configured in the system based on user demands when memory resources are sufficient. The memory block can be released for further use when not required. Heap memory management is a type of dynamic memory management. Compared with static memory management, dynamic memory management allows memory allocation on demand but causes fragmentation of memory. The heap memory of the OpenHarmony LiteOS-A has optimized the memory space partitioning based on the Two-Level Segregate Fit \(TLSF\) algorithm to achieve higher performance and minimize fragmentation. [Figure 1](#fig14558185217397) shows the core algorithm of the heap memory management. **Figure 1** Heap memory core algorithm ![](figure/heap-memory-core-algorithm.png "heap-memory-core-algorithm") Multiple free lists are used for management based on the size of the free memory block. The free memory blocks are divided into two parts: \[4, 127\] and \[27, 231\], as indicated by the size class in the above figure. 1. The memory in the range of \[4, 127\] \(lower part in the figure\) is equally divided into 31 parts. The size of the memory block corresponding to each part is a multiple of 4 bytes. Each part corresponds to a free list and a bit that indicates whether the free list is empty. The value **1** indicates that the free list is not empty. There are 31 bits corresponding to the 31 memory parts in the range of \[4, 127\]. 2. The memory greater than 127 bytes is managed in power of two increments. The size of each range is \[2^n, 2^\(n+1\) -1\], where n is an integer in \[7, 30\]. This range is divided into 24 parts, each of which is further divided into 8 second-level \(L2\) ranges, as shown in Size Class and Size SubClass in the upper part of the figure. Each L2 range corresponds to a free list and a bit that indicates whether the free list is empty. There are a total of 192 \(24 x 8\) L2 ranges, corresponding to 192 free lists and 192 bits. For example, insert 40-byte free memory to a free list. The 40-byte free memory corresponds to the 10th free list in the range of \[40, 43\], and the 10th bit indicates the use of the free list. The system inserts the 40-byte free memory to the 10th free list and determines whether to update the bitmap flag. When 40-byte memory is requested, the system obtains the free list corresponding to the memory block of the requested size based on the bitmap flag, and then obtains a free memory node from the free list. If the size of the allocated node is greater than the memory requested, the system splits the node and inserts the remaining node to the free list. If 580-byte free memory needs to be inserted to a free list, the 580-byte free memory corresponds to the 47th \(31 + 2 x 8\) free list in L2 range \[2^9, 2^9+2^6\], and the 47th bit indicates the use of the free list. The system inserts the 580-byte free memory to the 47th free list and determines whether to update the bitmap flag. When 580-byte memory is requested, the system obtains the free list corresponding to the memory block of the requested size based on the bitmap flag, and then obtains a free memory node from the free list. If the size of the allocated node is greater than the memory requested, the system splits the node and inserts the remaining node to the free list. If the corresponding free list is empty, the system checks for a free list meeting the requirements in a larger memory range. In actual application, the system can locate the free list that meets the requirements at a time. The following figure shows the memory management structure. **Figure 2** Dynamic memory management structure ![](figure/dynamic-memory-management-structure-20.png "dynamic-memory-management-structure-20") - Memory pool header The memory pool header contains the memory pool information, bitmap flag array, and free list array. The memory pool information includes the start address of the memory pool, total size of the heap memory, and attributes of the memory pool. The bitmap flag array consists of seven 32-bit unsigned integers. Each bit indicates whether the free list is inserted with free memory block nodes. The free list contains information about 223 free memory head nodes. The free memory head node information contains a memory node header and information about the previous and next nodes in the free list. - Memory pool nodes There are three types of nodes: free node, used node, and end node. Each memory node maintains the size and use flag of the memory node and a pointer to the previous memory node in the memory pool. The free nodes and used nodes have a data area, but the end node has no data area. ## Development Guidelines ### When to Use Heap memory management is mainly used to dynamically allocate and manage memory ranges requested by users. Heap memory management is mainly used in scenarios where users need to use memory blocks of different sizes. You can obtain a memory block of a specified size by using a dynamic memory application function of the operating system. Once the memory is used up, the memory release function is used to release the occupied memory so that the memory can be reused. ### Available APIs The following table describes APIs available for OpenHarmony LiteOS-A heap memory management. For more details about the APIs, see the API reference. **Table 1** Heap memory management APIs

Category

API

Description

Initializing or deleting a memory pool

LOS_MemInit

Initializes a dynamic memory pool of the specified size.

LOS_MemDeInit

Deletes a memory pool. It is valid only when LOSCFG_MEM_MUL_POOL is enabled.

Allocating or releasing dynamic memory

LOS_MemAlloc

Allocates memory of the specified size from the dynamic memory pool.

LOS_MemFree

Releases the memory allocated from the specified dynamic memory.

LOS_MemRealloc

Re-allocates a memory block of the required size and copies data from the original block to the newly allocated bock. If the new memory block is successfully allocated, the original memory block will be released.

LOS_MemAllocAlign

Allocates the memory of the specified size and aligned based on the specified bytes from a dynamic memory pool.

Obtaining memory pool information

LOS_MemPoolSizeGet

Obtains the total size of the specified dynamic memory pool.

LOS_MemTotalUsedGet

Obtains the total memory usage of the specified dynamic memory pool.

LOS_MemInfoGet

Obtains the memory structure information of the specified memory pool, including the free memory, used memory, number of free memory blocks, number of used memory blocks, and maximum size of the free memory block.

LOS_MemPoolList

Prints information about all initialized memory pools in the system, including the start address, size, total free memory, used memory, maximum size of the free memory block, number of free memory blocks, and number of used memory blocks of each memory pool. It is valid only when LOSCFG_MEM_MUL_POOL is enabled.

Obtaining memory block information

LOS_MemFreeNodeShow

Prints the size and number of free memory blocks in the specified memory pool.

Checking memory pool integrity

LOS_MemIntegrityCheck

Checks the integrity of the specified memory pool. It is valid only when LOSCFG_BASE_MEM_NODE_INTEGRITY_CHECK is enabled.
>![](../public_sys-resources/icon-note.gif) **NOTE:** >- The dynamic memory module manages memory through control block structures, which consume extra memory. Therefore, the actual memory space available to users is less than the value of **OS\_SYS\_MEM\_SIZE**. >- The **LOS\_MemAllocAlign** and **LOS\_MemMallocAlign** APIs consume extra memory for memory alignment, which may cause memory loss. When the memory used for alignment is freed up, the lost memory will be reclaimed. ### How to Develop The typical development process of dynamic memory is as follows: 1. Call the **LOS\_MemInit** API to initialize a memory pool. After a memory pool is initialized, a memory pool control header and end node will be generated, and the remaining memory is marked as free nodes. The end node is the last node in the memory pool, and its size is **0**. 1. Call the **LOS\_MemAlloc** API to allocate dynamic memory of any size. The system checks whether the dynamic memory pool has free memory blocks greater than the requested size. If yes, the system allocates a memory block and returns the pointer to the memory block. If no, the system returns NULL. If the memory block allocated is greater than the requested size, the system splits the memory block and inserts the remaining memory block to the free list. 1. Call the **LOS\_MemFree** API to release dynamic memory. The released memory block can be reused. When **LOS\_MemFree** is called, the memory block will be reclaimed and marked as free nodes. When memory blocks are reclaimed, adjacent free nodes are automatically merged. ### Development Example The example below implements the following: 1. Initialize a dynamic memory pool. 2. Allocate a memory block from the dynamic memory pool. 3. Store a piece of data in the memory block. 4. Print the data in the memory block. 5. Release the memory block. The sample code is as follows: ``` #include "los_memory.h" #define TEST_POOL_SIZE (2*1024*1024) __attribute__((aligned(4))) UINT8 g_testPool[TEST_POOL_SIZE]; VOID Example_DynMem(VOID) { UINT32 *mem = NULL; UINT32 ret; /* Initialize the memory pool. */ ret = LOS_MemInit(g_testPool, TEST_POOL_SIZE); if (LOS_OK == ret) { printf("Mem init success!\n"); } else { printf("Mem init failed!\n"); return; } /* Allocate memory.*/ mem = (UINT32 *)LOS_MemAlloc(g_testPool, 4); if (NULL == mem) { printf("Mem alloc failed!\n"); return; } printf("Mem alloc success!\n"); /* Assign a value.*/ *mem = 828; printf("*mem = %d\n", *mem); /* Release memory.*/ ret = LOS_MemFree(g_testPool, mem); if (LOS_OK == ret) { printf("Mem free success!\n"); } else { printf("Mem free failed!\n"); } return; } UINT32 ExampleDynMemEntry(VOID) { UINT32 ret; TSK_INIT_PARAM_S initParam = {0}; initParam.pfnTaskEntry = (TSK_ENTRY_FUNC)Example_DynMem; initParam.usTaskPrio = 10; initParam.pcName = "Example_DynMem"; initParam.uwStackSize = LOSCFG_BASE_CORE_TSK_DEFAULT_STACK_SIZE; initParam.uwResved = LOS_TASK_STATUS_DETACHED; /* Create a task with a higher priority. The task will not be executed immediately after being created, because task scheduling is locked.*/ ret = LOS_TaskCreate(&g_taskHiID, &initParam); if (ret != LOS_OK) { LOS_TaskUnlock(); PRINTK("Example_DynMem create Failed! ret=%d\n", ret); return LOS_NOK; } PRINTK("Example_DynMem create Success!\n"); while(1){}; return LOS_OK; } ``` ### Verification The output is as follows: ``` Mem init success! Mem alloc success! *mem = 828 Mem free success! ```