From: Robert Love <rml@tech9.net>
To: Akram.Abou-Emara@nokia.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Threads question on 2.4
Date: 03 Feb 2003 19:59:30 -0500 [thread overview]
Message-ID: <1044320369.783.117.camel@phantasy> (raw)
In-Reply-To: <F0B628F30F48064289D8CCC1EE21B7A8026B2335@mvebe001.americas.nokia.com>
On Mon, 2003-02-03 at 19:52, Akram.Abou-Emara@nokia.com wrote:
These questions might be better asked on the kernelnewbies list...
> Do kernel threads get preempted? Or do they have to
> give up the CPU on their own?
Without the preemptive kernel, they are not preemptive. With
preempt-kernel, they are. They tend to run at elevated priorities
anyhow, so this is not so much of an issue.
> Are there any rules for what scheduling policies and
> priority a kernel thread can have?
> reparent_to_init()sets the scheduling policy to
> SCHED_OTHER. Do you see a problem with changing the
> scheduling policy to SCHED_FIFO?
kernel threads can have any scheduling policy or priority - they really
do not differ much from regular threads (sans the lack of address
space).
Some kernel threads do indeed run with real-time policy.
Robert Love
prev parent reply other threads:[~2003-02-04 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 0:52 Kernel Threads question on 2.4 Akram.Abou-Emara
2003-02-04 0:59 ` Robert Love [this message]
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=1044320369.783.117.camel@phantasy \
--to=rml@tech9.net \
--cc=Akram.Abou-Emara@nokia.com \
--cc=linux-kernel@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