-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for linux-drm-syncobj-v1 #409
Comments
Just to add:
So this would help nvidia cards greatly. |
Duplicate of #343 |
Mine was better |
Heh, I know |
Nvidia's XWayland explicit sync merge request was just merged: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967 From recent comments on NVIDIA/egl-wayland#104, it seems the Nvidia 555 driver should have explicit sync support for Wayland EGL, and for GLX. While Vulkan WSI support for it will be in 560. |
"Nvidia drivers do mot"? What that means? |
I believe that is a typo. "do mot support" is close to "do not support". M and N are next to each other on QWERTY keyboards. |
what is wrong in this?, explicit sync was merged everywhere expect this and wlroots |
It's being worked on (Smithay/smithay#1356, #411). This is most important with Nvidia drivers, and its still another month before there's an Nvidia beta driver that supports it. It will be good to have something working by then to test that XWayland is working better on Nvidia. It's potentially better for performance of Vulkan applications on Mesa drivers, but in most cases it shouldn't really have any noticeable impact. So it's not especially urgent. |
for nvidia users it's urgent may the 15th changes everything and i have a video that will let every nvidia user on ubuntu or arch even fedora and pop compile the patches and use them |
Implicit sync also causes serious problems for driver implementers and the entire userspace stack. See https://lpc.events/event/11/contributions/1115/attachments/929/1831/Why%20we%20can't%20have%20nice%20things.pdf. |
In recent developments, Linux desktop environments have been transitioning from implicit sync mechanisms to explicit sync. This shift aims to enhance performance, responsiveness, and overall user experience. Two prominent desktop environments, Mutter and Plasma, have already embraced this change, and more are following suit.
Here’s a breakdown of the key points:
Implicit Sync vs. Explicit Sync:
Implicit Sync: Traditionally, Linux desktop environments relied on implicit synchronization mechanisms. These mechanisms automatically synchronized various processes, such as rendering graphics, handling input events, and managing window updates. However, this approach sometimes led to inefficiencies and unnecessary resource consumption.
Explicit Sync: The move towards explicit synchronization involves giving developers more control over synchronization points. Instead of automatic synchronization, explicit sync allows developers to specify when synchronization should occur. This fine-grained control enables better optimization and reduces unnecessary overhead.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3300
Smithay/smithay#1356 Seems its a thing sorta may the 15th explicit sync comes to nvidia!
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967 was just merged also
The text was updated successfully, but these errors were encountered: