Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 8 Nov 2000 13:51:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 8 Nov 2000 13:50:59 -0500 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:32008 "EHLO artax.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id ; Wed, 8 Nov 2000 13:50:47 -0500 Date: Wed, 8 Nov 2000 19:50:41 +0100 (CET) From: Mikulas Patocka To: Alan Cox cc: "J . A . Magallon" , Michael Rothwell , linux-kernel@vger.kernel.org Subject: Re: continuing VM madness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > Sadly it is not a bug but a VM misdesign (and people are just making > > different workarounds that more or less work). I believe that this > > solution will break again, as it happened in 2.2.15 and 2.2.16. > > 2.2.15->16 was the major transition in getting stuff right. 2.2.18 should be > pretty reasonable. With Andrea's additional patches its quite nice. If we > add page aging then in theory it'll be as good as 2.2 but in practice who > knows What about the possibility that kernel shoots processes when the machine is receiving too much packets and runs out of atomic memory? It didn't seem to go away in 2.2.16. 2.0 behaved correctly in this case. Mikulas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/