From: jesse <jessezx@yahoo.com>
To: Paulo Marques <pmarques@grupopie.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 11:03:39 -0800 (PST) [thread overview]
Message-ID: <20041221190339.24215.qmail@web52605.mail.yahoo.com> (raw)
In-Reply-To: <41C86F2A.7020409@grupopie.com>
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.
regards!
jesse
--- Paulo Marques <pmarques@grupopie.com> wrote:
> jesse wrote:
> > Con:
> >
> > thank you for your prompt reply in the holiday
> > season.
> >
> > My point is: Even kernel 2.4 is not
> > preemptive, the latence should be very
> > minimal.(<300ms)
> > why user space application with low nice priority
> > can't be effectively interrupted and holds the CPU
> > resource since all user space application is
> > preemptive?
>
> If your process has got work to do and has a higher
> priority than other
> processes, it gets to run. If you don't want this
> behavior, don't give
> it such a high priority.
>
> If you want low latency to do some quick high
> priority task, just do it
> quickly and relinquish the processor, instead of
> hogging it.
>
> What are you trying to accomplish, anyway?
>
> --
> 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:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 2:43 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 [this message]
2004-12-21 19:23 ` Paulo Marques
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=20041221190339.24215.qmail@web52605.mail.yahoo.com \
--to=jessezx@yahoo.com \
--cc=kernel@kolivas.org \
--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
all inboxes | Powered by JetHome®