From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with SMTP id p2SNvKLC192831 for ; Mon, 28 Mar 2011 18:57:21 -0500 Received: from mga03.intel.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id B778A1DFA70B for ; Mon, 28 Mar 2011 17:00:28 -0700 (PDT) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by cuda.sgi.com with ESMTP id 2oQ9sLTPwPhudkgS for ; Mon, 28 Mar 2011 17:00:28 -0700 (PDT) From: Andi Kleen Subject: Re: Very aggressive memory reclaim References: <20110328215344.GC3008@dastard> Date: Mon, 28 Mar 2011 16:58:50 -0700 In-Reply-To: <20110328215344.GC3008@dastard> (Dave Chinner's message of "Tue, 29 Mar 2011 08:53:44 +1100") Message-ID: MIME-Version: 1.0 List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: linux-mm@kvack.org, John Lepikhin , linux-kernel@vger.kernel.org, xfs@oss.sgi.com Dave Chinner writes: > > First it would be useful to determine why the VM is reclaiming so > much memory. If it is somewhat predictable when the excessive > reclaim is going to happen, it might be worth capturing an event Often it's to get pages of a higher order. Just tracing alloc_pages should tell you that. There are a few other cases (like memory failure handling), but they're more obscure. -Andi -- ak@linux.intel.com -- Speaking for myself only _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs