https://bugzilla.redhat.com/show_bug.cgi?id=2240414
Ben Woodard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Ben Woodard <[email protected]> --- (In reply to Tom Rix from comment #3) > I am wondering if rocm shouldn't be handled like mpi by using modules. > We are always going to switch a set of libs from multiple packages at the > same time. > instead of the mpi, we would have rocm gpu family backends. > ex/ > setenv ROCM_LIB /usr/lib64/rocm/gfx11/lib > prepend-path LD_LIBRARY_PATH /usr/lib64/rocm/gfx11/lib > > and there would be new package like rocm-module to set this up. > > Here is an example of what Benson suggested for gloo > https://bugzilla.redhat.com/show_bug.cgi?id=2240302 > https://copr-dist-git.fedorainfracloud.org/cgit/fed500/gloo/gloo.git/tree/ > gloo.spec?id=5f4092aba4f411ac9a10fc05d14aeab8909df3d9 I'm not sure that this would work. As Cordell pointed out many users have multiple different GPUs installed in their system. This won't be as much of a problem in the enterprise space where graphics aren't really a thing but many systems are built with APUs (combined CPU+GPU) packages and then they install a DGPU like a Radeon 7900 XT. How would that work with your alternative's ligic? You would need two to be active at once. I agree, that you should roll everything forward to 5.7 and in the back of your mind consider how to maintain compatibility when rocm 6 rolls out. It is supposed to be a break API release. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2240414 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202240414%23c4 _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
