Re: [ck] 2.6.16-ck9
- From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
- Date: Wed, 3 May 2006 18:27:10 +0200 (MEST)
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...
Try making SCHED_STAYIDLE non-idle enough so that non-catchable signals get
processed in an appropriate time.
You have the source, you can change the behavior as a temporary workaround.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.
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- 2.6.16-ck9
- From: Con Kolivas
- Re: [ck] 2.6.16-ck9
- From: Con Kolivas
- Re: [ck] 2.6.16-ck9
- From: Juho Saarikko
- Re: [ck] 2.6.16-ck9
- From: Con Kolivas
- 2.6.16-ck9
- Prev by Date: Re: [ck] 2.6.16-ck9
- Next by Date: Re: [RFC] Advanced XIP File System
- Previous by thread: Re: [ck] 2.6.16-ck9
- Next by thread: Re: [ck] 2.6.16-ck9
- Index(es):
Relevant Pages
|