.netframework computer memmgmnt memory memory_management opsys pgm_cpp programming unixbelleky%C3%B6netimi

My tags:

From Wikipedia, the free encyclopedia

This article does not cite any references or sources. Please help improve this article by adding citations to reliable sources (ideally, using inline citations). Unsourced material may be challenged and removed. (April 2008)

Memory management is the act of managing computer memory. In its simpler forms, this involves providing ways to allocate portions of memory to programs at their request, and freeing it for reuse when no longer needed. The management of main memory is critical to the computer system.

Virtual memory systems separate the memory addresses used by a process from actual physical addresses, allowing separation of processes and increasing the effectively available amount of RAM using disk swapping. The quality of the virtual memory manager can have a big impact on overall system performance.

Garbage collection is the automated allocation, and deallocation of computer memory resources for a program. This is generally implemented at the programming language level and is in opposition to manual memory management, the explicit allocation and deallocation of computer memory resources.

Contents 1 Features 1.1 Relocation 1.2 Protection 1.3 Sharing 1.4 Logical organization 1.5 Physical organization 1.6 Memory compaction 2 DOS memory managers 3 See also 4 External links

[edit] Features

Memory management systems on multi-tasking operating systems usually deal with the following issues.

[edit] Relocation

In systems with virtual memory, programs in memory must be able to reside in different parts of the memory at different times. This is because when the program is swapped back into memory after being swapped out for a while it can not always be placed in the same location. Memory management in the operating system should therefore be able to relocate programs in memory and handle memory references in the code of the program so that they always point to the right location in memory.

[edit] Protection

Processes should not be able to reference the memory for another process without permission. This is called memory protection, and prevents malicious or malfunctioning code in one program from interfering with the operation of other running programs.

[edit] Sharing

Even though the memory for different processes is protected from each other, different processes should be able to share information and therefore access the same part of memory. ...

[edit] Logical organization

Programs are often organized in modules. Some of these modules could be shared between different programs, some are read only and some contain data that can be modified. The memory management is responsible for handling this logical organization that is different from the physical linear address space. One way to arrange this organization is segmentation.

[edit] Physical organization

Memory is usually divided into fast primary storage and slow secondary storage. Memory management in the operating system handles moving information between these two levels of memory.

[edit] Memory compaction

The technique of relocating all occupied areas of memory to one end of the memory so as to get one large block of free memory space is called compaction.

Memory can be compacted under the following conditions:

1. As soon as a job terminates.
2. When a new job cannot be loaded into memory due to fragmentation.
3. At fixed time intervals.

[edit] DOS memory managers

In addition to standard memory management, the 640 KB barrier of MS-DOS and compatible systems led to the development of programs known as memory managers when PC main memories started to be routinely larger than 640 KB in the late 1980s (see conventional memory). These move portions of the operating system outside their normal locations in order to increase the amount of conventional or quasi-conventional memory available to other applications. Examples are EMM386, which was part of the standard installation in DOS's later versions, and QEMM. These allowed use of memory above the 640 KB barrier, where memory was normally reserved for RAMs, and high and upper memory.

[edit] See also

• Dynamic memory allocation
• Garbage collection
• Handle or reference
• Page table
• Paging
• Demand paging
• Pointer
• Virtual memory
• Memory management unit (MMU)

[edit] External links

• The Memory Management Reference
• Linux Memory Management
• Memory Management For System Programmers