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
It would be good to add "gpu" as a "compute_mode" option in HiOp. However, this option is not independent of "mem_space" selection. Here is the summary of compute mode and memory space option compatibilities:
"cpu" option works only with "default", "host" and likely "um" memory space options.
"hybrid" works with all but "device" memory space option.
"gpu", if added, would work with "um", "pinned" or "device" options.
We can simply document this and expect user to select a meaningful combination or we can add some logic to HiOp options class that would warn user or when incompatible combination was selected and fall back to the next best thing.
If HiOp is built without RAJA support, only "default" memory space is available.
Options "um", "pinned" or "device" are available only if HiOp is built with GPU support (for now it's CUDA only) turned on.
It would be good to add "gpu" as a "compute_mode" option in HiOp. However, this option is not independent of "mem_space" selection. Here is the summary of compute mode and memory space option compatibilities:
We can simply document this and expect user to select a meaningful combination or we can add some logic to HiOp options class that would warn user or when incompatible combination was selected and fall back to the next best thing.
If HiOp is built without RAJA support, only "default" memory space is available.
Options "um", "pinned" or "device" are available only if HiOp is built with GPU support (for now it's CUDA only) turned on.
CC @ashermancinelli @cnpetra
The text was updated successfully, but these errors were encountered: