Re:A simple Vulkan Compute example
by corysama on Sunday May 29, 2016 @11:04PM
(#11799334)
Short answer: Yes. But, it's pretty new. So, don't expect much pre-existing work today.
Long answer: Vulkan is a foundation for high-performance computing on GPU's. It includes SPIR-V which is intended as a compile target for higher level compute languages. https://www.khronos.org/spir
Re:A simple Vulkan Compute example
by leohutson on Sunday May 29, 2016 @08:21PM
(#11798906)
Zero cost interoperability with your graphics API is a big one. Using CUDA for compute, and then mapping that data into OpenGL to draw it is way slower than it should be.
Re:A simple Vulkan Compute example
by pandaman on Sunday May 29, 2016 @08:41PM
(#11798961)
Not to mention NVidia did not allow simultaneous compute and graphics workloads on the same SM until the newest 10 series GPUs while AMD had this since, at least, the very first GCN (2011?)
Re:A simple Vulkan Compute example
by shmerl on Sunday May 29, 2016 @10:31PM
(#11799237)
Wong question (CUDA isn't cross platform). I'd ask, how Vulkan compares to OpenCL? I think both intersect in some way, but Vulkan only focuses on GPU (compute and graphics), while OpenCL focuses only on compute but has more generic approach (GPU + CPU).
Re:A simple Vulkan Compute example
by corysama on Sunday May 29, 2016 @10:15PM
(#11799199)
Simple is not the same as easy.
Vulkan is not the convenience library. Vulkan is the ugly guts of the next twenty years of convenience libraries. If you enjoy Python, thank the systems programmers who implemented it in C. When you start enjoying some future SciPy-like system, thank the systems programmers who worked through 500 lines of this stuff before they could Hello Vulkan for your convenience.
Re:A simple Vulkan Compute example
by BonsaiDen on Monday May 30, 2016 @12:31AM
(#11799560)
Compared to the current situation of writing a few lines and then having to wait for a vendor specific day one graphics driver update to have your game actually running at halfway decent speed, it is simple.
The current APIs are a giant collection for graphics vendor specific driver "fixes" which had been implemented initially to cheat in benchmarks, and then later had to be implement to fix issues which arose from those initial cheats. It is a giant, ugly mess.
Also 95% of game developers will never ever touch a single line of vulkan because the engine developers of Unreal/Frostbite/CryEngine etc. will handle all of the "dirty work" for their abstractions to run on top of vulkan. All without the need of trying wo workaround vendor specific bug fixes etc.
Re:A simple Vulkan Compute example
by fsloth on Monday May 30, 2016 @01:55AM
(#11799798)
This sounds completely agreeable in GPU programming.
It's not feasible to provide elegant one liner solutions. It's about managing a state for a quite complex piece of hardware and the exact point of Vulkan was to provide a bare-metal low-overhead API without complicated utility routines. So yes, it's supposed to be like that.
Re:A simple Vulkan Compute example
by frign on Monday May 30, 2016 @12:50AM
(#11799612)
Yeah, I agree. Though, Vulkan is meant to be low-level, kind of like an ASM for Graphics Cards.
The euphemism of the article's title is too much though imho.
Long answer: Vulkan is a foundation for high-performance computing on GPU's. It includes SPIR-V which is intended as a compile target for higher level compute languages. https://www.khronos.org/spir
http://www.tomshardware.com/reviews/nvidia-geforce-gtx-1080-...
>simple
I don't know why people think shit like this is acceptable.
Vulkan is not the convenience library. Vulkan is the ugly guts of the next twenty years of convenience libraries. If you enjoy Python, thank the systems programmers who implemented it in C. When you start enjoying some future SciPy-like system, thank the systems programmers who worked through 500 lines of this stuff before they could Hello Vulkan for your convenience.
The current APIs are a giant collection for graphics vendor specific driver "fixes" which had been implemented initially to cheat in benchmarks, and then later had to be implement to fix issues which arose from those initial cheats. It is a giant, ugly mess.
Also 95% of game developers will never ever touch a single line of vulkan because the engine developers of Unreal/Frostbite/CryEngine etc. will handle all of the "dirty work" for their abstractions to run on top of vulkan. All without the need of trying wo workaround vendor specific bug fixes etc.
It's not feasible to provide elegant one liner solutions. It's about managing a state for a quite complex piece of hardware and the exact point of Vulkan was to provide a bare-metal low-overhead API without complicated utility routines. So yes, it's supposed to be like that.