Ingo wrote:
> > * Sven Dietrich <[EMAIL PROTECTED]> wrote: > > > This patch adds a config option to allow you to select > whether timer > > IRQ runs in thread or not. > > this patch only changes xtime_lock back and forth - it does > in no way impact the 'threadedness' of the timer IRQ. (it > does not move the timer IRQ into an interrupt thread.) > > nor do we really want to make it configurable - it's > non-threaded right now and we'll see what effect this has on > the worst-case latencies. > > Ingo > Its clear that there are all sorts of issues with process accounting and other race conditions associated with running the timer in a thread. The timer IRQ does have a noticable impact especially on the slower CPUS. In this domain, precise process time accounting may not be all that important, as long as the scheduler does not get confused, and that lone NODELAY IRQ doesn't get delayed (as much). It would be nice if some of the process accounting could be pipelined or deferred, but I don't have those answers right now. Sven - 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/
