Memory protection. Each 4k page of memory has its own access rights. In this way, memory which should not be accessed or modified at run time can be protected. Since every invalid memory access causes an exception, this feature is very useful for debugging a program with stray pointers or similar bugs.
Virtual Regions. Some programs can be mapped more efficiently in a virtual region.
RAM remapping using FillRAM. Unused pages of memory can be appended to another region. This has two advantages: regions larger than physically available can be created for program entities that must be located in consecutive address space (such as stack or heap). In addition, memory that would be wasted due to alignment restrictions without paging can be used.
Uncommitted memory support. RTTarget-32's virtual memory manager can be used only if paging is enabled.

Disadvantages of Paging

Memory overhead. The page table itself requires memory on the target system. For example, the page table for a computer with 4M of memory needs 8k. If RAM remapping is used, the page table grows to 12k.
Run-time overhead. Paging can lead to slightly slower program execution. The amount of overhead incurred depends on the program's use of memory and the CPU used. However, the overhead is hardly measurable and can be ignored on most systems.

Generally, the use of paging is recommended. The extra level of protection usually outweighs the small overhead incurred. If very low resource requirements are a major design goal, paging could be used during software development only and disabled for the production release. For applications using DLLs, paging is recommended to be able to use the virtual memory manager.

Left Advanced Topics

Choosing a Locate Method

Down Running at CPL 0 or 3