From owner-freebsd-hackers Wed Sep 22 15:49: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8B21515372 for ; Wed, 22 Sep 1999 15:49:04 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA28698; Wed, 22 Sep 1999 16:05:31 -0700 (PDT) Date: Wed, 22 Sep 1999 16:05:31 -0700 (PDT) From: Alfred Perlstein To: Chuck Robey Cc: Wes Peters , "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, Chuck Robey wrote: > On Wed, 22 Sep 1999, Wes Peters wrote: > > > Chuck Robey wrote: > > > > > > What kind of resources are there that both cause loss of swap AND are > > > freed up by sleeping a process? > > > > Any of them being consumed by short-lived processes that will run to > > completion and exit while everyone else is sleeping. This assumes such > > processes exist, of course. > > OK, you wait until some process exits. Ob course, if none do, then your > entire machine, all processes that ask for memory, wedge, instead of just > one. You can't even start 'kill -9'. It wouldn't be all that difficult to track how many processes were affected or for how long they were affected by this and change to a kill strategy at that point. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message