Overview of using virtual address space in Windows game development August 2, 2007 Windows Vista® significantly improves the way the operating system handles graphics processing units (GPUs). The Windows Vista Display Driver Model (WDDM) can better share GPU resources among multiple graphics applications. The video memory manager component of WDDM virtualizes the video memory resources available for use in the application. This allows you to link the new Windows Aero experience with other applications that use the GPU, such as video playback.
In the virtual memory system, each process has its own virtual memory called address space. In Windows XP 32 bit version, the virtual address space is 4 gigabytes (GB). It can be divided into two partitions (MSDN): 2 GB for the system, 3 GB for the process, 1 GB for the system. Library), 2011). On 64-bit Windows XP, the virtual address space per process on IA-64 bit systems is about 7152 GB and for x 64 systems it is 8192 GB (Russinovich & Solomon, 2008). All processes can access their respective virtual address space, but the address space is private and can not be accessed by other processes unless they are shared to others
Each process on 32-bit Microsoft Windows has its own virtual address space and can handle up to 4 gigabytes of memory. Each process on 64-bit Windows has 8 TB of virtual address space. All threads in a process can access their virtual address space, but these threads can not access memory belonging to other processes. Therefore, this prevents the process from being destroyed by other processes. The process's virtual address space is the set of virtual memory addresses that a process can use. The address space of each process is private and can not be accessed unless other processes share it.
The only address space that the operating system uniquely assigns to users or programs is the address space. This is a contiguous virtual address space that can be used to execute instructions and store data. With address space, you can distinguish logical partitions from the data executed in the program. This is how z / OS is used to build a dedicated container for handling each end user's request. Therefore, runtime protection by operating system architecture is guaranteed.