KDE On The Importance Of Wayland Explicit Sync
(www.phoronix.com)
from ylai@lemmy.ml to linux@lemmy.ml on 06 Apr 2024 19:14
https://lemmy.ml/post/14138782
from ylai@lemmy.ml to linux@lemmy.ml on 06 Apr 2024 19:14
https://lemmy.ml/post/14138782
Original blog: zamundaaa.github.io/wayland/…/explicit-sync.html
threaded - newest
This is the best summary I could come up with:
KDE KWin developer Xaver Hugl has written a detailed blog post for those interested in the topic.
Xaver Hugl has written a lengthy blog post explaining why Wayland explicit sync is a big deal and the issues it overcomes compared to the implicit sync model.
Besides some small-ish performance benefits, the big benefit for end-users with Wayland explicit sync is the NVIDIA proprietary driver being able to support it and in turn ironing out some of the remaining Wayland support challenges for that closed-source driver.
NVIDIA on Wayland flickering issues, frame pacing problems, and other challenges will be overcome with the NVIDIA explicit sync driver support paired with the Wayland compositor support and the likes of capable XWayland.
“With the explicit sync protocol being implemented in compositors and very soon in Xwayland and the proprietary NVidia driver, all those problems will finally be a thing of the past, and the biggest remaining blocker for NVidia users to switch to Wayland will be gone.”
The KWin merge request for implementing linux-drm-syncobj-v1 for explicit sync remains open with it still undergoing code review.
The original article contains 237 words, the summary contains 181 words. Saved 24%. I’m a bot and I’m open source!