From: milton@krutt.org (Milton Krutt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [milton@krutt.org: Re: Delaying an interrupt handler]
Date: Wed, 8 Apr 2015 18:53:29 +0200 [thread overview]
Message-ID: <20150408165329.GA3971@debian> (raw)
----- Forwarded message from Milton Krutt <milton@krutt.org> -----
Date: Tue, 7 Apr 2015 18:46:46 +0200
From: Milton Krutt <milton@krutt.org>
To: Malte Vesper <malte.vesper@postgrad.manchester.ac.uk>
Subject: Re: Delaying an interrupt handler
Not that late! I take your advice, and I inform all the folks who
suggested me to jump on a new kernel that now I am on a 3.19! So their
hints are still welcome. Bye
> Despite beeing fairly late, take a look at threaded interrupt
> handlers, they might help you. You will handle the interrupt fast
> but you can delay doing the actual work. In the threaded part of the
> interrupt handler you can sleep and thus use semaphores.
>
> hope it is still useful
----- End forwarded message -----
reply other threads:[~2015-04-08 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150408165329.GA3971@debian \
--to=milton@krutt.org \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).