From: ratheesh kannoth <ratheesh.ksz@gmail.com>
To: linux-newbie <linux-newbie@vger.kernel.org>
Subject: bottom half question
Date: Mon, 3 Dec 2012 17:56:57 +0530 [thread overview]
Message-ID: <CAGZFCEH__DQfr7-q-5F6JsffXwPHpaE5+235pjn=ib5XMH9M6g@mail.gmail.com> (raw)
In uni processor system ( 2.6 kernel )
An interrupt happened and ISR routine is serviced , then bottom
half scheduled and while the bottom half is running
1) Suppose same interrupt happened again - > then (the previous )
bottom half is preempted and ISR is serviced for new interrupt. After
ISR , same bottom half will be run again ? or the new one ?
2) if it is a new bottom half being run ,( since bottom half is in
interrupt context ) where it can store register info of previous
interrupt ?
3) Suppose a lot of interrupts happen in a short period of time , how
and when bottom half for each interrupt gets scheduled ?
-Ratheesh
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2012-12-03 12:26 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='CAGZFCEH__DQfr7-q-5F6JsffXwPHpaE5+235pjn=ib5XMH9M6g@mail.gmail.com' \
--to=ratheesh.ksz@gmail.com \
--cc=linux-newbie@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).