You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To find your the name of your GPU, you can run the following command or look for Display adapters in Device Manager.
90
+
To find the name of your GPU, you can run the following command or look for Display adapters in Device Manager.
91
91
```powershell
92
92
(Get-WmiObject win32_VideoController).caption
93
93
```
94
94
95
95
Once installation is complete, you are ready to deploy and run GPU-accelerated Linux modules through Azure IoT Edge for Linux on Windows.
96
96
97
97
## Configure GPU acceleration in an existing Azure IoT Edge Linux on Windows deployment
98
-
Assigning the GPU at deployment time will result in the most straightforward experience. However, to enable or disable the GPU after deployment use the 'set-eflowvm' commmand. When using 'set-eflowvm' the default parmeter will be used for any argument not specified. For example,
98
+
Assigning the GPU at deployment time will result in the most straightforward experience. However, to enable or disable the GPU after deployment use the 'set-eflowvm' command. When using 'set-eflowvm' the default parameter will be used for any argument not specified. For example,
99
99
100
100
```powershell
101
101
#Deploys EFLOW without a GPU assigned to the EFLOW VM
Several GPU vendors have provided user guides on getting the most of their hardware and software with EFLOW.
121
121
* Learn how to run Intel OpenVINO™ applications on EFLOW by following [Intel's guide on iGPU with Azure IoT Edge for Linux on Windows (EFLOW) & OpenVINO™ Toolkit](https://community.intel.com/t5/Blogs/Tech-Innovation/Artificial-Intelligence-AI/Witness-the-power-of-Intel-iGPU-with-Azure-IoT-Edge-for-Linux-on/post/1382405) and [reference implementations](https://www.intel.com/content/www/us/en/developer/articles/technical/deploy-reference-implementation-to-azure-iot-eflow.html).
122
-
* Get started with deploying CUDA-accelerated applications on EFLOW by following [NVIDIA's EFLOW User Guide for GeForce/Quadro/RTX GPUs](https://docs.nvidia.com/cuda/eflow-users-guide/index.html). Note this guide does not cover DDA-based GPUs such as NVIDIA T4 or A2.
122
+
* Get started with deploying CUDA-accelerated applications on EFLOW by following [NVIDIA's EFLOW User Guide for GeForce/Quadro/RTX GPUs](https://docs.nvidia.com/cuda/eflow-users-guide/index.html).
123
+
124
+
> [!NOTE]
125
+
> This guide does not cover DDA-based GPUs such as NVIDIA T4 or A2.
123
126
124
127
### Dive into the Technology
125
128
Learn more about GPU passthrough technologies by visiting the [DDA documentation](/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server#discrete-device-assignment-dda) and [GPU-PV blog post](https://devblogs.microsoft.com/directx/directx-heart-linux/#gpu-virtualization).
0 commit comments