GPU (reference) in projects: third_party

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:GPU (Results 1 – 25 of 782) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...32

/third_party/skia/third_party/externals/opengl-registry/extensions/NV/
D	NV_gpu_multicast.txt	50 This extension enables novel multi-GPU rendering techniques by providing application control 53 Multi-GPU rendering techniques fall into two categories: implicit and explicit. Existing 55 application complexity. An application must manage one context per GPU and multi-pump the API 56 stream. Implicit multi-GPU rendering techniques avoid these issues by broadcasting rendering 58 rendering (AFR), split-frame rendering (SFR) and multi-GPU anti-aliasing. They each have 61 With multi-GPU anti-aliasing, each GPU renders the same content with alternate sample 65 These issues with implicit multi-GPU rendering all have the same root cause: the driver lacks 71 - One context controls multiple GPUs. Every GPU in the linked group can access every object. 75 - Each GPU gets its own instance of all framebuffers, allowing individualized output for each 76 GPU. Input data can be customized for each GPU using buffers created with the storage flag, [all …]
D	WGL_NV_gpu_affinity.txt	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. [all …]
/third_party/openGLES/extensions/NV/
D	NV_gpu_multicast.txt	52 This extension enables novel multi-GPU rendering techniques by providing application control 55 Multi-GPU rendering techniques fall into two categories: implicit and explicit. Existing 57 application complexity. An application must manage one context per GPU and multi-pump the API 58 stream. Implicit multi-GPU rendering techniques avoid these issues by broadcasting rendering 60 rendering (AFR), split-frame rendering (SFR) and multi-GPU anti-aliasing. They each have 63 With multi-GPU anti-aliasing, each GPU renders the same content with alternate sample 67 These issues with implicit multi-GPU rendering all have the same root cause: the driver lacks 73 - One context controls multiple GPUs. Every GPU in the linked group can access every object. 77 - Each GPU gets its own instance of all framebuffers, allowing individualized output for each 78 GPU. Input data can be customized for each GPU using buffers created with the storage flag, [all …]
D	WGL_NV_gpu_affinity.txt	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. [all …]
D	GLX_NV_multigpu_context.txt	48 This extension allows the creation of an OpenGL context in a multi-GPU 49 environment with a specified multi-GPU strategy (known as SLI mode) which 50 takes precedence over process-wide multi-GPU mode settings. 52 The multi-GPU mode denotes vendor specific techniques to allow distributed 59 multi-GPU rendering mode per context, thus context switching can also 60 switch the current multi-GPU rendering mode. 63 contexts in single mode to force all rendering to be done on a single GPU, 68 The implementation is platform dependent and the actual multi-GPU rendering 99 preferred multi-GPU rendering mode for the OpenGL context.
D	WGL_NV_multigpu_context.txt	46 This extension allows the creation of an OpenGL context in a multi-GPU 47 environment with a specified multi-GPU strategy (known as SLI mode) which 48 takes precedence over process-wide multi-GPU mode settings. 50 The multi-GPU mode denotes vendor specific techniques to allow distributed 57 multi-GPU rendering mode per context, thus context switching can also 58 switch the current multi-GPU rendering mode. 60 The implementation is platform dependent and the actual multi-GPU rendering 89 preferred multi-GPU rendering mode for the OpenGL context. 135 specified when a linked multi-GPU display configuration is considered for multicast rendering
/third_party/skia/third_party/externals/opengl-registry/extensions/NVX/
D	NVX_linked_gpu_multicast.txt	47 This extension enables novel multi-GPU rendering techniques by providing application control 50 Multi-GPU rendering techniques fall into two categories: implicit and explicit. Existing 52 application complexity. An application must manage one context per GPU and multi-pump the API 53 stream. Implicit multi-GPU rendering techniques avoid these issues by broadcasting rendering 55 rendering (AFR), split-frame rendering (SFR) and multi-GPU anti-aliasing. They each have 58 With multi-GPU anti-aliasing, each GPU renders the same content with alternate sample 62 These issues with implicit multi-GPU rendering all have the same root cause: the driver lacks 68 - One context controls multiple GPUs. Every GPU in the linked group can access every object. 72 - Each GPU gets its own instance of all framebuffers and attached textures, allowing 73 individualized output for each GPU. Input data can be customized for each GPU using buffers [all …]
D	NVX_gpu_memory_info.txt	56 GL_NVX_gpu_memory_info provides applications visibility into GPU 59 current available GPU memory. This information is made available 63 total size of evictions of data from GPU memory since the last time 100 Section 6.1.x, GPU Memory Information Query 104 Information on GPU memory resources available can be queried 115 These will return the memory status of the context's associated GPU memory. 118 the overall GPU memory utilization so that an application can determine 119 when the resource usage is approaching the full capacity of the GPU memory 125 - dedicated video memory, total size (in kb) of the GPU memory 133 currently unused GPU memory [all …]
/third_party/openGLES/extensions/NVX/
D	NVX_linked_gpu_multicast.txt	47 This extension enables novel multi-GPU rendering techniques by providing application control 50 Multi-GPU rendering techniques fall into two categories: implicit and explicit. Existing 52 application complexity. An application must manage one context per GPU and multi-pump the API 53 stream. Implicit multi-GPU rendering techniques avoid these issues by broadcasting rendering 55 rendering (AFR), split-frame rendering (SFR) and multi-GPU anti-aliasing. They each have 58 With multi-GPU anti-aliasing, each GPU renders the same content with alternate sample 62 These issues with implicit multi-GPU rendering all have the same root cause: the driver lacks 68 - One context controls multiple GPUs. Every GPU in the linked group can access every object. 72 - Each GPU gets its own instance of all framebuffers and attached textures, allowing 73 individualized output for each GPU. Input data can be customized for each GPU using buffers [all …]
D	NVX_gpu_memory_info.txt	56 GL_NVX_gpu_memory_info provides applications visibility into GPU 59 current available GPU memory. This information is made available 63 total size of evictions of data from GPU memory since the last time 100 Section 6.1.x, GPU Memory Information Query 104 Information on GPU memory resources available can be queried 115 These will return the memory status of the context's associated GPU memory. 118 the overall GPU memory utilization so that an application can determine 119 when the resource usage is approaching the full capacity of the GPU memory 125 - dedicated video memory, total size (in kb) of the GPU memory 133 currently unused GPU memory [all …]
/third_party/skia/site/docs/dev/gardening/
D	gpu.md	3 title: "GPU Gardener Documentation" 4 linkTitle: "GPU Gardener Documentation" 11 * [What does a GPU Gardener do?](#what_is_a_gpu_gardener) 12 * [Tracking GPU Gardener Work](#tracking) 15 * [Tips for GPU Gardeners](#tips) 19 What does a GPU Gardener do? 22 The GPU Gardener has three main jobs: 24 1) Stay on top of incoming GPU-related bugs from clients in various bug trackers. This means triagi… 27 2) Improve the reliability of the GPU bots. This includes dealing with flaky images, crashing bots,… 33 The GPU Gardener should always prioritize dealing with incoming bugs. The balance of a gardener's t… [all …]
/third_party/skia/third_party/externals/angle2/doc/
D	GPUMemoryAnalysis.md	1 # GPU Memory Reporting and Analysis 6 GPU memory usage data can be reported when using the Vulkan back-end with drivers that support the 8 based on every allocation, free, import, unimport, and failed allocation of GPU memory. This 12 ## GPU Memory Reporting 16 each of the following GPU memory events: 18 - Allocation of GPU memory by ANGLE 19 - Free of GPU memory by ANGLE 20 - Import of GPU memory provided by another process (e.g. Android SurfaceFlinger) 21 - Unimport of GPU memory provided by another process 55 Note: At this time, GPU memory reporting has only been tested and used on Android, where the logged [all …]
/third_party/vulkan-loader/
D	README_OpenHarmony.md	7 核心API由GPU驱动实现，窗口系统集成(WSI)扩展API由[swapchain_layer](#swapchain_layer)实现，swapchain_layer是OpenHarmony平台是… 13 1、加载GPU驱动。 22 ## 加载GPU驱动 24 在OpenHarmony上，Vulkan-Loader会扫描指定路径下的GPU驱动的json清单文件并读取该文件加载GPU驱动。 33 建议：GPU驱动的json清单文件应放在`/vendor/etc/vulkan/icd.d/`目录中。 35 Vulkan-Loader会根据GPU驱动的json清单文件中配置的`library_path`找到GPU驱动的动态链接库文件(.so文件)并加载。 37 ### GPU驱动的json清单文件示例 53 ### GPU驱动的实现 55 GPU驱动需要实现的Vulkan接口请参考文档：[LoaderDriverInterface](docs/LoaderDriverInterface.md)，开发者需要按照文档里的要求实现对应的接口…
/third_party/openGLES/extensions/AMD/
D	WGL_AMD_gpu_association.txt	50 There currently is no way for applications to efficiently use GPU 51 resources in systems that contain more than one GPU. Vendors have 53 application among the available GPU resources. This has proven to be 58 use the GPU resources on a given system individually. By providing 63 wglGetGPUIDsAMD(). The current GPU assigned to a specific context 64 can be determined by calling wglGetContextGPUIDAMD. Each GPU in a 67 GPU can be obtained by calling wglGetGPUInfo. This will allow 68 applications to pick the most appropriate GPU for each rendering 71 Once all necessary GPU information has been obtained, a context tied 72 to a specific GPU can be created with wglCreateAssociatedContextAMD. [all …]
D	GLX_AMD_gpu_association.txt	53 There currently is no way for applications to efficiently use GPU 54 resources in systems that contain more than one GPU. Vendors have 56 application among the available GPU resources. This has proven to be 61 use the GPU resources on a given system individually. By providing 66 glXGetGPUIDsAMD. The current GPU assigned to a specific context 67 can be determined by calling glXGetContextGPUIDAMD. Each GPU in a 70 GPU can be obtained by calling glXGetGPUInfo. This will allow 71 applications to pick the most appropriate GPU for each rendering 74 Once all necessary GPU information has been obtained, a context tied 75 to a specific GPU can be created with glXCreateAssociatedContextAMD. [all …]
/third_party/skia/third_party/externals/opengl-registry/extensions/AMD/
D	WGL_AMD_gpu_association.txt	50 There currently is no way for applications to efficiently use GPU 51 resources in systems that contain more than one GPU. Vendors have 53 application among the available GPU resources. This has proven to be 58 use the GPU resources on a given system individually. By providing 63 wglGetGPUIDsAMD(). The current GPU assigned to a specific context 64 can be determined by calling wglGetContextGPUIDAMD. Each GPU in a 67 GPU can be obtained by calling wglGetGPUInfo. This will allow 68 applications to pick the most appropriate GPU for each rendering 71 Once all necessary GPU information has been obtained, a context tied 72 to a specific GPU can be created with wglCreateAssociatedContextAMD. [all …]
D	GLX_AMD_gpu_association.txt	53 There currently is no way for applications to efficiently use GPU 54 resources in systems that contain more than one GPU. Vendors have 56 application among the available GPU resources. This has proven to be 61 use the GPU resources on a given system individually. By providing 66 glXGetGPUIDsAMD. The current GPU assigned to a specific context 67 can be determined by calling glXGetContextGPUIDAMD. Each GPU in a 70 GPU can be obtained by calling glXGetGPUInfo. This will allow 71 applications to pick the most appropriate GPU for each rendering 74 Once all necessary GPU information has been obtained, a context tied 75 to a specific GPU can be created with glXCreateAssociatedContextAMD. [all …]
/third_party/skia/src/gpu/vk/
D	GrVkUtil.h	`24 #define GR_VK_CALL_RESULT(GPU, RESULT, X) \ argument 26 (RESULT) = GR_VK_CALL(GPU->vkInterface(), X); \ 28 if (RESULT != VK_SUCCESS && !GPU->isDeviceLost()) { \ 31 GPU->checkVkResult(RESULT); \ 34 #define GR_VK_CALL_RESULT_NOCHECK(GPU, RESULT, X) \ argument 36 (RESULT) = GR_VK_CALL(GPU->vkInterface(), X); \ 37 GPU->checkVkResult(RESULT); \ 41 #define GR_VK_CALL_ERRCHECK(GPU, X) \ argument 43 GR_VK_CALL_RESULT(GPU, SK_MACRO_APPEND_LINE(ret), X) \`
/third_party/flutter/skia/third_party/externals/angle2/infra/
D	ANGLEWrangling.md	8 [Chromium GPU FYI Waterfall](https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console) 28 wrangler and GPU Pixel Wrangler. 41 The [Chromium GPU FYI Waterfall](https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console) 43 persistent breakage that could be related to ANGLE. Also follow the `Internals>GPU>ANGLE` component 44 on the Chromium issue tracker to be alerted to reports of breakage on the GPU.FYI waterfall. 46 the health of the GPU.FYI waterfall. 48 Note that the GPU Pixel Wrangler is responsible for the Chromium bugs. Please file issues with 56 * Set components: `Internals>GPU` and/or `Internals>GPU>ANGLE`. 60 ### How to determine the ANGLE regression range on the GPU.FYI bots:
/third_party/flutter/skia/third_party/externals/angle2/src/feature_support_util/
D	feature_support_util.cpp	423 class GPU class 426 GPU(const std::string vendor, uint32_t deviceId, const Version &version) in GPU() function in angle::GPU 429 GPU(const std::string vendor, uint32_t deviceId) in GPU() function in angle::GPU 432 GPU(const std::string vendor) : mVendor(vendor), mDeviceId(), mVersion(), mWildcard(false) {} in GPU() function in angle::GPU 433 GPU() : mVendor(), mDeviceId(), mVersion(), mWildcard(true) {} in GPU() function in angle::GPU 434 bool match(const GPU &toCheck) const in match() 450 ~GPU() {} in ~GPU() 452 static GPU CreateGpuFromJson(const Json::Value &jObject) in CreateGpuFromJson() 454 GPU gpu = nullptr; in CreateGpuFromJson() 467 gpu = new GPU(vendor, deviceId, *version); in CreateGpuFromJson() [all …]
/third_party/skia/third_party/externals/angle2/src/feature_support_util/
D	feature_support_util.cpp	409 class GPU class 412 GPU(StringPart vendor, IntegerPart deviceId, Version version) in GPU() function in angle::GPU 418 GPU(std::string vendor, uint32_t deviceId, Version version) in GPU() function in angle::GPU 419 : GPU(StringPart(std::move(vendor)), IntegerPart(deviceId), std::move(version)) in GPU() 421 GPU() = default; 422 ~GPU() = default; 423 bool match(const GPU &toCheck) const in match() 433 static bool CreateGpuFromJson(const Json::Value &jObject, GPU out) in CreateGpuFromJson() 445 out = GPU{std::move(vendor), std::move(deviceId), std::move(version)}; in CreateGpuFromJson() 506 void addGPU(GPU &&gpu) { mGpuList.addItem(std::move(gpu)); } in addGPU() [all …]
/third_party/mesa3d/docs/drivers/
D	vc4.rst	5 Broadcom's VideoCore IV GPU. It is notably used in the Raspberry Pi 0 16 GPU block from Linux. 76 For GPU hangs, if you can get a short apitrace that produces the 99 (GPU) Initialize the per-tile draw call lists to empty. 100 (GPU) Run all draw calls collecting vertex data 101 (GPU) For each tile covered by a draw call's primitive. 117 from memory, in favor of a cheap GPU-side ``memset()`` of the tile 155 * Increasing GPU memory Increase CMA pool size 192 * Step 2: CPU vs GPU 195 application, the CPU is busy in the GL driver, the GPU is waiting for [all …]
/third_party/mindspore/
D	README_CN.md	82 \| GPU CUDA 10.1 \| Ubuntu-x86 \| ✔️ \| 128 - [GPU环境使用pip方式安装MindSpore](https://gitee.com/mindspore/docs/blob/master/install/mindspore_gpu_inst… 136 - [GPU环境使用源码编译方式安装MindSpore](https://gitee.com/mindspore/docs/blob/master/install/mindspore_gpu_ins… 149 \| GPU \| `mindspore/mindspore-gpu` \| `x.y.z` \| 已经预安装MindSpore `x.y.z` GPU版本的生产环境… 150 \| \| \| `devel` \| 提供开发环境从源头构建MindSpore（`GPU CUDA10.… 151 \| \| \| `runtime` \| 提供运行时环境安装MindSpore二进制包（`GPU CUDA1… 153 > 注意：不建议从源头构建GPU `devel` Docker镜像后直接安装whl包。我们强烈建议您在GPU `runtime` Docker镜像中传输并安装whl包。 164 - GPU 166 对于`GPU`后端，请确保`nvidia-container-toolkit`已经提前安装，以下是`Ubuntu`用户安装指南： 213 context.set_context(mode=context.PYNATIVE_MODE, device_target="GPU")
/third_party/skia/third_party/externals/dawn/src/dawn_node/binding/
D	GPU.h	`26 class GPU final : public interop::GPU { 28 GPU(Flags flags);`
/third_party/skia/third_party/externals/angle2/extensions/
D	EGL_ANGLE_power_preference.txt	`36 This extension allows selection of the high- or low-power GPU on 37 dual-GPU systems, specifically on macOS. 71 created on the integrated (low-power) or discrete (high-power) GPU 72 on dual-GPU systems. EGL_POWER_PREFERENCE_ANGLE is only a legal 86 hold on the high-power GPU. 92 its hold on the high-power GPU.`

12 3 4 5 6 7 8 9 10 >>...32