From deb9acd0c56cb586b4d5c8d749efaa9ef49408bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1ty=C3=A1s=20Aradi?= Date: Fri, 22 Nov 2024 15:13:21 +0100 Subject: [PATCH] Update based on review comment --- docs/how-to/hip_runtime_api/multi_device.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/how-to/hip_runtime_api/multi_device.rst b/docs/how-to/hip_runtime_api/multi_device.rst index 4a95dabff5..05d07c6d18 100644 --- a/docs/how-to/hip_runtime_api/multi_device.rst +++ b/docs/how-to/hip_runtime_api/multi_device.rst @@ -15,10 +15,10 @@ Device enumeration involves identifying all the available GPUs connected to the host system. A single host machine can have multiple GPUs, each with its own unique identifier. By listing these devices, you can decide which GPU to use for computation. The host queries the system to count and list all connected -GPUs, ensuring that the application can leverage the full computational power -available. Typically, applications list devices and their properties for -deployment planning, and also make dynamic selections during runtime to ensure -optimal performance. +GPUs that support the chosen ``HIP_PLATFORM``, ensuring that the application +can leverage the full computational power available. Typically, applications +list devices and their properties for deployment planning, and also make +dynamic selections during runtime to ensure optimal performance. If the application does not assign a specific GPU, the runtime typically assigns one automatically based on factors such as availability, performance,