Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761538AbZFOPZu (ORCPT ); Mon, 15 Jun 2009 11:25:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751426AbZFOPZn (ORCPT ); Mon, 15 Jun 2009 11:25:43 -0400 Received: from gir.skynet.ie ([193.1.99.77]:48325 "EHLO gir.skynet.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751331AbZFOPZm (ORCPT ); Mon, 15 Jun 2009 11:25:42 -0400 Date: Mon, 15 Jun 2009 16:25:43 +0100 From: Mel Gorman To: Christoph Lameter Cc: KOSAKI Motohiro , Andrew Morton , riel@redhat.com, fengguang.wu@intel.com, linuxram@us.ibm.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Johannes Weiner Subject: Re: [PATCH 0/3] Fix malloc() stall in zone_reclaim() and bring behaviour more in line with expectations V3 Message-ID: <20090615152543.GF23198@csn.ul.ie> References: <20090611163006.e985639f.akpm@linux-foundation.org> <20090612110424.GD14498@csn.ul.ie> <20090615163018.B43A.A69D9226@jp.fujitsu.com> <20090615105651.GD23198@csn.ul.ie> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1649 Lines: 38 On Mon, Jun 15, 2009 at 11:01:41AM -0400, Christoph Lameter wrote: > On Mon, 15 Jun 2009, Mel Gorman wrote: > > > > May I ask your worry? > > > > > > > Simply that I believe the intention of PF_SWAPWRITE here was to allow > > zone_reclaim() to aggressively reclaim memory if the reclaim_mode allowed > > it as it was a statement that off-node accesses are really not desired. > > Right. > > > Ok. I am not fully convinced but I'll not block it either if believe it's > > necessary. My current understanding is that this patch only makes a difference > > if the server is IO congested in which case the system is struggling anyway > > and an off-node access is going to be relatively small penalty overall. > > Conceivably, having PF_SWAPWRITE set makes things worse in that situation > > and the patch makes some sense. > > We could drop support for RECLAIM_SWAP if that simplifies things. > I don't think that is necessary. While I expect it's very rarely used, I imagine a situation where it would be desirable on a system that had large amounts of tmpfs pages but where it wasn't critical they remain in-memory. Removing PF_SWAPWRITE would make it less aggressive and if you were happy with that, then that would be good enough for me. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab -- 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/