Most of the tasklet uses are in rarely used or arcane drivers - in fact none of my 10 test-boxes utilizes _any_ tasklet in any way that could even get close to mattering to performance. In other words: i just cannot test this, nor do i think that others will really test this. I.e. if we dont approach this problem in some other way, nothing will happen and Steve's patch will be stalled forever and will live in -rt forever. (which might be a correct end result too, but i'm just not giving up this easily :-)
I've no idea but the drm uses tasklets to schedule the page flip or front/back blit as close to the vblank interrupt as possible to avoid tearing on vblank sync'ed applications (and compositing managers). I'm not sure we have any way to quantify this other than the closer to the irq the flip happens the better chance of the screen not tearing.. going forward where compositing is more used on a loaded system I wonder will we see more tearing on loaded systems.. I await the cleanups for the DRM code, it came from TG to support the above feature on Intel hw. Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
