[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081002153305.057cf6d9@infradead.org>
Date: Thu, 2 Oct 2008 15:33:05 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Greg KH <greg@...ah.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...l.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Steven Rostedt <rostedt@...dmis.org>,
Jon Masters <jonathan@...masters.org>,
Sven Dietrich <sdietrich@...e.de>
Subject: Re: [RFC patch 0/5] genirq: add infrastructure for threaded
interrupt handlers
On Thu, 2 Oct 2008 14:31:46 -0700
Greg KH <greg@...ah.com> wrote:
> On Thu, Oct 02, 2008 at 04:46:09PM +0200, Andi Kleen wrote:
> > Thomas Gleixner <tglx@...utronix.de> writes:
> > >
> > > - move long running handlers out of the hard interrupt context
> >
> > I'm not sure I'm really looking forward to this brave new world
> > of very long running interrupt handlers. e.g. what do you
> > do for example when some handler blocks for a very long time?
>
> We have this issue today with some irqs (USB is known for issue
> here...)
>
> So I don't think this is a big issue, and in the end, a better idea as
> it might force us to confront some of the big abusers and fix them.
>
one of the things irq threads gives you is that 'top' will show you
which ones are eating cpu ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists