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 780486B02A4 for ; Thu, 29 Jul 2010 12:10:21 -0400 (EDT) Date: Thu, 29 Jul 2010 18:09:47 +0200 From: Jan Kara Subject: Re: [PATCH 0/5] [RFC] transfer ASYNC vmscan writeback IO to the flusher threads Message-ID: <20100729160947.GE12690@quack.suse.cz> References: <20100729115142.102255590@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100729115142.102255590@intel.com> Sender: owner-linux-mm@kvack.org To: Wu Fengguang Cc: Andrew Morton , LKML , "linux-fsdevel@vger.kernel.org" , "linux-mm@kvack.org" , Dave Chinner , Chris Mason , Nick Piggin , Rik van Riel , Johannes Weiner , Christoph Hellwig , KAMEZAWA Hiroyuki , KOSAKI Motohiro , Andrea Arcangeli , Mel Gorman , Minchan Kim List-ID: On Thu 29-07-10 19:51:42, Wu Fengguang wrote: > Andrew, > > It's possible to transfer ASYNC vmscan writeback IOs to the flusher threads. > This simple patchset shows the basic idea. Since it's a big behavior change, > there are inevitably lots of details to sort out. I don't know where it will > go after tests and discussions, so the patches are intentionally kept simple. > > sync livelock avoidance (need more to be complete, but this is minimal required for the last two patches) > [PATCH 1/5] writeback: introduce wbc.for_sync to cover the two sync stages > [PATCH 2/5] writeback: stop periodic/background work on seeing sync works > [PATCH 3/5] writeback: prevent sync livelock with the sync_after timestamp Well, essentially any WB_SYNC_NONE writeback is still livelockable if you just grow a file constantly. So your changes are a step in the right direction but won't fix the issue completely. But what we could do to fix the issue completely would be to just set wbc->nr_to_write to LONG_MAX before writing inode for sync use my livelock avoidance using page-tagging for this case (it wouldn't have the possible performance issue because we are going to write all the inode anyway). I can write the patch but frankly there are so many patches floating around that I'm not sure what I should base it on... Honza -- Jan Kara SUSE Labs, CR -- 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