From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 890856B022F for ; Tue, 15 Jun 2010 09:37:47 -0400 (EDT) Date: Tue, 15 Jun 2010 09:37:27 -0400 From: Christoph Hellwig Subject: Re: [PATCH 12/12] vmscan: Do not writeback pages in direct reclaim Message-ID: <20100615133727.GA27980@infradead.org> References: <1276514273-27693-1-git-send-email-mel@csn.ul.ie> <1276514273-27693-13-git-send-email-mel@csn.ul.ie> <4C16A567.4080000@redhat.com> <20100615114510.GE26788@csn.ul.ie> <4C17815A.8080402@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C17815A.8080402@redhat.com> Sender: owner-linux-mm@kvack.org To: Rik van Riel Cc: Mel Gorman , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Dave Chinner , Chris Mason , Nick Piggin , Johannes Weiner , Christoph Hellwig , KAMEZAWA Hiroyuki , Andrew Morton List-ID: On Tue, Jun 15, 2010 at 09:34:18AM -0400, Rik van Riel wrote: > If direct reclaim can overflow the stack, so can direct > memcg reclaim. That means this patch does not solve the > stack overflow, while admitting that we do need the > ability to get specific pages flushed to disk from the > pageout code. Can you explain what the hell memcg reclaim is and why it needs to reclaim from random contexts? It seems everything that has a cg in it's name that I stumbled over lately seems to be some ugly wart.. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org