From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Nice 19 process still gets some CPU
Date: Mon, 28 Jun 2004 11:14:22 -0400 [thread overview]
Message-ID: <40E035CE.1020401@techsource.com> (raw)
Given how much I've read here about schedulers, I should probably be
able to answer this question myself, but I just thought I might talk to
the experts.
I'm running SETI@Home, and it has a nice value of 19. Everything else,
for the most part, is at zero.
I'm running kernel gentoo-dev-sources-2.6.7-r6 (I believe).
When I'm not running SETI@Home, compiler threads (emerge of a package,
kernel compile, etc.) get 100% CPU. When I AM running SETI@Home,
SETI@Home still manages to get between 5% and 10% CPU.
I would expect that nice 0 processes should get SO MUCH more than nice
19 processes that the nice 19 process would practically starve (and in
the case of a nice 19 process, I think starvation by nice 0 processes is
just fine), but it looks like it's not starving.
Why is that?
Thanks.
next reply other threads:[~2004-06-28 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 15:14 Timothy Miller [this message]
2004-06-28 15:04 ` Nice 19 process still gets some CPU Con Kolivas
2004-06-28 15:41 ` Timothy Miller
2004-06-28 15:24 ` Con Kolivas
2004-06-28 15:42 ` Richard B. Johnson
2004-06-28 15:47 ` Con Kolivas
2004-06-28 15:48 ` Kalin KOZHUHAROV
2004-06-28 15:51 ` Con Kolivas
2004-06-28 16:17 ` Chris Friesen
2004-06-28 16:23 ` Michael Buesch
2004-06-28 16:36 ` Chris Friesen
2004-06-28 21:15 ` Con Kolivas
2004-06-29 16:56 ` Kurt Garloff
2004-06-28 23:38 ` Peter Williams
2004-06-29 6:26 ` Benoît Dejean
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=40E035CE.1020401@techsource.com \
--to=miller@techsource.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