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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
