碎片问题详解（Fragmentation problem）.docVIP

碎片问题详解（Fragmentation problem） Memory fragmentation processing technology Memory fragmentation is a very difficult problem. How to allocate memory determines whether memory fragments will, when, how, and how it can become a problem. Even if there is still a lot of free memory in the system, memory fragmentation can eventually lead to memory run out Situation。 A system that constantly generates memory fragments, no matter how small the memory fragments are generated, will run out of memory as long as the time is long enough. This situation is unacceptable in many embedded systems, especially in highly available systems. Some software environments, such as OSE, have good tools for avoiding memory fragmentation, but the choices made by individual programmers still have an impact on the end result. Fragmented memory describes all the free memory that is not available in a system. These resources are still not available because the allocator responsible for allocating memory makes these memory unusable. This problem usually happens because the free memory goes out of the way in small, discontinuous ways. Because the allocation method determines whether memory fragmentation is a problem, the memory allocator plays an important role in ensuring the availability of free resources. Compile time and run time Memory allocation problems can occur in many cases. The programmer can compile and link the program, structure, union, array and scalar (used as local variables, global variables and static variables) data memory allocation, the programmer can use at run time (such as malloc) call command dynamic memory allocation. When a memory allocation function is performed with a compiler and a link program, memory fragmentation is not visible because the compiler knows about data life. Controlling the lifetime of data available, the advantage is that it allows data to be superimposed in the first in and out first. This will allow the memory allocation program to work more efficiently