Announcement

Collapse
No announcement yet.

The GLX Rewrite Lands For X.Org Server 1.15

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

  • The GLX Rewrite Lands For X.Org Server 1.15

    Phoronix: The GLX Rewrite Lands For X.Org Server 1.15

    X.Org Server 1.15 hasn't been too exciting with not many prominent changes, but just ahead of the closure of the merge window, but the GLX rewrite has landed. The GLX rewrite will simplify the X.Org Server's use of OpenGL and drops a whole lot of code in the process...

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

  • #2
    I'm curious as to how much this will affect opengl based compositors in terms of performance/effeciency.

    Comment


    • #3
      The mere fact that 41,000 lines of code have been removed shows exactly why X belongs to the past.

      Comment


      • #4
        Impressive numbers of code line reduction - congratulations!
        And nice to see the rewrite included in the 1.15 version

        Comment


        • #5
          Yay!

          Dropping 41000 lines of code!
          Keep trimming it down!

          Make it lean and clean!
          Burn old legacy code!

          Comment


          • #6
            Originally posted by teahopper View Post
            The mere fact that 41,000 lines of code have been removed shows exactly why X belongs to the past.
            That's one way to see it...another is that with these cleanups, it will be possibly faster and more responsive.

            Taking in account that Wayland & Mir are yet far from be fully finished, it's a good thing for corrent users...and make things harder for Wayland / Mir to beat its performance

            Comment


            • #7
              I have great hopes for better stability, greater performance and lower latency.

              Comment


              • #8
                Originally posted by remenic View Post
                I'm curious as to how much this will affect opengl based compositors in terms of performance/effeciency.
                AFAIK it doesn't affect you at all, since it only changes a codepath you are not using any more: accelerated indirect rendering. That was used in composited environments before accelerated direct rendering to offscreen buffers was introduced, IIRC that was in DRI2.

                So, no difference unless you're running openGL apps via remote X, or DMX, or accelerated Xephyr, or ancient DRI1 drivers or something equally exotic.


                Maybe you get a reduced memory footprint. This is mainly for cleaner code.

                Comment


                • #9
                  Originally posted by AJSB View Post
                  Taking in account that Wayland & Mir are yet far from be fully finished, it's a good thing for corrent users...and make things harder for Wayland / Mir to beat its performance
                  Remember Wayland is mainly composed by X developers themselves. Goal of GLX rewrite is to remove all the X dependencies so Wayland can use it without pulling the legacy codes hence this part of Phoronix article:
                  just be linked against the GL API.
                  See Why does Wayland use EGL and GLES2?

                  Comment


                  • #10
                    Originally posted by finalzone View Post
                    Remember Wayland is mainly composed by X developers themselves. Goal of GLX rewrite is to remove all the X dependencies so Wayland can use it without pulling the legacy codes hence this part of Phoronix article:
                    just be linked against the GL API.
                    See Why does Wayland use EGL and GLES2?
                    I think that's a different issue. That one requires changes to libGL, not GLX (GLX will always stay X-specific, as the name implies).

                    Comment

                    Working...
                    X