Live data from Hacker News

AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

phoronix.com

361–370 of 425 posts

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#361

As I understand, Vulkan allows to run custom code on GPU, including the code to multiply matrices. Can one simply use Vulkan and ignore CUDA, PyTorch and ROCm?

of course, but then you are just recreating CUDA. And that won’t scale well across an industry since each company would have their own language. AMD can just do what you are describing and then sell it as a standard.

I mean they literally did that, but then dropped it so yea

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#362
post #229

Earlier quoted context omitted.

> However, Microsoft has definitely been drinking the IBM koolaid a little to long and has lost the mandate of heaven. I think in the next 7-10 years we will reach a point where there is nothing Windows can do that linux cannot do better and easier without spying on you that's a fascinating statement with the clear ascendancy of neural-assisted algorithms etc. Things like DLSS are the future - small models that just…

Counterpoint: Most AI stuff is developed on either an OS agnostic language like Python or C, and then ported to Linux/OSX/Windows, so for AI it is less about the OS it runs on than the hardware, drivers, and/or connections that the OS supports. For the non-vendor lock in AI's (copilot), casting as wide of a net as possible to catch customers as easily as possible should by default mean that they would invest the smal…

Most AI dev that I've seen tends to be done on Linux or MacOS first. Certainly the research and training are, because HPC tends to be Linux. And of course, the models are deployed in containers, a Linux technology, to webservers running Linux.

MS has put a collosal amount money into catching up to at least be able to take advantage of the AI wave, that much is clear. Maybe for consumers this will be enough, but R&D wise I don't see them ever being the default choice.

And this is potentially a huge problem for them in the long run, because OS choice by industry is driven by the available tooling. If they lose ML, they could potentially lose traditional engineering if fields like robotics start relying on Linux more heavily.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#363
post #24
post #3

> after the CUDA back-end was around for years and after dropping OpenCL, Blender did add a Radeon HIP back-end... But the real kicker here is that using ZLUDA + CUDA back-end was slightly faster than the native Radeon HIP backend. This is absolutely crazy.

Is AMD just a puppet org to placate antitrust fears? Why are they like this?

Like Mozilla?

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#364

Earlier quoted context omitted.

Sounds ridiculous, why have a public presence on a social network then?

oh. I think the emphasis is on hacker news. you know certain social media sites contain certain toxic conversants.

HN isn't very toxic. You must be confusing it with another social media site.

If anything, the Asahi devs are the ones acting out.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#365
post #261

Earlier quoted context omitted.

fertile soil for Alyssa and Asahi Lina :) https://rosenzweig.io/ https://vt.social/@lina

I know that Lina doesn't like a lot of the attention HN sends her way so it may be better if you don't link her socials here.

I think it would be better to avoid mention of them (or the Asahi project) on HN entirely, for that matter.

If they don't want HN to criticize them, then they should expect to not get the free publicity that HN offers. Seems fair enough.

Also, between accusing HN of "supporting trans genocide" (which is some mix between "impossible" and "false"), and poisoning links with HN referrer URLs, they don't seem like very good people themselves.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#366
From the same repo, I found this excellent, well-written architecture document: https://github.com/vosen/ZLUDA/blob/master/ARCHITECTURE.md

I love the direct, "no bullshit" style of writing.

Some gems:

> Anyone familiar with C++ will instantly understand that compiling it is a complicated affair.

> Additionally CUDA allows, to a large degree, mixing CPU code and GPU code. What does all this complexity mean for ZLUDA? Absolutely nothing

> Since an application can dynamically link to either Driver API or Runtime API, it would seem that ZLUDA needs to provide both. In reality very few applications dynamically link to Runtime API. For the vast majority of applications it's sufficient to provide Driver API for dynamic (runtime) linking.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#367

Earlier quoted context omitted.

> I'm really rooting for AMD to break the CUDA monopoly Personally I want Nvidia to break the x86-64 monopoly, with how amazing properly spec'd Nvidia cards are to work with I can only dream of a world where Nvidia is my CPU too.

How would this a good idea? I am not very familiar with GPU programming but the small amount I've tried was nothing but pain a few years ago on linux, it was so bad that Torvald publicly used the f word in a very public event. That aside, CUDA seem like a great way to lock people in even further like AWS does with absolutely everything

>I am not very familiar with GPU programming but the small amount I've tried was nothing but pain a few years ago on linux, it was so bad that Torvald publicly used the f word in a very public event.

I'm pretty sure Torvalds was giving the finger over the subject of GPU drivers (which run on the CPU), not programming on the Nvidia GPU itself. Particularly, they namedropped Bumblebee (and maybe Optimus?) which was more about power-management and making Nvidia cooperate with a non-Nvidia integrated GPU than it was about the Nvidia GPU itself.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#368

As I understand, Vulkan allows to run custom code on GPU, including the code to multiply matrices. Can one simply use Vulkan and ignore CUDA, PyTorch and ROCm?

ncnn uses Vulkan for GPU acceleration, I've seen it used in a few projects to get AMD hardware support.

https://github.com/Tencent/ncnn

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#369
post #60

The interest in this thread tells me there are a lot of people who are not cool with the CUDA monopoly.

AMD's budget isn't measured in people, it's measured in dollars. HN commenters don't necessarily decide how many graphics cards their business will buy.

Re: AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source

#370

Earlier quoted context omitted.

Yes. This is what makes Nvidia's toolchain, if not great, at least ok. As a developer I can actually use their GPUs. And what I developed locally I can yhen run on Nvidia hardware in the cloud and pay by usage. AMD doesn't seem to understand that affordable entry-level hardware with good software support is key.

Ah yes, so that one does seem to be a stumbling block. ROCm is not remotely convinced that running on gaming cards is a particularly useful thing. HN is really sure that being able to develop code on ~free cards that you've got lying around anyway is an important gateway to running on amdgpu. The sad thing is people can absolutely run ROCm on gaming cards if they build from source. Weirdly GPU programmers seem determ…

Maybe someone that's trying to use a GPU to solve a particular problem doesn't necessarily also have the time, energy, knowledge, or interest to also first 1) find out how to construct the toolchain, 2) build said toolchain, and 3) debug the toolchain. Just because you're a programmer writing code for physics simulations, image processing, AI models, or whatever, doesn't mean you also want to spend hours or days on getting your tools working before you can even start writing your own code. And then do it again when deploying on another computer.

And it's really not surprising that people, GPU programmers included, doesn't want to spend time and money on trying out unsupported hardware and software combinations when again, it's supposed to be a tool to get a job done. If I got some Phillips head screws I'm not reaching for a flat head screwdriwer even though it probably will work, and if it's the only thing I have I'll buy some Phillips head ones for the next project.

Post reply on HN