From owner-freebsd-hackers Wed Sep 22 9:32:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id AFB84154F7 for ; Wed, 22 Sep 1999 09:32:25 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA03220; Wed, 22 Sep 1999 12:29:58 -0400 (EDT) (envelope-from chuckr@mat.net) Date: Wed, 22 Sep 1999 12:29:58 -0400 (EDT) From: Chuck Robey To: Alfred Perlstein Cc: "Daniel C. Sobral" , Ivan , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Out of swap handling and X lockups in 3.2R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Sep 1999, Alfred Perlstein wrote: > Terry Lambert brought up an interesting thought from AIX (I think), > instead of killing a process, it just sleeps the requesting process > until the situation alleviates itself. Of course this can wind up > wedging an entire system, it would probably be advisable to then > revert to killing when more than a threshold of processes go into > a vmwait sleep. Seeing as the reason for killing is because you're out of system resources, and you need to free up some in order to go on, and sleeping the process isn't going to free up the resources needed, I don't see how this'll help things. What kind of resources are there that both cause loss of swap AND are freed up by sleeping a process? ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message