From: Con Kolivas <kernel@kolivas.org>
To: jesse <jessezx@yahoo.com>
Cc: Paulo Marques <pmarques@grupopie.com>, linux-kernel@vger.kernel.org
Subject: Re: Gurus, a silly question for preemptive behavior
Date: Wed, 22 Dec 2004 08:35:48 +1100 [thread overview]
Message-ID: <41C89734.8020302@kolivas.org> (raw)
In-Reply-To: <20041221190339.24215.qmail@web52605.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
jesse wrote:
> Paulo:
>
> I already said in the messsage that my user space
> application has a low nice priority, i set it to 10.
> since my application has low priority compared to
> other user space applications, it is supposed to be
> interrupted. but it is not.
If your task is better priority the scheduler will make it preempt the
worse priority task. It sounds to me like you are complaining that the
worse priority task is still getting cpu? If so, you misunderstand
priority - it orders tasks according to priority giving lower latency
and preemptive behaviour to the better task, and gives _more_ cpu but
not all the cpu. The cpu must still be shared, but with more cpu
distributed to the better priority task. If you want your better
priority task to get _all_ the cpu you have to use real time scheduling.
Cheers,
Con
P.S. Please dont top post when replying, it's hard to follow an email
thread to see what you're replying to if you do that. These threads can
get very long and confusing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-12-21 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 2:43 Gurus, a silly question for preemptive behavior jesse
2004-12-21 5:59 ` Con Kolivas
2004-12-21 18:32 ` jesse
2004-12-21 18:44 ` Paulo Marques
2004-12-21 19:03 ` jesse
2004-12-21 19:23 ` Paulo Marques
2004-12-21 21:35 ` Con Kolivas [this message]
2004-12-21 23:07 ` jesse
2004-12-22 2:16 ` Con Kolivas
2004-12-22 12:39 ` K.R. Foley
2004-12-26 19:30 ` Stephen Satchell
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=41C89734.8020302@kolivas.org \
--to=kernel@kolivas.org \
--cc=jessezx@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.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