From: Jonathan Larmour <jlarmour@redhat.com>
To: Xavier Wang <xavierwang@ms19.url.com.tw>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] nested interrupts
Date: Thu, 18 Jan 2001 22:37:00 -0000 [thread overview]
Message-ID: <3A67E092.F01CBE44@redhat.com> (raw)
In-Reply-To: <00e201c081d2$c303df20$6f2314ac@realtek.com.tw>
Xavier Wang wrote:
> But as I knew, ISRs should be as short as
> possible to reduce the time of masking interrupts and other non-critical
> stuff can be processed in DSRs. So I don't understand what the following
> means:
>
> "Bearing this in mind, the only thing DSR absolutely has to do is to
> notify the scheduler. All the rest ought to be done either in an ISR or
> in a thread."
The DSR should just wake or signal a thread to let it know that the
interrupt happened, that's all. You can't do that from an ISR. All other
processing should take place in a thread - both ISRs and DSRs should be
short and simple like that, otherwise you will lose determinism.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
next prev parent reply other threads:[~2001-01-18 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 23:51 Xavier Wang
2001-01-18 1:03 ` Jesper Skov
2001-01-18 4:15 ` Xavier Wang
2001-01-18 5:00 ` Nick Garnett
2001-01-18 4:59 ` Xavier Wang
2001-01-18 5:46 ` Nick Garnett
2001-01-18 21:52 ` Xavier Wang
2001-01-18 22:35 ` Jonathan Larmour
2001-01-18 8:26 ` Sergei Slobodov
2001-01-18 20:56 ` Xavier Wang
2001-01-18 22:37 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-11 0:03 [ECOS] Nested Interrupts Sandeep Rikhi
2000-09-11 7:53 ` Jonathan Larmour
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=3A67E092.F01CBE44@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=xavierwang@ms19.url.com.tw \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).