Page 1 of 2 12 LastLast
Results 1 to 10 of 19

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

  1. #1
    Join Date
    Jan 2007
    Posts
    14,548

    Default 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. #2
    Join Date
    Oct 2007
    Posts
    7

    Default

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

  3. #3
    Join Date
    Mar 2013
    Posts
    10

    Default

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

  4. #4
    Join Date
    Jul 2013
    Location
    Germany
    Posts
    45

    Default

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

  5. #5
    Join Date
    Dec 2011
    Posts
    2,021

    Thumbs up Yay!

    Dropping 41000 lines of code!
    Keep trimming it down!

    Make it lean and clean!
    Burn old legacy code!

  6. #6
    Join Date
    Jul 2012
    Posts
    599

    Default

    Quote 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

  7. #7
    Join Date
    Jun 2010
    Posts
    149

    Default

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

  8. #8
    Join Date
    Nov 2008
    Posts
    764

    Default

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

  9. #9
    Join Date
    Nov 2011
    Posts
    271

    Default

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

  10. #10
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,537

    Default

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

Posting Permissions

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