Skip to content

Commit 3419530

Browse files
authored
pencil edits
Line 90: your the > the Line 98: commmand > command Line 98: parmeter > parameter Line 122: Converted note to Markdown syntax
1 parent d78699e commit 3419530

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/iot-edge/gpu-acceleration.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,15 +87,15 @@ Deploy-Eflow -gpuPassthroughType DirectDeviceAssignment -gpuCount 1 -gpuName "NV
8787
Deploy-Eflow -gpuPassthroughType ParaVirtualization -gpuCount 1 -gpuName “Intel(R) Iris(R) Xe Graphics”
8888
```
8989

90-
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.
9191
```powershell
9292
(Get-WmiObject win32_VideoController).caption
9393
```
9494

9595
Once installation is complete, you are ready to deploy and run GPU-accelerated Linux modules through Azure IoT Edge for Linux on Windows.
9696

9797
## 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,
9999

100100
```powershell
101101
#Deploys EFLOW without a GPU assigned to the EFLOW VM
@@ -119,7 +119,10 @@ Visit our [EFLOW Samples Page](https://github.com/Azure/iotedge-eflow/tree/main/
119119
### Learn More from our Partners
120120
Several GPU vendors have provided user guides on getting the most of their hardware and software with EFLOW.
121121
* 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.
123126
124127
### Dive into the Technology
125128
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

Comments
 (0)