|| ||Sven-Thorsten Dietrich <email@example.com>|
|| ||Thomas Gleixner <firstname.lastname@example.org>,
Jonathan Woithe <email@example.com>|
|| ||[ANNOUNCE] USB genirq infrastructure for threaded interrupt
|| ||Thu, 05 Mar 2009 00:40:18 -0800|
|| ||LKML <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Ingo Molnar <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Arjan van de Veen <firstname.lastname@example.org>,
Steven Rostedt <email@example.com>,
Jon Masters <firstname.lastname@example.org>|
|| ||Article, Thread
On Thu, 2009-02-26 at 13:28 +0000, Thomas Gleixner wrote:
> This patch series implements support for threaded irq handlers for the
> generic IRQ layer.
> Changes vs. V1:
> - review comments addressed
> - irq affinity setting for handler threads
I have forward-ported Thomas's patch set to 2.6.29-rc7, and added the
USB irq implementation for ohci, ehci and uhci.
A tar ball of the entire series is here:
After spending quite a bit of time looking at this implementation (and
The primary difference between the RT IRQ threading implementation, and
this one, is that the former implements mandatory per-LINE IRQ
threading, while the latter implements opt-in per-DEVICE IRQ threading.
The RFC "per-DEVICE" design can side-step the boot-IRQ quirks issue that
has plagued RT. But the opt-in design requires, that EVERY driver that
is to support IRQ threading must be modified.
Currently per-DEVICE design cannot cleanly support switching IRQs in and
out of thread context.
Last but not least, not all devices would be able to support IRQ
threading in this design. (RT has effectively no fall-out - practically
every piece of hardware works in that implementation)
The per-LINE design in RT brings with it a host of problems and
performance compromises, see the boot IRQ quirks work merged into
But the IRQ quirks issue can't be addressed for all chipsets, and
continues to be a problem on some hardware. This implementation would
also not completely eliminate that problem, depending on the device
palette presented and their IRQ arrangement / sharing.
The advantage of the RT per-line design, is that drivers modifications
are minimal, and just about every driver and every architecture works
with the existing implementation.
But per-line performance is abysmal under high IRQ loads when IRQs are
shared, and this has potential to boost throughput for RT. In some
cases, (multi-core) it might even boost throughput for the other PREEMPT
The ideal solution IMO, would be one where you can switch IRQs in and
out of thread context.
This would increase the tuning and debugging options, and not compromise
throughput for those who don't care for what threading can provide.
SO with those general comments, following is the punch list against my
1. IRQ threading will impact performance, and simply forcing it on, as
in the USB case, may not be an ideal solution. This design does not
allow the ability to turn on and off IRQ threading as the RT per-line
IRQ implementation does.
I'll run some benchmarks with what hardware I have here tomorrow.
2. Status tracking. The contents of the status register should be stored
in the IRQ (quickcheck handler, and used in the threaded portion). I
have added some debugging, and I can see the USB status registers
changing between running the quickcheck handler in IRQ context, and
executing the thread.
This would obviously happen if a USB device is plugged in, between IRQ
and thread execution, for example. But any USB activity causes status
USB drivers seem to be graceful enough to "catch up" on the changes.
Other hardware may not be as forgiving. What do you do - queue up a list
of status register snapshots, or just process the device as-is, when the
thread runs? What events may be missed? This is probably hardware
dependent, and possibly further driver-code mods may be needed to
3. Locking. USB has 3 primary implementations. Each use a different
degree of locking strictness, and this implementation requires adding
locks to be compatible with any possible RT implementation (because in
RT, the IRQ-context portion locks must be raw locks, while the thread
side locks must be mutexes to avoid all sorts of latency and
In general, there has to be at least some locking around the caching of
status registers, so that the quickcheck does not stomp of status
register bits being written by a yet incomplete thread-level execution.
I.e. the assumption is, that device level IRQs are not re-enabled until
the end of thread execution. This is probably not consistent with a lot
of driver implementations, which may assume that IRQ-context execution
This is the very terse version, just to put down some of my thoughts.
Overall, I would be curious about feedback on in implementation of this
on top of the RT tree.
IMO, a hybrid solution, where per-device as well as per-line IRQ
threading, and NO IRQ threading, are all possible to co-exist, would be
ideal both for variants.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/