autotldr@lemmings.world
on 12 Feb 2024 16:30
nextcollapse
This is the best summary I could come up with:
While there have been efforts by AMD over the years to make it easier to port codebases targeting NVIDIA’s CUDA API to run atop HIP/ROCm, it still requires work on the part of developers.
The tooling has improved such as with HIPIFY to help in auto-generating but it isn’t any simple, instant, and guaranteed solution – especially if striving for optimal performance.
In practice for many real-world workloads, it’s a solution for end-users to run CUDA-enabled software without any developer intervention.
Here is more information on this “skunkworks” project that is now available as open-source along with some of my own testing and performance benchmarks of this CUDA implementation built for Radeon GPUs.
For reasons unknown to me, AMD decided this year to discontinue funding the effort and not release it as any software product.
Andrzej Janik reached out and provided access to the new ZLUDA implementation for AMD ROCm to allow me to test it out and benchmark it in advance of today’s planned public announcement.
The original article contains 617 words, the summary contains 167 words. Saved 73%. I’m a bot and I’m open source!
BloodSlut@lemmy.world
on 12 Feb 2024 17:00
nextcollapse
amd real af for that
BloodSlut@lemmy.world
on 12 Feb 2024 17:02
nextcollapse
novideo’s existence setting the bar so low that im giving kudos to a traded for-profit company
“AMD decided this year to discontinue funding the effort and not release it as any software product”.
So AMD decided that it wasn’t worthwhile and so the developer released it on his own. AMDs decisions are just baffling. You still can’t even install Pytorch for rocm on Windows.
partial_accumen@lemmy.world
on 12 Feb 2024 17:31
nextcollapse
So AMD decided that it wasn’t worthwhile and so the developer released it on his own. AMDs decisions are just baffling.
AMD may have done this to avoid legal entanglements. It allows the solution to exist without a full endorsement from AMD and also lets the open source community drive it to where it needs to be as far as features and functionality.
eager_eagle@lemmy.world
on 12 Feb 2024 19:43
collapse
my thoughts too - now I really hope this project has a future in the open source env and it’s not just an ambitious endeavor
Along with what the other comment says, they could think that the project is in a good position to stand on its own now. It may have needed the funding to get to a good place where people will support it, but I’d bet it’s there now.
BombOmOm@lemmy.world
on 12 Feb 2024 17:09
nextcollapse
This is a big deal as it kills one of the major vendor lock-ins nVidia has. Gives people much more choice in the products they can buy to achieve their tasks.
rhebucks-zh@incremental.social
on 12 Feb 2024 19:08
nextcollapse
AMD now has the secret sauce. Now they need an architecture with proper dual-issue, and even a backport of the CUs onto RDNA3 structures for the RDNA4 lineup would be good, or 2025 RDNA5 would also be good.
downhomechunk@midwest.social
on 12 Feb 2024 20:05
collapse
Oddly enough, I’ve been trying to build rocm on slackware for the past week. It keeps failing out somewhere and throwing a HIP error that I can’t figure out. I wonder if this has anything to do with it.
threaded - newest
This is the best summary I could come up with:
While there have been efforts by AMD over the years to make it easier to port codebases targeting NVIDIA’s CUDA API to run atop HIP/ROCm, it still requires work on the part of developers.
The tooling has improved such as with HIPIFY to help in auto-generating but it isn’t any simple, instant, and guaranteed solution – especially if striving for optimal performance.
In practice for many real-world workloads, it’s a solution for end-users to run CUDA-enabled software without any developer intervention.
Here is more information on this “skunkworks” project that is now available as open-source along with some of my own testing and performance benchmarks of this CUDA implementation built for Radeon GPUs.
For reasons unknown to me, AMD decided this year to discontinue funding the effort and not release it as any software product.
Andrzej Janik reached out and provided access to the new ZLUDA implementation for AMD ROCm to allow me to test it out and benchmark it in advance of today’s planned public announcement.
The original article contains 617 words, the summary contains 167 words. Saved 73%. I’m a bot and I’m open source!
amd real af for that
novideo’s existence setting the bar so low that im giving kudos to a traded for-profit company
“AMD decided this year to discontinue funding the effort and not release it as any software product”.
So AMD decided that it wasn’t worthwhile and so the developer released it on his own. AMDs decisions are just baffling. You still can’t even install Pytorch for rocm on Windows.
AMD may have done this to avoid legal entanglements. It allows the solution to exist without a full endorsement from AMD and also lets the open source community drive it to where it needs to be as far as features and functionality.
my thoughts too - now I really hope this project has a future in the open source env and it’s not just an ambitious endeavor
Along with what the other comment says, they could think that the project is in a good position to stand on its own now. It may have needed the funding to get to a good place where people will support it, but I’d bet it’s there now.
This is a big deal as it kills one of the major vendor lock-ins nVidia has. Gives people much more choice in the products they can buy to achieve their tasks.
AMD now has the secret sauce. Now they need an architecture with proper dual-issue, and even a backport of the CUs onto RDNA3 structures for the RDNA4 lineup would be good, or 2025 RDNA5 would also be good.
Oddly enough, I’ve been trying to build rocm on slackware for the past week. It keeps failing out somewhere and throwing a HIP error that I can’t figure out. I wonder if this has anything to do with it.