No announcement yet.

amdgpu questions

  • Filter
  • Time
  • Show
Clear All
new posts

  • #51
    Originally posted by duby229 View Post
    Not that overclockers will care much, but most GPU's are sold at very near their clock speed limits. It's been a long time since overclocking a GPU made any sense.
    Typically true though it can make a difference for <30/60 FPS cases when you just need a little more performance:,26.html


    • #52
      Originally posted by Xen0sys View Post
      Typically true though it can make a difference for <30/60 FPS cases when you just need a little more performance:,26.html
      ooh that's ugly. The MSI 390s already have exorbitant power targets. That beast with +50% power target and 1200 MHz will swallow a lot.
      Current gen Radeons aren't really overclockable easy. Something is holding them back and they are sold quite near their limits, as duby pointed out. Also, they have been very generous when it comes to voltages. All newer Chips (Hawaii, Fiji, Tonga) could be undervolted quite well. Nvidia's Maxwell was introduced well near their sweet spots with a lot of clock reserves and the boost with adaptive clocks/voltages seems to work better, too. If you really fine tune your Radeon, you can get quite close to the efficiency of Maxwell but most of them still don't overclock nice at all.

      That's also a bit problematic, as you can set a delta voltage in Windows with tools from Asus, MSI or Sapphire. But if you set a delta of e.g. -100 mV that could run nice in the highest dpm state but crash in the lower ones when the voltage drops too much. So for the fine tuning you need to adjust the vbios and tweak the voltage tables, which is not a nice solution.
      Would be nice, however to have access to the voltage tables without the risk of flashing the vbios...


      • #53
        In the commit history we can see that there is progress made in DAL, also with the help of redhat devs. In the discussion in the mailing list there were still concerns about DAL on general, even almost suggesting to drop completely.

        Can somebody tell something about the plans about this topic? It might not be a problem for the hybrid stack but when customers consider to move over to amdgpu all-open (e.g. for later open source vulkan and openCL support) they may lose functionality like adaptive sync or dp/HDMI audio.
        Talking about adaptive sync: Intel said to support it in the future. Is there any chance, code could be shared on a higher level? And are there any little tasks that new interested devs could jump into to make features like adaptive sync and in the long-term feature parity (or catching up to a point) for the open stack happen (faster)?
        Last edited by juno; 25 April 2016, 06:23 AM.


        • #54
          I saw this video:
          It's not very technical, I assume the functionality is in the Windows driver and VMWare or is this also possible with Linux? If not, are there plans for supporting this tech on Linux too?
          And is this limited to FirePRO hardware forever or also coming to radeons?

          edit: OK, got it. It's only for VMWare ESXi and vSphere. However, the question still stands: is support planned for amdgpu/kvm? This would basically make the need to passthrough obsolete, enabling multiple guests (win or linux) to utilise the same GPU...
          Last edited by juno; 22 May 2016, 08:39 AM.