71
DirectX 12 'Work Graphs' aim to eliminate CPU bottlenecks by putting the GPU in charge
(www.tweaktown.com)
this post was submitted on 12 Mar 2024
71 points (97.3% liked)
Games
16806 readers
1127 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
GPU's as the ONLY compute source in a computer cannot and will not function, mainly due to how pipelining works on existing architectures (and other instructions)
You're right, in that GPU's are excellent at parallelization. Unfortunately when you pipeline several instructions to be run in parallel, you actually increase each individual instruction's execution time. (Decreasing the OVERALL execution time though).
GPU's are stupid good at creating triangles effectively, and pinning them to a matrix that they can then do "transformations" or other altering actions to. A GPU would struggle HARD if it had to handle system calls and "time splitting" similar to how an OS handles operating system background tasks.
This isnt even MENTIONING the instruction set changes that would be needed for x86 for example to run on a GPU alone.
TLDR: CPU's are here to stay for a really really long time.
... why would you run x86?
Nevermind that "cannot function" is not the same thing as "slow." Every reply has been a technically-proficient attack rather than sincere consideration of what is possible. The article is about rearranging the established relationship of CPU and GPU - the root comment asks "at some point." An all-caps dismissal of running existing software is a tell.
We're not talking about binaries you already have. We're not necessarily talking about general software. This is about future games. We're not even talking about a system with no CPU - the root comment describes reducing the importance of components. Crucial pieces of discrete hardware in past computers live on in modern motherboards as a tiny fraction of some chip.
Even CPUs themselves are experimenting with heterogeneous core layouts, where an itty-bitty Atom or ARMv7 handles the basics, while some wildly different silicon either sits idle or does all the work. The difference between that and an APU chewing through SPIR-V might be less than you think.
You are the one who brought up the question of even needing the CPU at all. Also, It wasn't meant to be an attack. Just an explanation as to why you'd still need a CPU.
All I meant was a large portion of software and compatibility tools still use it, and our modern desktop CPU architectures are still inspired from it. Things like CUDA are vastly different was my point
But if what you meant by your original comment was to not do away with the CPU, then yes! By all means, plenty of software is now migrating to taking advantage of the GPU as much as possible. I was only addressing you asking "at some point do we even need the CPU?" - the answer is yes :)