4 ms·
I was waiting for things to stabilize a bit on the software and kernel side, for the last 3 years. First was to ensure the Kernel driver would work, then ROCM
by vkaku 4y ago
I was waiting for things to stabilize a bit on the software and kernel side, for the last 3 years.
First was to ensure the Kernel driver would work, then ROCM would work, then something like Tensorflow would work. If ROCM wasn't going to be there, it was PlaidML for me. A lot of that died in time.
Quite recently I decided to say f--- it and moved to Pytorch, Dockerized ROCM and things seemed to work great on most distros today.
I guess Pytorch did a better job of it than Google did in getting it to work on AMD cards. Ditto with Blender who used this stack on Windows a long time before the rest of us could get to.
Very recently I tried to HIPify most CUDA code and I was able to get it to work. AMD seem to be open to patches too. So that may be the best things that could happen to this platform moving forward.
What sucks with ROCM is that AMD are purposely removing older cards from ROCM and that is such a wasted opportunity for AMD. Kudos to that one guy who still ports the Polaris code to work with ROCM 5.4.x.
If they extended their attitude of graphics driver improvements for older cards to ROCM, it would Rock em.
Finally, I want to add this, if AMD would rather the community do a better job - it should let the community ship the next version. We'd all benefit - like Mesa. A lot of game consoles would highly benefit from this work too.