From: Con Kolivas <kernel@kolivas.org>
To: Juho Saarikko <juhos@mbnet.fi>
Cc: ck list <ck@vds.kolivas.org>, linux list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.16-ck9
Date: Wed, 3 May 2006 23:30:12 +1000 [thread overview]
Message-ID: <200605032330.13131.kernel@kolivas.org> (raw)
In-Reply-To: <1146646484.4260.6.camel@a88-112-69-25.elisa-laajakaista.fi>
On Wednesday 03 May 2006 18:54, Juho Saarikko wrote:
> On Wed, 2006-05-03 at 01:01, Con Kolivas wrote:
> > The spid will show you any threads with different pids to the main task.
> > Then check the actual scheduling policy they run at. Perhaps FahCore
> > actually manually sets them to SCHED_NORMAL.
>
> And so it does. Annoying. Time to hack kernel to add a new scheduling
> policy, SCHED_STAYIDLE, which is like SCHED_IDLE but cannot be unset
> except by root.
>
> Can't make it the default, since a program running at SCHED_IDLE in a
> machine with 100% CPU usage by some other program will never process
> SIGKILL, and thus can only be killed by setting its scheduling policy to
> normal...
I toyed with the idea of making it one way to convert tasks to SCHED_IDLEPRIO
but not back to SCHED_NORMAL much like we do for niceing tasks up but not
back down again. However I personally found this very inconvenient as I often
might run something idleprio for a while and then change it back. It seems a
fair thing for a normal user to do.
> Darn obnoxious program, SetiAtHome...
Obviously when they wrote the linux client and added the ability to set the
priority from within the program to nice 19 they also explicitly set the
scheduling policy at the same time. This might make sense on some other OS...
but not linux.
--
-ck
next prev parent reply other threads:[~2006-05-03 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 13:38 2.6.16-ck9 Con Kolivas
2006-05-02 20:57 ` [ck] 2.6.16-ck9 Juho Saarikko
2006-05-02 22:01 ` Con Kolivas
2006-05-03 8:54 ` Juho Saarikko
2006-05-03 13:30 ` Con Kolivas [this message]
2006-05-03 16:27 ` Jan Engelhardt
2006-05-03 16:25 ` Jan Engelhardt
2006-05-03 20:21 ` Juho Saarikko
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=200605032330.13131.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=juhos@mbnet.fi \
--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