Announcement

Collapse
No announcement yet.

AMDVLK 2021.Q2.2 Brings Minor Improvements But No Vulkan Ray-Tracing Yet

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • AMDVLK 2021.Q2.2 Brings Minor Improvements But No Vulkan Ray-Tracing Yet

    Phoronix: AMDVLK 2021.Q2.2 Brings Minor Improvements But No Vulkan Ray-Tracing Yet

    AMD engineers today published AMDVLK 2021.Q2.2 as their latest open-source public code drop of their official Linux Vulkan driver...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Didn't AMD release "Radeon for Linux" package with ray tracing? It's not using amdvlk?

    Comment


    • #3
      Originally posted by shmerl View Post
      Didn't AMD release "Radeon for Linux" package with ray tracing? It's not using amdvlk?
      Closed source package Ray Tracing extension. Open stack still not.

      Comment


      • #4
        Different compiler backends.

        Comment


        • #5
          Originally posted by agd5f View Post
          Different compiler backends.
          I see. So AMD are still not happy with LLVM overall to keep a separate closed compiler?

          Comment


          • #6
            Originally posted by shmerl View Post
            I see. So AMD are still not happy with LLVM overall to keep a separate closed compiler?
            I don't think you'd ever want consumers to deal with the slow shader compile times, and also deliberately decreasing performance isn't a good idea with a competitor like Nvidia.

            Comment


            • #7
              Originally posted by aufkrawall View Post
              I don't think you'd ever want consumers to deal with the slow shader compile times, and also deliberately decreasing performance isn't a good idea with a competitor like Nvidia.
              llvm isn't that bad overall. Sure ACO is an improvement though. May be AMD can use that as an open option.

              Comment


              • #8
                Originally posted by shmerl View Post
                llvm isn't that bad overall.
                The compile times of the amdvlk-open compiler are definitely really, really bad. I haven't tested with Navi, but with Polaris it was several times worse than upstream LLVM. When a game has lots of shaders, it can take over an hour to compile them all at once (which most Vulkan and D3D12 games do) with a slow CPU & amdvlk-open. With ACO, it would be a matter of a few minutes.

                Comment


                • #9
                  I do not understand, why
                  AMD needs a closed AND and an open source driver.

                  That sounds to me like a lot of work has to be done twice.
                  But why?

                  Comment


                  • #10
                    obri because some commercial customers still using old distro and kernel and they need provide support for them. OpenSource drivers working fine mostly for rolling base distro or with some hacks around not so old (with a custom kernel and mesa/drm and llvm).

                    Comment

                    Working...
                    X