[PATCH 3/3] xfree86: Add a conservative SIGIO handler path

Tiago Vignatti tiago.vignatti at nokia.com
Thu Oct 14 12:26:07 PDT 2010


On Thu, Oct 14, 2010 at 06:49:06PM +0200, ext Adam Jackson wrote:
> Instead of actually processing input in the handler, the conservative
> path just raises enough of a dispatch exception to bomb out of request
> processing and handle input instead.

ajax, I understand the rationale but would be great if you elaborate a bit
defending why we need _another_ method here. We're adding more complexity and,
for instance, we would have to justify the removal of this new method when
introducing the input-thread given I was already assuming like dead all SIGIO
paths.

So, to better accomplish this all, we need to perform and benchmark:
1. input thread
2. aggressive SIGIO (current one by default on linux) 
3. conservative SIGIO (raising up isItTimeToYield)
4. old input processing using the main thread handler


Do you have some thoughts on those?

             Tiago


More information about the xorg-devel mailing list