Announcement

Collapse
No announcement yet.

Intel Still Making Source Engine Performance Optimizations

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

  • Intel Still Making Source Engine Performance Optimizations

    Phoronix: Intel Still Making Source Engine Performance Optimizations

    For those not actively following the Mesa Git repository, there continues to be new performance-optimizing patches flowing in from Intel's developers for their open-source Linux graphics 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
    That looks to my untrained eye to be a big improvement in reduction of instructions. Someone will have to actually benchmark to see what the real world effects will be though.

    Comment


    • #3
      I still have to pinch myself everytime I see a title like that.

      Comment


      • #4
        Originally posted by phoronix View Post
        Phoronix: Intel Still Making Source Engine Performance Optimizations

        For those not actively following the Mesa Git repository, there continues to be new performance-optimizing patches flowing in from Intel's developers for their open-source Linux graphics driver...

        http://www.phoronix.com/vr.php?view=MTQzNjQ
        I'm pretty sure this is one of the optimizations (but not the only) enabled for radeon by setting R600_DEBUG=sb on r600g.

        So, judging by that, it's unlikely to make much difference on the benchmarks michael runs, but can be very big on real applications like the Source games or WINE.

        Comment


        • #5
          Originally posted by smitty3268 View Post
          I'm pretty sure this is one of the optimizations (but not the only) enabled for radeon by setting R600_DEBUG=sb on r600g.
          Yes, r600g/sb has an if-conversion pass that produces the same result for the IF-MOV-ELSE-MOV-ENDIF pattern, though it's a bit more generic and handles almost any suitable conditional code, e.g. with more than one MOV in each branch, other instructions, nested IFs, etc.

          Originally posted by smitty3268 View Post
          So, judging by that, it's unlikely to make much difference on the benchmarks michael runs, but can be very big on real applications like the Source games or WINE.
          Many apps in Michael's benchmarks don't use shaders with conditional control flow at all, in such cases these optimizations have nothing to work on.

          Comment


          • #6
            This sounds like something the GLSL compiler should do, not the drivers. Why not? Does the IR not have a SEL equivalent?

            Comment


            • #7
              Originally posted by curaga View Post
              This sounds like something the GLSL compiler should do, not the drivers. Why not? Does the IR not have a SEL equivalent?
              Where do you think the compiler lives?

              Comment


              • #8
                Originally posted by Ancurio View Post
                Where do you think the compiler lives?
                It lives in src/glsl, while the drivers live under src/mesa/drivers and src/gallium/drivers. Having this kind of simplification in the GLSL compiler would be in one place, instead of duplicated in every driver.

                Comment


                • #9
                  does those optimizations in anyway relate to older cpus as well

                  Hi all,
                  Do these source engine perf. optimizations have any advantage for older generations of Intel CPU's as well ?

                  Comment


                  • #10
                    Anyone benchmark this yet?

                    Comment

                    Working...
                    X