Kernel Virtual Memory Shared by all kernel Servers and driversĬached access to physical memory 0x80000000
Kernel Space 2 Gigabytes Fixed mapping independent of user space RAM Backed Mapfiles Mapped at fixed location for better backwards compatibilityĪll DLLs – code and data Same mapping across all processes Data pages are unique physical pages Code pages are shared 0x40000000Įxecutable code and data VM Allocation File Back Mapfiles R/W for OS components Read only for user process User Space 2 Gigabytes Each process has its own mapping Improved system performance Increased security and robustness High degree of backwards compatibilityĪpplication Virtual Memory Space 0x80000000 Introducing the New Kernel 2 GB of Virtual Memory per processģ2,000 processes Unified Kernel Critical OS components moved into kernel space Shared memory Upper half of user space is shared memory Read / Write by all processes Windows CE 5.0 Memory Model Virtual Memory Map 2 GB for Kernel Single 2 GB mapping for all processes Divided up into 32 MB “slots”ģ2 Process Limit Each process has one 32 MB slot 32 slots for processes
Slot 32 Slot 31 : : Slot 7 Slot 6 – Explorer.exe Slot 5 – Services.exe Slot 4 – GWES.exe Slot 3 – Device.exe Slot 2 – FileSys.exe Slot 1 – ROM DLLs Slot 0 – Executionģ2 Slots for Processes Execution Slot and Shared DLL Slot Windows CE Limits From Windows CE 1 to Windows CE 5, Windows CE has always had limits 32 processes at any one time 32 MB Virtual Memory per process NET Compact Framework Consultant – Work with companies to help their Windows CE application and platform development effortsĪgenda Overview - Introduction Windows CE 6 Memory Model New Features Compatibility BSP Changes Speaker Douglas Boling dbolingmedc Īuthor – “Programming Microsoft Windows CE 3rd Edition” Trainer – Classes on Windows CE App Development Windows CE OAL Development.
Windows CE 6.0 Architecture Douglas Boling President Boling Consulting Inc.