碎片问题详解（Details of the debris problem）.docVIP

碎片问题详解（Details of the debris problem） Memory chip processing techniques Memory fragmentation is a very tricky issue. How to allocate memory determines whether memory chips will, when, and how to become a problem. Even when there is actually a lot of free memory in the system, memory fragments can eventually result in memory running out Situation. A system that constantly generates fragmentation of memory, however small it may be, will run out of memory as long as it is long enough. This situation is not acceptable in many embedded systems, especially in high availability systems. Some software environments, such as the OSE real-time operating system, have good tools to avoid memory fragmentation, but the choices made by individual programmers still have an impact on the final result. The fragmentation memory describes all available free memory in a system. These resources are still not used because the allocator that allocates memory makes these memory unusable. This usually happens because the free memory is different in a small, discontinuous manner. Because the allocation method determines whether the memory fragment is a problem, the memory allocator plays an important role in ensuring availability of free resources. Compile time and run time Memory allocation problems occur in many cases. Programmers can compile programs and link programs, as the structure, and set, arrays, and scalars (used as global variables, static variables or local variables) of data memory, programmers can use at run time, such as the malloc () call command to dynamically allocate memory. Memory fragmentation is not present when the memory allocation function is completed with the compiler and link-program, because the compiler knows the data life. The advantage of taking control of the data life that can be used is that the data can be superimposed in the way that the data comes in first. This makes the memory allocation program more efficient, and not the memory fragmentation. In gener