Announcement

Collapse
No announcement yet.

A Proof-of-Concept Vulkan Window Compositor Is In the Works

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

  • A Proof-of-Concept Vulkan Window Compositor Is In the Works

    Phoronix: A Proof-of-Concept Vulkan Window Compositor Is In the Works

    With Vulkan 1.1 it should be possible to write a pure Vulkan Wayland compositor while a Phoronix reader has tipped us off to a developer starting work on a proof-of-concept Vulkan window compositor...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Good news, but how many DEs will be able to enjoy it? I count 2 : Mate and Xfce, I wish it would work with Gnome and Kde or they can merge this work if it arrives to work

    Comment


    • #3
      Originally posted by mitcoes View Post
      Good news, but how many DEs will be able to enjoy it? I count 2 : Mate and Xfce, I wish it would work with Gnome and Kde or they can merge this work if it arrives to work
      If standard desktop (MATE) supports it it will be more than enough.

      Comment


      • #4
        that's the best real news of the whole year.

        Comment


        • #5
          I'm waiting as well for some news about the Vulkan renderer for Kwin :-)

          Comment


          • #6
            Originally posted by Azrael5 View Post
            that's the best real news of the whole year.
            How so?

            Vulkan is beneficial mostly to reduce draw call overhead.

            A window compositor does close to no work. It renders a few rectangles with a flat mapped texture on them.

            It will see minuscule to no benefit from Vulkan.

            Granted, it wouldn't hurt, but aside from the "cool factor" it is pretty much a pointless, albeit modest effort.

            Comment


            • #7
              Compiz used to take much cpu

              Comment


              • #8
                Hope this/ this idea gets turned into a framework , that actually sees real world use

                Comment


                • #9
                  Originally posted by ddriver View Post
                  How so?
                  What will be nice about this is not necessarily performance, but removing OpenGL ES as a requirement for accelerated Wayland desktops. It will allow for a minimal overall stack, probably less use of resources.

                  Also, as you know there's some performance overhead when running OpenGL games on an OpenGL desktop. I'm guessing this has to do with the driver managing multiple GL contexts. Perhaps with Vulkan this can be avoided?

                  Comment


                  • #10
                    So now we do care about cutting down on overheads, abstractions and dependencies? What happened to "let's port it to web assembly"

                    BTW I wasn't aware that OpenGL ES in particular is a requirement. In fact I am pretty sure it works with regular OpenGL, which will be a dependency for a bunch of software that will likely never get ported to Vulkan, and thus a necessity.

                    Comment

                    Working...
                    X