Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754689AbYAPNHG (ORCPT ); Wed, 16 Jan 2008 08:07:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752827AbYAPNG4 (ORCPT ); Wed, 16 Jan 2008 08:06:56 -0500 Received: from smtp.ustc.edu.cn ([202.38.64.16]:43170 "HELO ustc.edu.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S1751301AbYAPNGz (ORCPT ); Wed, 16 Jan 2008 08:06:55 -0500 Message-ID: <400488821.15609@ustc.edu.cn> X-EYOUMAIL-SMTPAUTH: wfg@mail.ustc.edu.cn Date: Wed, 16 Jan 2008 21:06:55 +0800 From: Fengguang Wu To: Andrew Morton Cc: David Chinner , Michael Rubin , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch] Converting writeback linked lists to a tree based data structure References: <20080115080921.70E3810653@localhost> <1200386774.15103.20.camel@twins> <532480950801150953g5a25f041ge1ad4eeb1b9bc04b@mail.gmail.com> <400452490.28636@ustc.edu.cn> <20080115194415.64ba95f2.akpm@linux-foundation.org> <20080116075538.GW155407@sgi.com> <20080116001343.06e4ddab.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080116001343.06e4ddab.akpm@linux-foundation.org> X-GPG-Fingerprint: 53D2 DDCE AB5C 8DC6 188B 1CB1 F766 DA34 8D8B 1C6D User-Agent: Mutt/1.5.12-2006-07-14 Message-Id: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2596 Lines: 52 On Wed, Jan 16, 2008 at 12:13:43AM -0800, Andrew Morton wrote: > On Wed, 16 Jan 2008 18:55:38 +1100 David Chinner wrote: > > > On Tue, Jan 15, 2008 at 07:44:15PM -0800, Andrew Morton wrote: > > > On Wed, 16 Jan 2008 11:01:08 +0800 Fengguang Wu wrote: > > > > > > > On Tue, Jan 15, 2008 at 09:53:42AM -0800, Michael Rubin wrote: > > > > > On Jan 15, 2008 12:46 AM, Peter Zijlstra wrote: > > > > > > Just a quick question, how does this interact/depend-uppon etc.. with > > > > > > Fengguangs patches I still have in my mailbox? (Those from Dec 28th) > > > > > > > > > > They don't. They apply to a 2.6.24rc7 tree. This is a candidte for 2.6.25. > > > > > > > > > > This work was done before Fengguang's patches. I am trying to test > > > > > Fengguang's for comparison but am having problems with getting mm1 to > > > > > boot on my systems. > > > > > > > > Yeah, they are independent ones. The initial motivation is to fix the > > > > bug "sluggish writeback on small+large files". Michael introduced > > > > a new rbtree, and me introduced a new list(s_more_io_wait). > > > > > > > > Basically I think rbtree is an overkill to do time based ordering. > > > > Sorry, Michael. But s_dirty would be enough for that. Plus, s_more_io > > > > provides fair queuing between small/large files, and s_more_io_wait > > > > provides waiting mechanism for blocked inodes. > > > > > > > > The time ordered rbtree may delay io for a blocked inode simply by > > > > modifying its dirtied_when and reinsert it. But it would no longer be > > > > that easy if it is to be ordered by location. > > > > > > What does the term "ordered by location" mean? Attemting to sort inodes by > > > physical disk address? By using their i_ino as a key? > > > > > > That sounds optimistic. > > > > In XFS, inode number is an encoding of it's location on disk, so > > ordering inode writeback by inode number *does* make sense. > > This code is mainly concerned with writing pagecache data, not inodes. Now I tend to agree with you. It is not easy to sort writeback pages by disk location. There are three main obstacles: - there can be multiple filesystems on the same disk - ext3/reiserfs/... make use of blockdev inode, which spans the whole partition; - xfs may store inode metadata/data separately; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/