From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Question regarding interrupt handlers
Date: Thu, 10 Apr 2003 10:24:39 +0100 [thread overview]
Message-ID: <f69d68141c2849995ce77133e6eec2a9@vitanuova.com> (raw)
In-Reply-To: <1049900092.4070.35.camel@utip129>
try this:
have the driver use kproc to create a kernel-only process (ie, kproc)
to do the less critical work;
do only the critical work in the interrupt handler; and have
the interrupt handler wakeup the kproc when there is work for
it to do. a kproc starts with a priority higher than user level
and if necessary you can use procpriority to adjust it.
if something else is running at a lower priority it will be pre-empted
at the end of the interrupt handler. (if not, it's a bug and can be fixed.)
you can use this technique as well to deal with interrupt-livelock
(eg, with networked systems under heavy load). there, the interrupt
handler and kproc also need to manipulate the interrupt-enable
of the device appropriately to ensure progress through a work queue.
the main difference between a kproc and a full process produced by
rfork() is that a kproc lacks a user address space, all kprocs
share a process group and name space, and starts with
no file descriptors. that's just to say there is
essentially only a single notion of a `process' from the point of view
of most of the system. there aren't tasks and processes, tasklets,
threads, filaments, looms, broadlooms, etc.
prev parent reply other threads:[~2003-04-10 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 14:54 Martijn Punt
2003-04-09 15:00 ` Fco.J.Ballesteros
2003-04-09 15:02 ` Sape Mullender
2003-04-10 9:24 ` C H Forsyth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f69d68141c2849995ce77133e6eec2a9@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).