Re: Ongoing 2.4 VM suckage

[Pavel Zaitsev]

--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Jeffrey W. Baker([e-mail])@Thu, Aug 02, 2001 at 02:52:11PM -0700:
> Gosh, here's an idea: if there is no memory left and someone malloc()s
> some more, have malloc() fail?  Kill the process that required the memory?
> I can't believe the attitude I am hearing.  Userland processes should be
> able to go around doing whaever the fuck they want and the box should stay
> alive.  Currently, if a userland process runs amok, the kernel goes into
> self-fucking mode for the rest of the week.

Userland process shall be suspended after it reaches certain rate of
swaps per second. It may resume after short while. Userland process,
if written properly will see that malloc is failing and inform user.
If its being bad, then it will be suspended.
p.

--=20
Take out your recursive cannons and shoot!
110461387
http://gpg.md5.ca
http://perlpimp.com

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7adDqEhbFhd1U3E0RAgJ8AKDQP6TLLKgWoaUvzHg6RpTp0Q8aQwCghSl8
Wzts4Kx/aHaMsvwBau5z0Dg=
=FO8y
-----END PGP SIGNATURE-----

--M9NhX3UHpAaciwkO--