From owner-cvs-src Fri Mar 14 12:25:37 2003 Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F2FD37B401; Fri, 14 Mar 2003 12:25:34 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C71043F93; Fri, 14 Mar 2003 12:25:24 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h2EKOh905789; Fri, 14 Mar 2003 17:24:43 -0300 Message-ID: <3E723A8A.8070100@tcoip.com.br> Date: Fri, 14 Mar 2003 17:24:42 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030214 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Mike Silbersack Cc: Garance A Drosihn , Poul-Henning Kamp , Juli Mallett , Eivind Eklund , David Schultz , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/vm ... SIGDANGER References: <8023.1047662161@critter.freebsd.dk> <20030314140414.V4480@odysseus.silby.com> In-Reply-To: <20030314140414.V4480@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-cvs-src@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Silbersack wrote: > > I'm really not sure how much of a help this SIGDANGER or whatever will be. > As I see it, there are two cases of OOM: > > 1. Heavy load, lots of busy processes, all legitimate. > - Nobody has complained about this case having problems. > > 2. Light load, then some program goes crazy and forks / chews up ram. X > gets killed. > - I think this is what people are complaining about. No, there are a couple of other cases: 3) Serious Processing(tm) application blithely allocates memory until memory allocation fails. At that point it stops allocating memory. Another application then uses some previously untouched allocated memory, and first application gets killed losing hours of work. 4) Very Important Server allocates a lot of memory, and gets killed when stupid user starts another xterm. Whatever you may or may not think the correct way of handling these two cases is, people *have* complained of our present way of handling them. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Lowery's Law: If it jams -- force it. If it breaks, it needed replacing anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message