ROCm allows people with AMD GPUs to run CUDA code based on their HIP Compiler and other runtime components. This translates to better performance on software like Blender and Tensorflow2. This involves including the kernel modules needed for ROCm+packaging the userland+dependent packages in a nice portable way.
I think this could be driven by project manager who covers tensorflow2.
Metadata Update from @lkocman: - Issue assigned to lkocman
Please be aware of nature of 15.5 "Cosmetic release". As we plan to invest a lot of resources into ALP development. I'll open a request for the feature though.
Metadata Update from @lkocman: - Custom field SUSE Jira - SUSE Linux Enterprise adjusted to https://jira.suse.com/browse/PM-3497
AMD supports SUSE, SUSE supports AMD. ROCm is available with this repo: https://repo.radeon.com/rocm/zyp/ Choose version that you prefer. Support for Leap 15.4 is in place, so it is "out of the box" already. AMD drivers for video cards are also available: https://repo.radeon.com/, i.e. OpenCL support is here for GCN2 and newer. What users need for ROCm from SLE/openSUSE is a recompiling it with flag(s) to enable support for pre-GCN5 chips (GCN2-GCN4). Question from user: https://forums.opensuse.org/showthread.php/571913-Installing-ROCM-in-TW-and-Leap AMD doesn't support pre-GCN5 GPUs by default with ROCm since ROCm 4.5 (phased out by AMD, code is still in place). Read more here: https://developer.blender.org/T96740#1386492
Metadata Update from @lkocman: - Issue tagged with: SLE-Accept-Pending
I've quickly discussed feature with Product Management, and the ROCm from the AMD repo will not be shipped as part of SLES => Leap.
Neal mentioned the existing thread about community effort around ROCm https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/VLLMW3HHO5Q4AZUI22RIFXAJHADCMBYL/
There it would have to be packaged for Factory first, and then it could be submitted to openSUSE Backports (Leap). Once it's in factory, feel free to submit it to backports right away. Meanwhile closing the issue.
Metadata Update from @lkocman: - Issue close_status updated to: Rejected - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.