From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail6.bemta7.messagelabs.com (mail6.bemta7.messagelabs.com [216.82.255.55]) by kanga.kvack.org (Postfix) with ESMTP id 1D79A6B004A for ; Thu, 14 Jul 2011 11:10:01 -0400 (EDT) Date: Thu, 14 Jul 2011 11:09:59 -0400 From: Christoph Hellwig Subject: Re: [PATCH 5/5] mm: writeback: Prioritise dirty inodes encountered by direct reclaim for background flushing Message-ID: <20110714150959.GA30936@infradead.org> References: <1310567487-15367-1-git-send-email-mgorman@suse.de> <1310567487-15367-6-git-send-email-mgorman@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1310567487-15367-6-git-send-email-mgorman@suse.de> Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Linux-MM , LKML , XFS , Dave Chinner , Christoph Hellwig , Johannes Weiner , Wu Fengguang , Jan Kara , Rik van Riel , Minchan Kim On Wed, Jul 13, 2011 at 03:31:27PM +0100, Mel Gorman wrote: > It is preferable that no dirty pages are dispatched from the page > reclaim path. If reclaim is encountering dirty pages, it implies that > either reclaim is getting ahead of writeback or use-once logic has > prioritise pages for reclaiming that are young relative to when the > inode was dirtied. what does this buy us? If at all we should prioritize by a zone, e.g. tell write_cache_pages only to bother with writing things out if the dirty page is in a given zone. We'd probably still cluster around it to make sure we get good I/O patterns, but would only start I/O if it has a page we actually care about. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org