From: Paulo Marques <pmarques@grupopie.com>
To: jesse <jessezx@yahoo.com>
Cc: Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: Gurus, a silly question for preemptive behavior
Date: Tue, 21 Dec 2004 19:23:17 +0000 [thread overview]
Message-ID: <41C87825.8020901@grupopie.com> (raw)
In-Reply-To: <20041221190339.24215.qmail@web52605.mail.yahoo.com>
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.
The confusion comes from "low nice priority". The lower the nice value
the higher the priority.
Anyway, you still haven't give enough data to analyze. What does your
application do? Is it I/O intensive? If it is, it could be that the
kernel itself is hogging the CPU doing I/O on behalf of a low prio
process (priority, specially in 2.4, only affects CPU distribution and
not I/O). How do you know it's not being preempted? What is your
.config? What patches do you have applied? And finally, why don't you
upgrade to a 2.6 kernel :) ?
--
Paulo Marques - www.grupopie.com
"A journey of a thousand miles begins with a single step."
Lao-tzu, The Way of Lao-tzu
next prev parent reply other threads:[~2004-12-21 19:24 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 [this message]
2004-12-21 21:35 ` Con Kolivas
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=41C87825.8020901@grupopie.com \
--to=pmarques@grupopie.com \
--cc=jessezx@yahoo.com \
--cc=kernel@kolivas.org \
--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