Lines Matching refs:GPU
42 On systems with more than one GPU it is desirable to be able to
43 select which GPU(s) in the system become the target for OpenGL
44 rendering commands. This extension introduces the concept of a GPU
46 GPU(s) specified by the affinity mask. GPU affinity is immutable.
50 affinity-DC is a device context with a GPU affinity mask embedded
52 commands to be sent to the GPU(s) in the affinity mask.
56 wglCreateAffinityDCNV. This function takes a list of GPU handles,
62 A context created from an affinity DC will inherit the GPU
66 GPU(s) in its affinity mask. Once created, this context can be
86 displayed by the GPU(s) in the affinity mask of the context.
139 GPU Affinity
145 <iGpuIndex> is an index value that specifies a GPU.
147 <phGPU> upon return will contain a handle for GPU number
148 <iGpuIndex>. The first GPU will be index 0.
151 starting at index 0, all GPU handles can be queried. If the
158 GPU call:
164 <hGpu> is a handle to the GPU to query.
200 <DeviceString> is a string describing the GPU for this display
226 ERROR_INVALID_HANDLE <hGpu> is not a valid GPU handle.
229 OpenGL commands to a specific GPU or set of GPUs. An affinity-DC
230 is a device context with a GPU affinity mask embedded in it. This
232 sent to the GPU(s) in the affinity mask. An affinity-DC can be
239 <phGpuList> is a NULL-terminated array of GPU handles to which the
241 GPU handle, as returned by wglEnumGpusNV, it is silently ignored.
267 context to only allow OpenGL commands to be sent to those GPU(s)
278 valid GPU handles
294 desktop that are displayed by the GPU(s) in the affinity-mask of
327 To retrieve a list of GPU handles that make up the affinity-mask
336 <iGpuIndex> is an index value of the GPU handle in the affinity
339 <phGpu> upon return will contain a handle for GPU number
340 <iGpuIndex>. The first GPU will be at index 0.
343 <iGpuIndex>, starting at index 0, all GPU handles associated with
402 // Example 2 - Offscreen rendering to one GPU using a FBO
422 // Create an affinity-DC associated with the first GPU
444 // Example 3 - Offscreen rendering to one GPU using a pBuffer
463 // Create an affinity-DC associated with the first GPU
532 2) Should the GPU affinity concept also apply to D3D and/or GDI
567 these two contexts each render to a different GPU. It can do this
569 first GPU, the other for the second GPU. It also creates two
572 lock the context to the GPU in the mask of that affinity-DC. Make
574 context to the second GPU. This is effectively what issue 4) is
621 this extension where each GPU has its own set of resources, not
622 shared with another GPU.