Results 1 to 10 of 10

Thread: Intel Still Making Source Engine Performance Optimizations

  1. #1
    Join Date
    Jan 2007
    Posts
    13,398

    Default 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...

    http://www.phoronix.com/vr.php?view=MTQzNjQ

  2. #2
    Join Date
    Aug 2012
    Posts
    418

    Default

    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.

  3. #3
    Join Date
    Dec 2009
    Location
    Ontario
    Posts
    143

    Default

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

  4. #4
    Join Date
    Oct 2008
    Posts
    2,904

    Default

    Quote 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.

  5. #5
    Join Date
    Apr 2013
    Posts
    38

    Default

    Quote 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.

    Quote 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.

  6. #6
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,723

    Default

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

  7. #7
    Join Date
    Aug 2011
    Posts
    432

    Default

    Quote 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?

  8. #8
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,723

    Default

    Quote 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.

  9. #9
    Join Date
    Dec 2008
    Posts
    18

    Default 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 ?

  10. #10
    Join Date
    Aug 2012
    Posts
    418

    Default

    Anyone benchmark this yet?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •