From owner-freebsd-current Wed Apr 14 18:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id E7FB214BEF for ; Wed, 14 Apr 1999 18:30:34 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA04575; Wed, 14 Apr 1999 21:28:12 -0400 (EDT) Message-ID: <371540AA.BA9AED2A@acm.org> Date: Wed, 14 Apr 1999 21:28:10 -0400 From: Jim Bloom X-Mailer: Mozilla 4.51 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <199904142340.TAA96857@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A signal handler is not guaranteed to work. It must be written such that it does not require a new page of memory. Some possible problems here are the stack growing, writing on a new page in the data segment, etc. I'm not familiar enough with the VM system, but if you couldn't create a new swap page for a process, what would guarantee that the signal handler could get the pages it needs. Jim Bloom bloom@acm.org Mikhail Teterin wrote: > > If we are up to discussing the possible implementations, I'd suggest > that the system uses something other then SIGKILL to notify the > program it's time to pay for the over-commit speed and convenience. > I think, SIGBUS is appropriate, but I'm not sure. > > Anything a program can _catch_ and react upon, if its author chooses > to. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message