LCA: The ways of Wayland [LWN.net]

LCA: The ways of Wayland

Posted Feb 13, 2013 21:35 UTC (Wed) by lonely_bear (subscriber, #2726)
Parent article: LCA: The ways of Wayland

That situation leaves the X server itself with very little to do. Client applications draw everything locally, and the X server hands the drawing to the window manager to render it. The window manager hands back the rendered screen, and the X server "does what it's told" and puts it on the display.

I think this only apply to composite case, which I do not really found any useful case for my own daily usage. Without composite, the X server does handle quite a lots of things regarding windows drawing, and it is not nothing but a "terrible, terrible, terrible" inter-process communication (IPC) bus.

(Log in to post comments)

LCA: The ways of Wayland

Posted Feb 13, 2013 23:29 UTC (Wed) by airlied (subscriber, #9104) [Link]

even in the non-composite case, the server isn't doing a huge amount.

Its just doing the window contents copy mostly.

Though I do feel Daniel is being a mis leading, even if apps are rendering offscreen, a lot of them are using X render to do that rendering, so the server is still involved.

(granted X render can be slower than sw).

LCA: The ways of Wayland

Posted Feb 14, 2013 9:55 UTC (Thu) by daniels (subscriber, #16193) [Link]

They'd be better off using Pixman locally than a mix of local rendering and Render. :)