to thread the X server (?)
daniel at fooishbar.org
Thu Jun 19 01:52:49 PDT 2008
On Thu, Jun 19, 2008 at 09:39:22AM +0200, Xavier Bestel wrote:
> On Wed, 2008-06-18 at 23:14 +0200, Daniel Stone wrote:
> > On Wed, Jun 18, 2008 at 10:56:40PM +0200, Juliusz Chroboczek wrote:
> > > I appear to have missed part of the discussion. Why are you trying to
> > > multithread the X server? It will cause a lot of subtle bugs, and
> > > I don't see what it will buy you.
> > One interesting path I see with the input-in-a-separate-thread work is
> > eventually getting a complete path from hardware input event to client
> > delivery that cannot be blocked by rendering, meaning we always have
> > very low latency on input events.
> Xorg has a problem latency-wise: clients can block each other. When I
> play a video (in Totem), and simultaneously use a web browser, the video
> skips a lot - on a dual-proc system.
> I don't think just separating the input processing from the client
> requests processing will solve that.
Sure, but one problem at a time. :) Getting end-to-end independent input
processing is much, much, much easier than simultaneous client requests.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: Digital signature
More information about the xorg