Calling from the timer into a regular process sounds risky.
What if the user code page faults? What if it loops endlessly (you're
already in the timer BH, remember)? These issues could probably be
worked out (page locking, special timer faults, etc.), but...
The crucial issue is real-time response. Given that
constraint, it might be reasonable (depending upon other
characteristics of your application) to recode your application (or
its time-critical parts) as a loadable kernel module. Except for
whatever hooks (if any) it uses in more general code, your loadable
module won't be contributing to *everyone's* kernel bloat.
By the way, have ou considered implementing your time-critical
section(s) for RTLinux (Real-Time Linux)? This would seem like an
ideal application.
Craig Milo Rogers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html