Date: Wed, 9 Jan 2008 11:11:05 +0100 From: "Heiko Wundram (Beenic)" <wundram@beenic.net> To: freebsd-hackers@freebsd.org Subject: Re: Graceful failure instead of panicking in kmem_malloc Message-ID: <200801091111.06050.wundram@beenic.net> In-Reply-To: <66462bcb31fb347796200bd5260d7cdc@gmail.com> References: <67beabb0801081555v4ca3b729x294322fa724afa09@mail.gmail.com> <67beabb0801081925t67f995b8hc4cc779f88c2ba@mail.gmail.com> <66462bcb31fb347796200bd5260d7cdc@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mittwoch, 9. Januar 2008 10:29:43 schrieb Joshua Isom: > Why not try to take out some user processes? Going with a combination > of process priority and memory usage, it should at least be more > tolerable than a panic. Ahemm. No. That's not tolerable in real world conditions. Have you ever had the OOM-killer strike on Linux (which is known for this, and has been criticized at other times for its braindead default behavior of overcommiting virtual memory space almost two-fold)? That's a major, major PITA. I'd rather have the system reboot and come back up to a clean and initialized state than to "randomly" kill user processes and leave it crippled but (somewhat) running (with sshd possibly killed off, which is especially bad on remote boxes), as basically to recover cleanly from the OOM-killer striking, you're going to have to reboot the box anyway. -- Heiko Wundram Product & Application Development
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200801091111.06050.wundram>