From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC PATCH 0/6] Do not call ->writepage[s] from direct reclaim and use a_ops->writepages() where possible Date: Tue, 15 Jun 2010 10:11:22 -0400 Message-ID: <20100615141122.GA27893@infradead.org> References: <1275987745-21708-1-git-send-email-mel@csn.ul.ie> <20100615140011.GD28052@random.random> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mel Gorman , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Dave Chinner , Chris Mason , Nick Piggin , Rik van Riel To: Andrea Arcangeli Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:57336 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757829Ab0FOOL3 (ORCPT ); Tue, 15 Jun 2010 10:11:29 -0400 Content-Disposition: inline In-Reply-To: <20100615140011.GD28052@random.random> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Jun 15, 2010 at 04:00:11PM +0200, Andrea Arcangeli wrote: > collecting clean cache doesn't still satisfy the allocation), during > allocations in direct reclaim and increase the THREAD_SIZE than doing > this purely for stack reasons as the VM will lose reliability if we This basically means doubling the stack size, as you can splice together two extremtly stack hungry codepathes in the worst case. Do you really want order 2 stack allocations?