hipsetdeviceflags Interface Reference#
hipfort::hipsetdeviceflags Interface Reference
The current device behavior is changed according the flags passed. More...
Public Member Functions | |
| integer(kind(hipsuccess)) function | hipsetdeviceflags_ (flags) |
Detailed Description
The current device behavior is changed according the flags passed.
- Parameters
-
[in] flags The schedule flags impact how HIP waits for the completion of a command running on a device. hipDeviceScheduleSpin : HIP runtime will actively spin in the thread which submitted the work until the command completes. This offers the lowest latency, but will consume a CPU core and may increase power. hipDeviceScheduleYield : The HIP runtime will yield the CPU to system so that other tasks can use it. This may increase latency to detect the completion but will consume less power and is friendlier to other tasks in the system. hipDeviceScheduleBlockingSync : On ROCm platform, this is a synonym for hipDeviceScheduleYield. hipDeviceScheduleAuto : Use a hueristic to select between Spin and Yield modes. If the number of HIP contexts is greater than the number of logical processors in the system, use Spin scheduling. Else use Yield scheduling.
hipDeviceMapHost : Allow mapping host memory. On ROCM, this is always allowed and the flag is ignored. hipDeviceLmemResizeToMax :
- Warning
- ROCm silently ignores this flag.
- Returns
- hipSuccess, hipErrorInvalidDevice, hipErrorSetOnActiveProcess
Member Function/Subroutine Documentation
◆ hipsetdeviceflags_()
| integer(kind(hipsuccess)) function hipfort::hipsetdeviceflags::hipsetdeviceflags_ | ( | integer(c_int), value | flags | ) |
The documentation for this interface was generated from the following file: