From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Question regarding interrupt handlers
Date: Wed, 9 Apr 2003 17:00:35 +0200 [thread overview]
Message-ID: <d0b51d52fc29b431519f00a2e30bddd5@plan9.escet.urjc.es> (raw)
In-Reply-To: <1049900092.4070.35.camel@utip129>
[-- Attachment #1: Type: text/plain, Size: 123 bytes --]
if you have to do something in `background' out of the interrupt handler
you can just create a kernel thread for the task.
[-- Attachment #2: Type: message/rfc822, Size: 2090 bytes --]
From: Martijn Punt <m.punt@student.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Question regarding interrupt handlers
Date: 09 Apr 2003 16:54:52 +0200
Message-ID: <1049900092.4070.35.camel@utip129>
Hi,
I'm relatively new to Plan 9 (and this mailinglist) and am currently
developing a device driver for a satellite tv-card for plan 9. My
previous experience is limited to Linux, and have a question about
interrupt handlers:
How do interrupt handlers in Plan 9 cope with large amounts of work
having to be done in order to handle an interrupt?
Is there a way to split the task in two parts, one to be handled
immediately and the other to be executed at a more convenient time?
Are there standard approaches for this problem in Plan 9, similar to the
approach of tasklets and bottom half processing in Linux?
Any help will be greatly appreciated,
Greets Martijn Punt
next prev parent reply other threads:[~2003-04-09 15:00 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 [this message]
2003-04-09 15:02 ` Sape Mullender
2003-04-10 9:24 ` C H Forsyth
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=d0b51d52fc29b431519f00a2e30bddd5@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).