Announcement

Collapse
No announcement yet.

Likely Radeon Gallium3D Regression On Linux 3.14 + Mesa 10.2

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

  • Likely Radeon Gallium3D Regression On Linux 3.14 + Mesa 10.2

    Phoronix: Likely Radeon Gallium3D Regression On Linux 3.14 + Mesa 10.2

    For anyone currently experiencing a slowdown of their Radeon Gallium3D open-source driver stack or are interested in helping out track down a new performance issue, it appears the Linux 3.14 + Mesa 10.2 configuration is regressing on Ubuntu 14.04 LTS in place of Linux 3.13 + Mesa 10.1.

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

  • #2
    Originally posted by phoronix View Post
    Phoronix: Likely Radeon Gallium3D Regression On Linux 3.14 + Mesa 10.2

    For anyone currently experiencing a slowdown of their Radeon Gallium3D open-source driver stack or are interested in helping out track down a new performance issue, it appears the Linux 3.14 + Mesa 10.2 configuration is regressing on Ubuntu 14.04 LTS in place of Linux 3.13 + Mesa 10.1.

    http://www.phoronix.com/vr.php?view=19941
    HyperZ is disabled by default since this commit:
    http://cgit.freedesktop.org/mesa/mes...afe60faff48d84

    Comment


    • #3
      Originally posted by AnonymousCoward View Post
      HyperZ is disabled by default since this commit:
      http://cgit.freedesktop.org/mesa/mes...afe60faff48d84
      Aww, you beat me to it.

      I hope this is what Marek works on next. It'd be nice to finally get this working well.

      Comment


      • #4
        I do understand the reason for the change. I myself got bit by this one:
        https://bugs.freedesktop.org/show_bug.cgi?id=64471

        Let's hope these issues can be resolved so it can be re-enabled by default again.

        Comment


        • #5
          Whatever happened to those memory optimizations by curaga? No tests?

          Comment


          • #6
            curaga & Marek patches (both work on memory management code), are not in Mesa yet.

            Marek just posted patchset, while curaga have something cooking for this week or next. (Or thats what I read from comments below article about Marek patchset )

            In other words we may see that work done for 3.15/Mesa 10.2/10.3

            Comment


            • #7
              So now you write articles on testing and live versions of software? Maybe you should take a break instad, and improve articles that actually matter.

              Comment


              • #8
                Originally posted by genstorm View Post
                So now you write articles on testing and live versions of software? Maybe you should take a break instad, and improve articles that actually matter.
                Yeah. Because major regressions in performance are nobody concerns.

                STFU. And go play Angry Birds or something. Demanding that BENCHMARKING website stop BENCHMARKING is ....

                Comment


                • #9
                  Originally posted by genstorm View Post
                  So now you write articles on testing and live versions of software?
                  Why not? I was also wondering what is causing the performance drop, thanks to Michael and other people who made it clear, now I know the reason behind that.

                  Comment


                  • #10
                    Originally posted by przemoli View Post
                    Yeah. Because major regressions in performance are nobody concerns.
                    When they matter, e.g. in final versions, yes. Have YOU ever used software based on live sources? Regressions may happen on any commit, might be fixed in one of the following commits. In that case, where HyperZ has been disabled, you will get a fine Changelog entry with the final announcement, and all of those costly benchmarking and wondering 'what the heck degraded here' moments have been a waste of time. Time that is so badly missing to improve the poor average quality of other articles.

                    You can keep your insults to yourself.

                    Comment


                    • #11
                      Originally posted by genstorm View Post
                      When they matter, e.g. in final versions, yes. Have YOU ever used software based on live sources? Regressions may happen on any commit, might be fixed in one of the following commits. In that case, where HyperZ has been disabled, you will get a fine Changelog entry with the final announcement, and all of those costly benchmarking and wondering 'what the heck degraded here' moments have been a waste of time. Time that is so badly missing to improve the poor average quality of other articles.

                      You can keep your insults to yourself.
                      I do.

                      I'm literally using Mesa git.
                      And I recommend it to anyone who use OpenSuSE (pontostroy repos) or Ubuntu (oibaf repos).
                      Its easy, Its quick, and very benefitial.


                      And for sure its good to know that form now I need to set that HyperZ variable.

                      ("But its beta" is good excuse for CLOSED source projects, where onlything You can do is hope for the best, and only priorities of devs matter. In FLOSS You can grapple with the code Yourself. As some comment above showed.)
                      (Never played AB, though I have nothing against them nor against casual gamers, You included. As long as You do not demand that others start changing their behavior.)
                      Last edited by przemoli; 03-02-2014, 07:33 AM.

                      Comment


                      • #12
                        Originally posted by przemoli View Post
                        I'm literally using Mesa git.
                        And I recommend it to anyone who use OpenSuSE (pontostroy repos) or Ubuntu (oibaf repos).
                        Its easy, Its quick, and very benefitial.
                        You should never ever recommend it to any _regular_ user.

                        Originally posted by przemoli View Post
                        And for sure its good to know that form now I need to set that HyperZ variable.
                        Something that people found out by simply looking through the last few commits between 'normal' and 'degraded' state.

                        Originally posted by przemoli View Post
                        ("But its beta" is good excuse for CLOSED source projects, where onlything You can do is hope for the best, and only priorities of devs matter. In FLOSS You can grapple with the code Yourself. As some comment above showed.)
                        It doesn't matter for the majority of users to whom software development is a black box. They will not look into gitweb and search for the regression, but well, they shouldn't use it in the first place. They will be bothered by the news item though, while it is entirely possible that it will not matter for a final release and if, is going to be properly announced (or even taken care of by package maintainers).

                        Comment


                        • #13
                          Hm I never seem to get any problem with hyperz so how would I enable it? I using the oibaf PPA.

                          Change the flag to DBG_HYPERZ and reverse the logic
                          so setting the flag enabled the feature. This disables
                          hyperz on r600g and radeonsi by default. It can be
                          enabled by setting the env var.

                          Where can i apply the settings please?

                          Thank you

                          Comment


                          • #14
                            Originally posted by genstorm View Post
                            When they matter, e.g. in final versions, yes. Have YOU ever used software based on live sources?
                            I think mostly everybody who actually play games with open source drivers use Oibaf PPA or other sources with fresh Mesa as well as latest kernel. Also as games I mean not only SuperTuxKart or OpenTTD.

                            PS: I use those drivers from git for about a year and never get any serious glitch or GPU lockup because of that.
                            Last edited by _SXX_; 03-02-2014, 07:52 AM.

                            Comment


                            • #15
                              Originally posted by jonty789 View Post
                              Hm I never seem to get any problem with hyperz so how would I enable it? I using the oibaf PPA.
                              Set this environment variable:
                              R600_DEBUG=hyperz

                              Comment

                              Working...
                              X