It'll probably behave as it does now if you try using unified memory in Metal (i.e., you will get an error). It's currently only valid in iOS/iPad/iEtc devices.
It looks like Apple will be going it's own way with GPU, as tight integration between GPU and CPU enables much better performance. Think vias rather than buses.
The higher end Macs should see some large on-chip (or part of chiplet array) GPU implementations.
It'll largely be transparent at the Metal API level.
Interestingly, from a business perspective this is mainly bad for AMD.
At 13:50, is he saying that x64 code running under Rosetta will enjoy TSO memory ordering? Is Apple implementing something stricter than the ARM memory model in their own silicon, maybe with a mode bit that Rosetta gets to set?
9 comments
[ 0.26 ms ] story [ 34.7 ms ] threadYou can find some of Gavin's prior work on ioccc :D
x86 is a trainwreck.
Have a look here: https://developer.apple.com/documentation/metal/mtlstoragemo...
I guess there will be a compile-time flag that you can #ifdef to check if you are on a new Apple Silicon mac or not.
The higher end Macs should see some large on-chip (or part of chiplet array) GPU implementations.
It'll largely be transparent at the Metal API level.
Interestingly, from a business perspective this is mainly bad for AMD.
I was thinking to shift to Surface Book 3 but i think i should wait until end of this year.