Announcement

Collapse
No announcement yet.

KWin-LowLatency: An Effort To Yield Less Stutter & Lower Latency With The KDE Desktop

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

  • KWin-LowLatency: An Effort To Yield Less Stutter & Lower Latency With The KDE Desktop

    Phoronix: KWin-LowLatency: An Effort To Yield Less Stutter & Lower Latency With The KDE Desktop

    The kwin-lowlatency project is an independent fork of the KWin window manager / compositor aiming to deliver less stutter and a more responsive KDE desktop experience...

    http://www.phoronix.com/scan.php?pag...in-Low-Latency

  • #2
    It's going to be rather useless with Wayland and Freesync. Someone should better continue the work on KWin over Vulkan.

    Comment


    • #3
      Typos:

      Originally posted by phoronix View Post
      at the moment.Additionally,
      (missing space after dot)

      Originally posted by phoronix View Post
      have said they didn't want to mege upstream.

      Comment


      • #4
        Always appreciated if somebody tries to improve kwin. I do use Plasma Wayland only nowadays, so it wan't be useful for me at the moment

        Comment


        • #5
          Originally posted by debianxfce View Post

          What is the point of this? You need X for games and other apps anyway.
          with that attitude, sure, we will always need it.

          Comment


          • #6
            Originally posted by debianxfce View Post
            "It is sad to see this kind of pro software in the Linux community as a stupidity developer.
            Word!

            Comment


            • #7
              There is something to consider here. Mainstream code is supposed to be as clean as possible, that is why new ideas get rejected way too often. The point is not to give up because you get rejected, it means that the new idea has to be refined to the point that it fits the mainstream of said project.
              This is common sense, just because developers does not say it in this manner, it is the underline principle.

              What bothers me is that people think rejection defines "no innovation" is borderline <self censor>.

              Comment


              • #8
                Originally posted by debianxfce View Post
                "Due to the explicit GLX usage and not yet receiving enough testing, the work isn't aiming for upstream KWin at the moment.Additionally, the developer is planning to merge the unredirected windows branch and that is code the upstream developers have said they didn't want to mege upstream."

                Make software better, this is only a dream because IBM,Amazon and "stable" believers. How can people test code when it is not merged, this is a big problem in Linux community. There is stupid reasons to block good ideas too often, for example nobody use kde with wayland and the radv config system. It is sad to see this kind of stupidity in the Linux community as a pro software developer.
                Really stop being clueless. IBM and Amazon don't work in the GUI field of KDE at all. Your nobody claim was bogus here counted straight by the next post.

                Originally posted by debianxfce View Post
                What is the point of this? You need X for games and other apps anyway.
                The question about "Vulkan" is interesting. Vulkan in the windows manager allows better cpu and gpu usage over opengl path. So you want to reduce added latency by compositor Vulkan is a good path. That is even if the compositor is running on X11.

                Lets follow this question forwards what do you really need with X11.

                Yes you need X but do you in fact need GLX. That interesting point xwayland uses a EGL(OpenGL ES) and forwards GLX to that and allows applications using EGL to bypass.

                1) EGL(OpenGL ES) can be used under X11 and Wayland.
                2) GLX is only under X11.
                3) No EGL support under X11 equals what.

                The reality here is no EGL support under X11 equals a stack of not working programs.

                Any sane developer looking at a X11 compositor patch that requires GLX and does not support EGL(OpenGL ES) applications would be saying that need to develop more before merging because who wants broken applications.

                Really this is not example of developer stupidity rejecting a patch. This is just another example of your stupidity debianxfce not understanding the interrelationships and requirements.

                Solutions under X11 for compositor need to support GLX and EGL applications running on X11. Wayland gets simpler even with xwayland your compositor only has to deal with EGL because all GLX is converted to EGL.

                GLX in the X11 server is one of areas that there is an internal API cluster of disaster behind it that need to go away to fix a stack of performance problems.

                https://www.phoronix.com/scan.php?pa...-Beta-3-Vulkan
                I forgot to include this. Long term GLX will be redirected to EGL or Vulkan and EGL will be redirected to Vulkan.

                So X11 running on top of Wayland long term everything could be just front end for Vulkan. Short term we are needing EGL support with wayland and xwayland glx is already redirected to EGL.
                Last edited by oiaohm; 05-08-2019, 03:59 AM.

                Comment


                • #9
                  Wayland will always be useless for gaming so long as they keep forcing Vsync, with no way to disable it.

                  The fact that Wayland and Gnome developers thought it would be okay to force Vsync and even hard cap the refresh rate to 60Hz (only recently fixed in Gnome), makes me have almost zero trust in them for gaming performance.

                  Comment


                  • #10
                    No wayland support = dead on arrival.

                    Comment

                    Working...
                    X