From: "Christopher Friesen" <cfriesen@nortel.com>
To: "Sat." <walking.to.remember@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: when or where can the case occur in "linux kernel development " about "kernel preemption"?
Date: Fri, 26 Aug 2005 10:40:24 -0600 [thread overview]
Message-ID: <430F45F8.8020505@nortel.com> (raw)
In-Reply-To: <6b5347dc05082609206ff7a305@mail.gmail.com>
Sat. wrote:
> the case about kernel preemption as follow :
>
> the book said "when a process that has a higher priority than the
> currenty running process is awakened ".
>
> but I can think about when such case can occur , could you give me an example ?
There may be others, but one common case is when a hardware interrupt
causes the higher priority process to become runnable. Some examples of
this would be a network packet arriving, or the expiry of a hardware timer.
Chris
next prev parent reply other threads:[~2005-08-26 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 16:20 when or where can the case occur in "linux kernel development " about "kernel preemption"? Sat.
2005-08-26 16:40 ` Christopher Friesen [this message]
2005-08-27 15:57 ` Sat.
2005-08-28 7:05 ` Gaurav Dhiman
2005-08-29 11:46 ` linux-os (Dick Johnson)
2005-08-29 17:54 ` George Anzinger
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=430F45F8.8020505@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walking.to.remember@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