From: "Learning Linux" <learninglinux4@gmail.com>
To: "Dong Feng" <middle.fengdong@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 14:10:52 +0530 [thread overview]
Message-ID: <9f1dc2cf0705150140k1fef87acvd774c7e171e4a660@mail.gmail.com> (raw)
In-Reply-To: <a2ebde260705150028j16cc12a2ya6d5906c97ce193b@mail.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.
next prev parent reply other threads:[~2007-05-15 8:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 6:37 Learning Linux
[not found] ` <366312910705140010m78b215a2t1753445e81120288@mail.gmail.com>
2007-05-14 7:16 ` Learning Linux
2007-05-14 15:24 ` Bahadir Balban
2007-05-14 15:56 ` Dong Feng
[not found] ` <366312910705142217geba69dbm98a6c0bf2aabb937@mail.gmail.com>
2007-05-15 6:45 ` Dong Feng
[not found] ` <366312910705150010p623f9732mc498f457245d23a1@mail.gmail.com>
2007-05-15 7:28 ` Dong Feng
2007-05-15 8:40 ` Learning Linux [this message]
2007-05-15 8:58 ` Dong Feng
2007-05-15 16:57 ` Phillip Susi
2007-05-15 17:23 ` David Schwartz
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
[not found] ` <366312910705140552o6a507cbbl806f2ad0efc9d90c@mail.gmail.com>
2007-05-14 13:36 ` Dong Feng
2007-05-14 15:22 linux
2007-05-14 15:55 ` Rik van Riel
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=9f1dc2cf0705150140k1fef87acvd774c7e171e4a660@mail.gmail.com \
--to=learninglinux4@gmail.com \
--cc=2500.pradeep@gmail.com \
--cc=bahadir.balban@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=middle.fengdong@gmail.com \
/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
all inboxes | Powered by JetHome®