-nomap: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
[[Category:OFP Startup Parameters]] | [[Category:OFP Startup Parameters]] | ||
One of the [[:Category:OFP Startup Parameters|OFP Startup Parameters]] '''-nomap''' forces '''OFP''' to avoid memory mapping for file access. | One of the [[:Category:OFP Startup Parameters|OFP Startup Parameters]], '''-nomap''' forces '''OFP''' to avoid memory mapping for file access. | ||
While memory mapping is very efficient from a performance point of view, it can quickly fill all available virtual space, causing various memory allocation errors or even driver crashes or freezes. | While memory mapping is very efficient from a performance point of view, it can quickly fill all available virtual space, causing various memory allocation errors or even driver crashes or freezes. | ||
This switch is especially important for users with display adapters with large amounts of VRAM (128MB or more), which reserves a lot of virtual addresses in the application address space for themselves. | This switch is especially important for users with display adapters with large amounts of VRAM (128MB or more), which reserves a lot of virtual addresses in the application address space for themselves. | ||
Revision as of 15:22, 22 April 2006
One of the OFP Startup Parameters, -nomap forces OFP to avoid memory mapping for file access.
While memory mapping is very efficient from a performance point of view, it can quickly fill all available virtual space, causing various memory allocation errors or even driver crashes or freezes.
This switch is especially important for users with display adapters with large amounts of VRAM (128MB or more), which reserves a lot of virtual addresses in the application address space for themselves.