From owner-freebsd-current Mon May 7 11:25:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2576A37B424 for ; Mon, 7 May 2001 11:25:32 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f47IOwC27448; Mon, 7 May 2001 11:24:58 -0700 (PDT) Date: Mon, 7 May 2001 11:24:58 -0700 From: Alfred Perlstein To: Rik van Riel Cc: Matt Dillon , Sheldon Hearn , Kris Kennaway , Dennis Glatting , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm Message-ID: <20010507112458.U18676@fw.wintelcom.net> References: <200105071709.f47H9Pr61499@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Mon, May 07, 2001 at 02:58:53PM -0300 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Rik van Riel [010507 10:59] wrote: > > Indeed, this is an interesting area. In the process of > researching how to best implement this for Linux I have > found various reasons why both FreeBSD's and NetBSD's > load control systems cannot work in various realistic > scenarios. > > The next step is designing a load control system that > does work (not too hard) and having a reliable way of > detecting when exactly the system is thrashing (next > to impossible?). > > I'll make a detailed writeup of exactly why FreeBSD's > load control system cannot work and will post it to > arch@freebsd.org and linux-mm@kvack.org soon... ;) You might as well not bother unless you're actually going to provide code that fixes the issue. For some reason banning you from the irc channel hasn't convinced you that complaining without providing patches isn't the way we do things around here. Anyhow, since you do seem to code a bit for Linux you might want to take a shot at fixing the Linux code. Last I checked, given enough time (30 minutes or so) FreeBSD recovers from such situations while Linux wets the bed and requires a power cycle. thank you and good bye, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message