Memory Limits in Sectin View Mapping
in [Device Drivers]
|
From: Alon on 16 Jun 2005 12:30 Hi! According to the MSDN the routine "MmMapViewInSystemSpace" as well as many other Memory Manager Routines, is reserved for system use and should not be used in a driver. Despite this information, I want to know if there is a limitation of section view size I can try and map with this fucntion. I made some tests on a standard machine (256MB memory PIII), and found out that the maximum size is 16MB, not one byte more... Is it hard coded or related to my physical memory amount? Is there other API that can be used instead this "private" fucntion? Thanks Alon
From: Eliyas Yakub [MSFT] on 23 Jun 2005 01:46 Posting response from Memory manager: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemViewSize = DWORD n, where n is the number of megabytes dedicated to this view space. By default this is 16mb, but he can make it larger if he likes. In Longhorn, the key does not exist since the entire kernel VA space is dynamic (ie, his views could potentially consume nearly the entire 2gb kernel VA space, etc). -- -- -Eliyas This posting is provided "AS IS" with no warranties, and confers no rights. http://www.microsoft.com/whdc/driver/default.mspx http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
From: Alon on 7 Jul 2005 04:33 Hi again! Thanks a lot for the answer. I'm using this function to map two sections, one of them is approx 4.90 MB and when I try to re-map the second one to the size of 4,129,280 for example I fail again & again...after I fail I try to allocate Paged memory with the same size, and NonPaged memory with the same size and I Success! I looked on the specific machine in the value in the registry and it says 48. My questions: 1. Is there any substitute to this function (MmMapViewInSystemSpace)? 2. Is there a way I can check how much available "SystemView" memory I have? 3. Any other idea implementing memory mapped file? Thanks Alon "Eliyas Yakub [MSFT]" < wrote in message news:%23vOrWb7dFHA.580(a)TK2MSFTNGP15.phx.gbl... > Posting response from Memory manager: > > HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory > Management\SystemViewSize = DWORD n, where n is the number of megabytes > dedicated to this view space. By default this is 16mb, but he can make it > larger if he likes. > > In Longhorn, the key does not exist since the entire kernel VA space is > dynamic (ie, his views could potentially consume nearly the entire 2gb > kernel VA space, etc). > > > -- > -- > -Eliyas > This posting is provided "AS IS" with no warranties, and confers no rights. > http://www.microsoft.com/whdc/driver/default.mspx > http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx > > Hi! According to the MSDN the routine "MmMapViewInSystemSpace" as well as many other Memory Manager Routines, is reserved for system use and should not be used in a driver. Despite this information, I want to know if there is a limitation of section view size I can try and map with this function. I made some tests on a standard machine (256MB memory PIII), and found out that the maximum size is 16MB, not one byte more... Is it hard coded or related to my physical memory amount? Is there other API that can be used instead this "private" function? Thanks Alon
|
Pages: 1 Prev: Is it correct?SDIO CMD53 ,SDBUS_REQUEST_PACKET Next: *.inf question |