No you don’t as I understand it. The point of HSA is the hardware doesn’t matter as you don’t code for a single types of hardware, don’t code for cores. You don’t even code for the CPU or GPU. You use the entire system compute power.“No, you still have to sufficiently 'thread' your code to take advantage of any increase in execution units.” “Unfortunately it doesn't magically solve the problem of how do you spread your code over many execution units. Code still has to be written to take advantage of 'moar corez'.”
You seem to be missing the point of HSA. When the standard is created it can be used on the desktop and you can swap away from Intel. HSA means you can use MIPS, ARM, AMD interchangeable. You are not fixed into a one hardware type.“HSA will likely gain some traction in the mobile ARM space, but with only AMD backing it on the desktop/laptop/server (ok the ARM guys have some hardware here nobody is currently interested in) space it's not going anywhere quickly there.”
No one is going crazy or beating down points as it didn’t fit our agenda. You completely misunderstood the situation then started blaming us. I directly asked you questions in a polite matter and all you did was go crazy at us. The very thing you are accusing us of. I am trying to discuss the points but you don’t seem to want to.“Why cant we have nice things, why cant points be raised without some going crazy? Nobody wanted to discuss my points, only beat them down because it didn't fit the agenda.”
That’s not the main premise of HSA it’s in the list of requirements for HSA though. The main premise of HSA is that the high level language is used so you are not locked into a single hardware solution. The premise is that you don’t have to recode the application when swapping between CPU’s, GPU brand. You don’t code for a single CPU or GPU or set amount of cores. You code in the high level language and HSA makes use of the entire system compute power.“The main premise of HSA is to allow CPU and GPU to work as one,”
The goal of HSA is that it’s not feasible to keep coding for dozens of hardware platforms. So you run one code across all the platforms. Making it so you can swap GPU and CPU without new code. I don’t see how Nivida are doing anything comparable to that and would go as far to say NVlink is the opposite to the goal of HSA.
Shared memory is part of the list of requirements for HSA. It is not the main premise of HSA.
That’s not true at least 3 of the CPU makers want HSA and want to work in servers.“You say HSA is a standard. But it's a standard for markets where the current incumbents have no interest in taking any part of.”
Last edited: