RSS Feed for This Post

Inside the Windows Vista Kernel: Part 2

Category Vista | Permalink | 24. February 2007

« Keeley Hazell Homemade Nude Tape Youtube Video | Britney Spears and her Green Umbrella Youtube Video »

Last month, in the first installment of this three-part series, I looked at Windows Vista kernel enhancements in the areas of processes and I/O.

This time I’ll cover advances in the way Windows Vista manages memory, as well as major improvements to system startup, shutdown, and power management (Part 1).

 

Every release of Windows® improves scalability and performance, and Windows Vista™ is no different. The Windows Vista Memory Manager includes numerous enhancements, like more extensive use of lock-free synchronization techniques, finer-grained locking, tighter data-structure packing, larger paging I/Os, support for modern GPU memory architectures, and more efficient use of the hardware Translation Lookaside Buffer. Plus, Windows Vista memory management now offers dynamic address space allocation for the requirements of different workloads.

Four performance-enhancing features that use new technologies make their operating system debut on Windows Vista: SuperFetch, ReadyBoost, ReadyBoot, and ReadyDrive. I’ll discuss them in detail later in this article.

Dynamic Kernel Address Space

Windows and the applications that run on it have bumped their heads on the address space limits of 32-bit processors. The Windows kernel is constrained by default to 2GB, or half the total 32-bit virtual address space, with the other half reserved for use by the process whose thread is currently running on the CPU. Inside its half, the kernel has to map itself, device drivers, the file system cache, kernel stacks, per-session code data structures, and both non-paged (locked-in physical memory) and paged buffers allocated by device drivers. Prior to Windows Vista, the Memory Manager determined at boot time how much of the address space to assign to these different purposes, but this inflexibility sometimes led to situations where one of the regions became full while others still had plenty of available space. The exhaustion of an area can lead to application failures and prevent device drivers from completing I/O operations.

In 32-bit Windows Vista, the Memory Manager dynamically manages the kernel’s address space, allocating and deallocating space to various uses as the demands of the workload require. Thus, the amount of virtual memory used to store paged buffers can grow when device drivers ask for more, and it can shrink when the drivers release it. Windows Vista will therefore be able to handle a wider variety of workloads and likewise the 32-bit version of the forthcoming Windows Server® code-named “Longhorn,” will scale to handle more concurrent Terminal Server users.

Of course, on 64-bit Windows Vista systems, address space constraints are not currently a practical limitation and therefore require no special treatment as they are configured to their maximums.

Read More :  www.microsoft.com

301 Read

Related Posts



Trackback URL

Sociable

TAG

Share Enjoy:
, , , , , , , , , , , , ,
Share and Enjoy: Digg del.icio.us Netvouz DZone ThisNext MisterWong Wists blinkbits BlinkList blogmarks BlogMemes Bumpzee co.mments connotea Furl Ma.gnolia MisterWong.de Reddit Scoopeo Slashdot SphereIt Spurl StumbleUpon YahooMyWeb BlogMemes Cn BlogMemes Fr BlogMemes Jp BlogMemes Sp blogtercimlap Blue Dot Book.mark.hu De.lirio.us DotNetKicks Fark feedmelinks Fleck Gwar Haohao Hemidemi IndiaGram IndianPad Internetmedia kick.ie LinkaGoGo Linkter MyShare Netscape NewsVine PlugIM PopCurrent ppnow RawSugar Rec6 scuttle Shadows Simpy Smarking Taggly TailRank Technorati Webride Wykop