Originally posted by jrch2k8
View Post
Announcement
Collapse
No announcement yet.
GNOME On Wayland Is Good For GNOME 3.10
Collapse
X
-
Originally posted by jrch2k8 View Postwell im pretty sure timestamps and vsync don't exclude each other but maybe a wayland dev could go into the details of how they can interact with each other, using simple logic you need at least the freq of the vertical refresh since it make no sense to render faster than the vertical refresh when you can use that exceeding time to save power or other more interestesting functions other than discard 300 frames without never reach a front buffer.
btw i mean vsync for weston and other compositor, couldnt edit after realize used the wrong word
[*] nothing about wayland requires that the compositor renders to the back buffer and does vsync'd page flips.. but for a UI, why would you do anything different?
Regarding performance/speed/whatever, wayland enables two important optimizations which are not really possible with X. First, with EGL_EXT_buffer_age, it is able to know the state of the new back-buffer after a flip, and only redraw what is out-of-date. So if you just have a small area of screen changing (moving a window, scrolling, etc), the gpu does not need to re-render the entire screen. (This one might become possible w/ X11 at some point.) And second, for hw that supports overlays, it can sanely utilize hw overlays in the display controller to bypass the gpu for some/all composition.
I'd guess that most compositing window managers that are being ported to wayland, in the first step they probably keep their existing rendering logic as it is just to get something working. Which doesn't take full advantage of the optimizations that wayland makes possible, but for the first step it is more important to get something into the hands of other developers so they can start working on updating apps, etc.
Comment
Comment