-nomap: Difference between revisions
Jump to navigation
Jump to search
(removed first link - it's in the category box and in the back button history) |
No edit summary |
||
| Line 2: | Line 2: | ||
[[Category:OFP Startup Parameters]] | [[Category:OFP Startup Parameters]] | ||
'''-nomap''' forces | '''-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 13:54, 23 April 2006
-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.