• Home
  • Raw
  • Download

Lines Matching refs:DC

49       This extension also introduces the concept called affinity-DC. An
50 affinity-DC is a device context with a GPU affinity mask embedded
55 command wglEnumGpusNV. An affinity-DC is created by calling
57 which make up the affinity mask. An affinity-DC can also
58 indirectly be created by obtaining a DC from a pBuffer handle, by
60 affinity-DC by calling wglCreatePbuffer.
62 A context created from an affinity DC will inherit the GPU
63 affinity mask from the DC. Once inherited, it cannot be changed.
69 1. Make the affinity-context current to an affinity-DC. This
71 as the affinity mask in the DC. There is no window
72 associated with an affinity DC, therefore this is a way to
76 the pBuffer DC, which is obtained from a pBuffer handle,
77 will be the same affinity-mask as the DC used to created the
83 2. Make the affinity-context current to a DC obtained from a
93 affinity mask) current to an affinity-DC. This would mean a way
228 A new type of DC, called an affinity-DC, can be used to direct
229 OpenGL commands to a specific GPU or set of GPUs. An affinity-DC
232 sent to the GPU(s) in the affinity mask. An affinity-DC can be
235 wglGetPbufferDCARB. To create an affinity-DC directly call:
240 affinity-DC will be restricted. If an element in the list is not a
243 If successful, the function returns an affinity-DC. If it fails,
246 To create an affinity-DC indirectly, first call
247 wglCreatePbufferARB passing it an affinity-DC. Next, pass the
249 wglGetPbufferDCARB to create an affinity-DC for the pBuffer. The
250 DC returned by wglGetPbufferDCARB will have the same affinity mask
251 as the DC used to create the pBuffer handle by calling
254 An affinity-DC has no window associated with it, and therefore it
257 current to an affinity-DC will only be able to render into an
263 A context created from an affinity-DC, by calling wglCreateContext
264 and passing it an affinity-DC, is called an affinity-context. This
265 context will inherit the affinity mask from the DC. This affinity-
275 create the affinity-DC.
280 An affinity-context can only be made current to an affinity-DC
287 affinity-DC, wglMakeCurrent and wglMakeContextCurrentARB will fail
289 fail if either the "read" or "draw" DC is an affinity-DC.
291 If an affinity-context is made current to a DC obtained from a
295 the context. Note that a DC obtained from a window does not have
315 To delete an affinity-DC call:
319 <hdc> Is a handle of an affinity-DC to delete.
325 ERROR_INVALID_HANDLE <hdc> is not a handle of an affinity-DC.
328 of an affinity-DC, call:
334 <hAffinityDC> is a handle of the affinity-DC to query.
344 the DC can be queried. If the function succeeds, the return value
354 affinity-DC.
373 // Example 1 - Normal window creation, DC setup and
422 // Create an affinity-DC associated with the first GPU
428 // Set a pixelformat on the affinity-DC
463 // Create an affinity-DC associated with the first GPU
503 1) Do we really need an affinity-DC, or can we do with just an
506 DISCUSSION: If affinity is not part of a DC, a new function will
515 counter to the whole idea of this extension. Thus an affinity-DC
518 Thus the question reduces to, do we need an affinity-DC in order
519 to facilitate off-screen rendering to a FBO? Having an affinity-DC
523 that does need a DC.
526 c) The driver implementation might benefit from knowing at DC
541 3) Should setting a pixelformat on an affinity-DC be required?
543 DISCUSSION: Setting a pixelformat on an affinity-DC is not
546 that the pixelformats of the DC and RC passed to it match. This
547 becomes an issue when making an affinity-context current to a DC
548 obtained from a window. The DC has a pixelformat set by the
550 same pixelformat. This means the affinity-DC, that the affinity-
553 RESOLUTION: YES. Setting a pixelformat on an affinity-DC is
557 affinity-DC where the mask of the context spans more GPUs than the
558 mask in the DC?
561 affinity-DC where the mask of the context spans less GPUs than the
562 mask in the DC?
571 GPUs. Making one context current to the first affinity-DC will
572 lock the context to the GPU in the mask of that affinity-DC. Make
573 another context current to the second affinity-DC will lock that