On Tue, Dec 04, 2001 at 02:42:46PM -0600, Eli Carter wrote:
> Well, I'm not sure that's accurate... what about interrupt handlers?
> There is something called "interrupt context" where kernel code is
> executed, but _not_ on behalf of some process (think receive of a packet
> for instance).
The time taken while running those int handlers is still charged to the
process that was running when the int happened, and calling blocking
functions or swtch() (sorry, traditional term, maybe it is schedule()
under linux) it is some random process that gets 'screwed'. :)
Hence the importance of not sleeping when in interrupt context. I
believe it is still called 'executing in process context', though, since
there *is* a 'current' -- you just shouldn't do anything with it. :)
Cheers
--
Join the fight against terrorism by giving up your liberties today!
PGP signature
