![]() ![]() So it is very possible for an application to specify they would like to map a file at the 29GB address offset, and everything from the lower address up to the now memory mapped file at 29GB is empty address space. NOTE: when memory mapping a file, the application has the opiton of specifying where in the virtual address space it would like the file to be mapped. Or an application can memory map a bunch of smaller files, but if you have enough of them then that adds up to a lot of virtual address space. If the file is huge, then the virtual address space needed to map it will be large as well. Some might be memory mapped files, where an explicit file accessed as if it is part of memory (vs doing read/write operations). Then comes the data used by the application. Also these add-ons are most likely mapped into the virtual address space with gaps between them and other code. ![]() And the disk for this comes from the add-on files. If the application has loadable modules, such as browser or photoshop add-ons, then these get mapped into virtual address space. Again the disk used are the shared library and framework files. The application code is mapped into this space, and the disk used for this is the actual executable code.Īll the shared libraries and application frameworks that the application uses are mapped into the virtual address space, often times with empty gaps in the address space. Virtual Memory is often times filled with holes of unused address space. Virtual Memory information is mostly meaningless, except to software developers and very few of them. so 30 GB+ is excessive, right? Or, has "virtual memory" taken on a new meaning in Leopard, or OS X. ![]() Thanks for the reply! My understanding is that virtual memory uses hard drive space. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |