PCTuning fórum

Eddward píše:no hlavne je idealne cim skor vypatrat coho/koho zasluha to je, aby sa nakoniec neukazalo ze je to len nejaka nahoda ci "bug", ktory si nikto nejak nevsimol a len co pride novy ovladac alebo aktualizacia OS bude to prec...

Eddward píše:no hlavne je idealne cim skor vypatrat coho/koho zasluha to je, aby sa nakoniec neukazalo ze je to len nejaka nahoda ci "bug", ktory si nikto nejak nevsimol a len co pride novy ovladac alebo aktualizacia OS bude to prec...

webwalker píše:Ten bug se jmenuje "Virtual memory"

Jinak to tahání zdrojů vůbec nemusí být nějak masivnější než před tím.

As more hardware vendors move toward a hardware based scheduling model, where work is submitted to the GPU directly from user mode and where the GPU manages the various queue of work itself, it is necessary to eliminate the need for the video memory manager to inspect and patch every command buffer before submission to a GPU engine.

To achieve this we are introducing support for GPU virtual addressing in WDDM v2. In this model, each process gets assigned a unique GPU virtual address space in which every GPU context to execute in. An allocation, created or opened by a process, gets assigned a unique GPU virtual address within that process GPU virtual address space that remains constant and unique for the lifetime of the allocation. This allows the user mode driver to reference allocations through their GPU virtual address without having to worry about the underlying physical memory changing through its lifetime.

Individual engines of a GPU can operate in either physical or virtual mode. In the physical mode, the scheduling model remains the same as it is with WDDM v1.x. In the physical mode the user mode driver continues to generate the allocation and patch location lists. They are submitted along a command buffer and are used to patch command buffers to actual physical addresses before submission to an engine.

In the virtual mode, an engine references memory through GPU virtual addresses. In this mode the user mode driver generates command buffers directly from user mode and uses new services to submit those commands to the kernel. In this mode the user mode driver doesn’t generate allocation or patch location lists, although it is still responsible for managing the residency of allocations. For more information on driver residency, see Driver residency in WDDM 2.0.

Ingamacek píše: Amd karty reportuju daleko mensi vram load nV karty reportuju velkost zabratej vram aj s virtual memory