User Level I/O
Some embedded and I/O intensive applications prefer to do most of their
I/O processing work in user space. They can do this through PIOs and mmap'ing their device registers. I'd like to present a feature that will allow them to handle interrupts in user space as well.
SGI's User Level Interrupt (ULI) feature allows applications to safely
do interrupt processing with user space handler functions. Applications get a high degree of control and a quick response (~3us) while ensuring that things like segfaults or infinite loops in the handler won't take down the OS. More information can be found at http://oss.sgi.com/projects/uli/.
I have ULI patches for IA64 on 2.6.10 and 2.6.11-rc4. On the web page
you can also find a support library, documentation, and very simple sample applications. The feature definitely isn't done yet but it's ready for people to start playing with. In particular, the code for handling infinite loops and supporting debugging is incomplete and the assembly needs to be cleaned up.
Please take a look at this and let me know what you guys think. We'd
like to get this integrated in 6.5.12 or soon after.
Thanks,
Michael
Signature · 2 lines
Michael A. Raymond Office: (651) 683-3434 Core OS Group Real-Time System Software
Quoted 1 line · Michael Raymond
like to get this integrated in 6.5.12 or soon after.
Slipping back into Linux numbers, 2.6.12.
Thanks,
Robin
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Robin" = Robin Holt <[email protected]> writes:
Robin> On Tue, Feb 22, 2005 at 10:59:57AM -0600, Michael Raymond
Quoted 1 line · Robin> wrote:
Quoted 1 line
like to get this integrated in 6.5.12 or soon after.
Robin> Slipping back into Linux numbers, 2.6.12.
How does this compare with the user-level interrupts stuff I've done?
http://www.gelato.unsw.edu.au/IA64wiki/UserLevelDrivers
Signature · 2 lines
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever*
Your project appears to wrap user I/O functionality together nicely. I
hadn't looked at it in a while but I'll try to come up to speed on it.
Where your work appears to differ is that you explicitly use a thread
for handling interrupts whereas ULIs run on whatever thread was running when the interrupt came in. Specifically, code running on the interrupt stack twiddles the TLBs so that the address space of the process that registered the ULI is addressable from the CPU. It then RFI's into user space, runs the handler, returns to the kernel, and resets the VM info. Depending on the scheduling load, ULIs can offer much better responsiveness.
I think that both approaches have their place.
Michael
Quoted 8 lines · Peter Chubb
How does this compare with the user-level interrupts stuff I've done?
http://www.gelato.unsw.edu.au/IA64wiki/UserLevelDrivers
Signature · 2 lines
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever*
Signature · 2 lines
Michael A. Raymond Office: (651) 683-3434 Core OS Group Real-Time System Software