<div class="gmail_quote">2010/11/18 Justin Lee <<a href="mailto:justinlee5455@gmail.com">justinlee5455@gmail.com</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> This kind of latency due to OS scheduling could be eliminated by direct-procedure call. That is, the client passes the GEM buffer to the server just like it passes the GEM buffer as an argument to a function. In this approach, the compositor is not a process. Rather, the compositor is just a function live in the client program. So there will be no context switches. </blockquote></div> So ? Move wayland entirely into the kernel ? Then there will be no delay. And that's probably what MacOSX and Windows NT does. As far as I know, Darwin uses quantz (AGL?) as basis of their GUI system , but WIndows NT uses bullshit GDI .....