On Fri, Jul 23, 1999 at 05:21:03PM +0100, Stephen C. Tweedie wrote:
> > I have made a fairly substantial SCHED_IDLE patch, but due to
> > the (never resolved) deadlock issues I haven't submitted it.
>=20
> Yes, it really is a loaded gun. A large SCHED_IDLE process can consume
> arbitrary system resources, and if there is any single cpu-bound process
> preventing it from being scheduled, you won't even be able to kill -9
> the SCHED_IDLE task (the kill signal isn't delivered until the task is
> next scheduled).
The kill -9 can be handled by promoting this process to another scheduling
class, when there are signals pending. Especially with SIGKILL.
Note that some of the OOM patches discussed for includsion into the kernel
are promoted to SCHED_RR when being killed.
Regards,
--=20
Kurt Garloff <garloff@suse.de> SuSE GmbH, N=FCrnberg, FRG
Linux kernel development; SCSI drivers: tmscsim(DC390), DC395
--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3in
iQCVAwUBN5i92BaQN/7O/JIVAQHZbAP/Q4TnUCIC7tcivPxQ1Fym0J9hizsmWzBo
8O0Q8jPGWhNBa5DBYMqMd7Mk9ydb5vAgc5+FiEvTK9axSsliWlolpSJ9cCuJkyvF
peCJBZ++ZJbFjckOGPIQL+FM6xXdVU2shpk5sXbHJJAzzw6yHL3zfgRRobqPRnLz
2hlKvSyOxG0=
=G6sL
-----END PGP SIGNATURE-----
--J2SCkAp4GZ/dPZZf--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/