It is an interesting approach but I cannot help but think what AMD needs to do is approach this with the Windows scheduler. Intel has thread director and it seems that AMD needs something similar, to organise which CCD to use and if particular threads should be scheduled together as part of SMT or even power gating particular CCDs on multi CCD designs.
Thread director is marketing speak. It's not actually directing the scheduling, but rather getting metrics to give the scheduler on the OS to help it make more informed decisions.
Here's a paper talking about it and its effectiveness https://pmctrack-linux.github.io/assets/papers/apsys22-saez.pdf
klonmeister@reddit
It is an interesting approach but I cannot help but think what AMD needs to do is approach this with the Windows scheduler. Intel has thread director and it seems that AMD needs something similar, to organise which CCD to use and if particular threads should be scheduled together as part of SMT or even power gating particular CCDs on multi CCD designs.
the_dude_that_faps@reddit
Thread director is marketing speak. It's not actually directing the scheduling, but rather getting metrics to give the scheduler on the OS to help it make more informed decisions.
Here's a paper talking about it and its effectiveness https://pmctrack-linux.github.io/assets/papers/apsys22-saez.pdf
Cheers
Shoddy-Ad-7769@reddit
Problem is it still needs to interface with Windows. 200 series for intel has been a disaster, and they admitted it.
kuddlesworth9419@reddit
I get the impression Microsoft is dragging their feet so AMD and the board partners are just doing what Microsoft should already be doing.
PC-mania@reddit
So Gigabyte goes beyond what ASUS is going with their Turbo mode. Interesting.
r1y4h@reddit
I kinda like the Gigabyte approach turbo mode approach.