By: David Hess (davidwhess.delete@this.gmail.com), August 24, 2018 9:08 pm
Room: Moderated Discussions
Ricardo B (ricardo.b.delete@this.xxxxx.xx) on August 24, 2018 5:22 am wrote:
>
> Naively, I would say that the best approach for dealing with power hungry instructions
> would be to run at normal clock speed and restrict the instruction issue rate until
> some criteria are met and then down clock the core and un-restrict the issue rate.
Running at a slower clock would allow the extra complex instructions to take advantage of more gate delays per stage.
>
> Naively, I would say that the best approach for dealing with power hungry instructions
> would be to run at normal clock speed and restrict the instruction issue rate until
> some criteria are met and then down clock the core and un-restrict the issue rate.
Running at a slower clock would allow the extra complex instructions to take advantage of more gate delays per stage.
