Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751274AbWHQX4u (ORCPT ); Thu, 17 Aug 2006 19:56:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751272AbWHQX4u (ORCPT ); Thu, 17 Aug 2006 19:56:50 -0400 Received: from smtp-out.google.com ([216.239.45.12]:36980 "EHLO smtp-out.google.com") by vger.kernel.org with ESMTP id S1751233AbWHQX4t (ORCPT ); Thu, 17 Aug 2006 19:56:49 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:user-agent: x-accept-language:mime-version:to:cc:subject:references:in-reply-to: content-type:content-transfer-encoding; b=dR4uSgByGpJPWVejNHmeSXE2nGteYQ71nZLVeMVTnJ5ufJ1aZAS4vjan3qHDrPqBk +NAgpkLmNibjO0JRo6D/w== Message-ID: <44E5015D.80606@google.com> Date: Thu, 17 Aug 2006 16:53:01 -0700 From: Daniel Phillips User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Morton CC: Peter Zijlstra , David Miller , riel@redhat.com, tgraf@suug.ch, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Mike Christie Subject: Re: [RFC][PATCH 2/9] deadlock prevention core References: <20060808211731.GR14627@postel.suug.ch> <44DBED4C.6040604@redhat.com> <44DFA225.1020508@google.com> <20060813.165540.56347790.davem@davemloft.net> <44DFD262.5060106@google.com> <20060813185309.928472f9.akpm@osdl.org> <1155530453.5696.98.camel@twins> <20060813215853.0ed0e973.akpm@osdl.org> <44E3E964.8010602@google.com> <20060816225726.3622cab1.akpm@osdl.org> In-Reply-To: <20060816225726.3622cab1.akpm@osdl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 950 Lines: 26 Andrew Morton wrote: > Daniel Phillips wrote: >>What happened to the case where we just fill memory full of dirty file >>pages backed by a remote disk? > > Processes which are dirtying those pages throttle at > /proc/sys/vm/dirty_ratio% of memory dirty. So it is not possible to "fill" > memory with dirty pages. If the amount of physical memory which is dirty > exceeds 40%: bug. Hi Andrew, So we make 400 MB of a 1 GB system unavailable for write caching just to get around the network receive starvation issue? What happens if some in kernel user grabs 68% of kernel memory to do some very important thing, does this starvation avoidance scheme still work? Regards, Daniel - 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/