Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964843AbVLNQhV (ORCPT ); Wed, 14 Dec 2005 11:37:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964844AbVLNQhV (ORCPT ); Wed, 14 Dec 2005 11:37:21 -0500 Received: from e2.ny.us.ibm.com ([32.97.182.142]:30148 "EHLO e2.ny.us.ibm.com") by vger.kernel.org with ESMTP id S964843AbVLNQhU (ORCPT ); Wed, 14 Dec 2005 11:37:20 -0500 Message-ID: <43A04A38.6020403@us.ibm.com> Date: Wed, 14 Dec 2005 08:37:12 -0800 From: Matthew Dobson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alan Cox CC: Andrea Arcangeli , Pavel Machek , linux-kernel@vger.kernel.org, Sridhar Samudrala , Andrew Morton , Linux Memory Management Subject: Re: [RFC][PATCH 0/6] Critical Page Pool References: <439FCECA.3060909@us.ibm.com> <20051214100841.GA18381@elf.ucw.cz> <20051214120152.GB5270@opteron.random> <1134565436.25663.24.camel@localhost.localdomain> In-Reply-To: <1134565436.25663.24.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1497 Lines: 36 Alan Cox wrote: > On Mer, 2005-12-14 at 13:01 +0100, Andrea Arcangeli wrote: > >>On Wed, Dec 14, 2005 at 11:08:41AM +0100, Pavel Machek wrote: >> >>>because reserved memory pool would have to be "sum of all network >>>interface bandwidths * ammount of time expected to survive without >>>network" which is way too much. >> >>Yes, a global pool isn't really useful. A per-subsystem pool would be >>more reasonable... > > > > The whole extra critical level seems dubious in itself. In 2.0/2.2 days > there were a set of patches that just dropped incoming memory on sockets > when the memory was tight unless they were marked as critical (ie NFS > swap). It worked rather well. The rest of the changes beyond that seem > excessive. Actually, Sridhar's code (mentioned earlier in this thread) *does* drop incoming packets that are not 'critical', but unfortunately you need to completely copy the packet into kernel memory before you can do any processing on it to determine whether or not it's 'critical', and thus accept or reject it. If network traffic is coming in at a good clip and the system is already under memory pressure, it's going to be difficult to receive all these packets, which was the inspiration for this patchset. Thanks! -Matt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/