Announcement

Collapse
No announcement yet.

The Grinch That Stole The Radeon Gallium3D Performance?

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

  • The Grinch That Stole The Radeon Gallium3D Performance?

    Phoronix: The Grinch That Stole The Radeon Gallium3D Performance?

    There are some significant performance drops right now on Mesa master for the forthcoming 7.12/8.0 release concerning the Gallium3D driver for older ATI Radeon graphics processors. The performance of the R300g driver is now setback compared to earlier Mesa releases.

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

  • #2
    Sigh

    Phoronix - where articles ARE the bug reports

    Comment


    • #3
      Has anyone else got an r300 card handy to do a quick besect on? I'm running all r600's here

      Comment


      • #4
        Originally posted by FireBurn View Post
        Has anyone else got an r300 card handy to do a quick besect on? I'm running all r600's here
        The regressed commits should be published on Christmas.
        Michael Larabel
        http://www.michaellarabel.com/

        Comment


        • #5
          Also, please compare the visual output. Maybe about three screenshots over the duration of the test.
          Just to show whether it's just a performance regression or whether it actually renders more and better.

          Comment


          • #6
            You really have to write & publish guide how to compile and test out newest mesa drivers

            Comment


            • #7
              Originally posted by przemoli View Post
              You really have to write & publish guide how to compile and test out newest mesa drivers

              Code:
              git clone git://anongit.freedesktop.org/mesa/mesa
              Code:
              cd mesa
              The following is correct for a 64 bit stripped down mesa - make sure you have the 'devel' packages installed on your distro

              Code:
              ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
              --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-option-checking --enable-dri --enable-glx --enable-xcb --enable-texture-float
              --disable-debug --disable-egl --enable-gbm --disable-gles1 --disable-gles2 --enable-glx-tls --disable-osmesa --enable-asm --enable-shared-dricore
              --enable-shared-glapi --with-dri-drivers= --with-gallium-drivers=,swrast,r300 --disable-d3d1x --disable-gallium-g3dvl --enable-gallium-llvm --disable-openvg
              --disable-vdpau --disable-xvmc
              Code:
              make
              WARNING the next line will overwrite [possibly trash] your system's mesa

              Code:
              make install
              to bisect:

              Code:
              git bisect start
              Code:
              git bisect bad
              this marks the current git head as bad
              Code:
              git bisect good mesa-7.11.2
              says we know mesa 7.11.2 worked ok

              Then test a game that we know has regressed and for each run mark it as good or bad until it finds the rotten commit

              Then make and try again

              You shouldn't need to use "make install" but I can't for the life of me remember the environmental override that lefts you do MESAOVERRIDE=/lib/I/just/built mygame

              Hope that helps

              Comment


              • #8
                Off-topic, but the (not so apt or clever) references to Christmas and Holidays in pretty much every article (and even some comments) is a bit over the top for a relatively technical website. (And that's an understatement.)

                Merry Christmas and Happy Holidays.

                Comment


                • #9
                  Originally posted by FireBurn View Post
                  You shouldn't need to use "make install" but I can't for the life of me remember the environmental override that lefts you do MESAOVERRIDE=/lib/I/just/built mygame
                  LD_PRELOAD or LD_LIBRARY_PATH for libgl.so, and LIBGL_DRIVERS_PATH I think.

                  Comment


                  • #10
                    Originally posted by AnonymousCoward View Post
                    LD_PRELOAD or LD_LIBRARY_PATH for libgl.so, and LIBGL_DRIVERS_PATH I think.
                    If someone can confirm that I'll update my post

                    Comment


                    • #11
                      Originally posted by FireBurn View Post
                      If someone can confirm that I'll update my post
                      I've for sure done it with LD_LIBRARY_PATH=X LIBGL_DRIVERS_PATH=X

                      I'm not sure if both of those are necessary - i think it's just one of them.

                      Comment


                      • #12
                        Originally posted by smitty3268 View Post
                        I've for sure done it with LD_LIBRARY_PATH=X LIBGL_DRIVERS_PATH=X

                        I'm not sure if both of those are necessary - i think it's just one of them.
                        LIBGL_DRIVERS_PATH=/path/to/mesa/lib/gallium is always needed, this is the location where your r300_dri.so is.
                        LD_LIBRARY_PATH=/path/to/mesa/lib is needed for mesa's libGL.so, however usually your system stock libGL.so is sufficient.

                        Comment


                        • #13
                          This analysis confirms that performance is an important issue the gallium3d drivers need to address. Gallium 3d developers have implemented more and more features to their drivers and that is great, but sometimes I think that this has been at the cost of performance (which is far behind proprietary drivers).
                          Also, I am curious of how much attention do older hardware drivers get. Maybe this is not an issue for some, but here in third world countries we run a lot of older hw in our machines.
                          Anyway I am confident that these performance issue will be resolved. =)



                          Merry Christmas.

                          Comment


                          • #14
                            Originally posted by zwastik View Post
                            This analysis confirms that performance is an important issue the gallium3d drivers need to address. Gallium 3d developers have implemented more and more features to their drivers and that is great, but sometimes I think that this has been at the cost of performance (which is far behind proprietary drivers).
                            Also, I am curious of how much attention do older hardware drivers get. Maybe this is not an issue for some, but here in third world countries we run a lot of older hw in our machines.
                            Anyway I am confident that these performance issue will be resolved. =)

                            Merry Christmas.
                            https://twitter.com/#!/michaellarabe...60220548927488
                            https://twitter.com/#!/michaellarabe...62664813146112
                            Michael Larabel
                            http://www.michaellarabel.com/

                            Comment


                            • #15
                              Originally posted by FireBurn View Post
                              Sigh

                              Phoronix - where articles ARE the bug reports
                              Phoronix, where they post better articles than just reprints of ads.

                              Comment

                              Working...
                              X