System virtual address (VA) space allocated on-demand
Instead of at boot time based registry & configuration information
Region sizes bounded only by VA limitations
Applies to non-paged, paged, session space, mapped views, etc.
Kernel page tables allocated on demand
No longer preallocated at system boot, saves
1.5MB on x86 systems3MB on PAE systems
16MB to 2.5GB on 64-bit machines
Boot with very large registries on 32-bit machines
With and without /3GB switch Important for large multipath LUN machines
MM locates registry VA space used by boot loader & reuses it as dynamic kernel virtual address space
Key Benefits of Dynamic Address Space
Maximum resources available in wide range of scenarios, w/ no human intervention
Desktop heap exhaustion
Terminal Server maximum scaling
Large video clients
/3GB SQL and Exchange machines
Http servers, NFS servers, etc
Features enabled w/o reboot, yet have no cost if not used
64-bit systems grow to maximum limit regardless of underlying physical configuration
128GB paged pool, nonpaged pool
1TB system cache/system PTEs/special pool
128GB session pool
128GB session views (desktop heaps), etc
本文介绍了一种按需分配的系统虚拟地址空间管理方法,这种方法不再依赖于启动时的注册表和配置信息,而是根据实际需求动态分配内核页表等资源。通过这种方式,可以有效节省内存,例如,在x86系统上最多可节省1.5MB,在64位机器上可节省的空间从16MB到2.5GB不等。此外,动态地址空间还能够更好地应对各种资源不平衡的情况,如桌面堆栈耗尽、终端服务器的最大扩展能力等问题。
2万+

被折叠的 条评论
为什么被折叠?



