From owner-freebsd-hackers Wed Sep 22 9:39:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C316714E71 for ; Wed, 22 Sep 1999 09:39:23 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA06930; Thu, 23 Sep 1999 01:39:18 +0900 (JST) Message-ID: <37E905DE.7ACBDD7A@newsguy.com> Date: Thu, 23 Sep 1999 01:37:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Ivan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Out of swap handling and X lockups in 3.2R References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ivan wrote: > > Of course I didn't mean that malloc() calls the pageout daemon ... I > simply meant that if no more memory space can be regained (in particular > by killing a process) then at some point memory allocations will be > refused -- or else, when does malloc() ever returns NULL ?! When per-process limits have been reached. > Or even simply send SIGTERM for instance before SIGKILL ... at least, > that would be understood by many processes (such as the X server). When the time comes to do a SIGKILL, nothing else should be used. There is +NO+ memory free. A SIGTERM under these circunstances can led to a deadlock (or else require disgustingly complex code). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Thus, over the years my wife and I have physically diverged. While I have zoomed toward a crusty middle-age, she has instead clung doggedly to the sweet bloom of youth. Naturally I think this unfair. Yet, if it was the other way around, I confess I wouldn't be happy either." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message