From: "Dong Feng" <middle.fengdong@gmail.com>
To: Learning Linux <learninglinux4@gmail.com>
Cc: pradeep singh <2500.pradeep@gmail.com>,
Bahadir Balban <bahadir.balban@gmail.com>,
kernelnewbies@nl.linux.org, linux-newbie@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Why can't we sleep in an ISR?
Date: Tue, 15 May 2007 16:58:02 +0800 [thread overview]
Message-ID: <a2ebde260705150158m45286bd6u5007be863b6ff791@mail.gmail.com> (raw)
In-Reply-To: <9f1dc2cf0705150140k1fef87acvd774c7e171e4a660@mail.gmail.com>
Yes, you are right in this regard. An interrupt handler does steal the
time slice from the interrupted process.
So now I think it is considered an acceptable deviation in calculating
the process run time as well as determine process scheduling because
an ISR should take very short time to return, in part as a consequence
of the rule that ISR should not sleep.
2007/5/15, Learning Linux <learninglinux4@gmail.com>:
> > The interrupt handler's execution time will definitely defer the
> > execution of the process, but I think it does not steal the process's
> > time slice (the time_slice field not subtracted).
>
> It will definitely be substracted from the process's time slice.
> Because the timeslice is substracted in timer interrupt, and does not
> differenciate if the process is executing ISR or not.
>
-
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
next prev parent reply other threads:[~2007-05-15 8:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 6:37 Why can't we sleep in an ISR? Learning Linux
2007-05-14 7:10 ` pradeep singh
2007-05-14 7:16 ` Learning Linux
2007-05-14 15:24 ` Bahadir Balban
2007-05-14 15:56 ` Dong Feng
2007-05-15 5:17 ` pradeep singh
2007-05-15 6:45 ` Dong Feng
2007-05-15 7:10 ` pradeep singh
2007-05-15 7:28 ` Dong Feng
2007-05-15 8:12 ` pradeep singh
2007-05-15 8:40 ` Learning Linux
2007-05-15 8:58 ` Dong Feng [this message]
2007-05-15 16:57 ` Phillip Susi
2007-05-15 22:49 ` Dong Feng
2007-05-16 15:20 ` Phillip Susi
2007-05-16 23:17 ` Dong Feng
2007-05-17 16:07 ` Phillip Susi
2007-05-17 23:50 ` Dong Feng
2007-05-14 12:25 ` Helge Hafting
2007-05-14 12:52 ` pradeep singh
2007-05-14 13:36 ` Dong Feng
-- strict thread matches above, loose matches on Subject: below --
2007-05-14 15:22 linux
2007-05-14 15:55 ` Rik van Riel
2007-05-15 9:34 rohit hooda
2007-05-15 9:46 ` pradeep singh
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=a2ebde260705150158m45286bd6u5007be863b6ff791@mail.gmail.com \
--to=middle.fengdong@gmail.com \
--cc=2500.pradeep@gmail.com \
--cc=bahadir.balban@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=learninglinux4@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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