X-Spam-Checker-Version: SpamAssassin 3.3.0-rupdated (updated) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00, FH_DATE_PAST_20XX autolearn=no version=3.3.0-rupdated Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o2FGO10W064038 for ; Mon, 15 Mar 2010 11:24:02 -0500 X-ASG-Debug-ID: 1268669282-3759021e0000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from bombadil.infradead.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 8C9B91D337A2 for ; Mon, 15 Mar 2010 09:08:02 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) by cuda.sgi.com with ESMTP id DBGgqkMCVrLiKLlY for ; Mon, 15 Mar 2010 09:08:02 -0700 (PDT) X-ASG-Whitelist: Client Received: from hch by bombadil.infradead.org with local (Exim 4.69 #1 (Red Hat Linux)) id 1NrCpl-000533-OT; Mon, 15 Mar 2010 16:08:01 +0000 Date: Mon, 15 Mar 2010 12:08:01 -0400 From: Christoph Hellwig To: Dave Chinner Cc: xfs@oss.sgi.com X-ASG-Orig-Subj: Re: [RFC] Delayed logging Subject: Re: [RFC] Delayed logging Message-ID: <20100315160801.GB10406@infradead.org> References: <20100315043000.GK4732@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100315043000.GK4732@dastard> User-Agent: Mutt/1.5.19 (2009-01-05) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html X-Barracuda-Connect: bombadil.infradead.org[18.85.46.34] X-Barracuda-Start-Time: 1268669282 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean Some comments on the patches: - "xfs: cluster fsync transaction" seems like something that can stand on it's own and go into the tree now. Despite the comments it currently only clusters in fsync and not write_inode which might lead to higher benefits, btw. - the busy extent tracking might be worth to be reordered before the delayed logging series. In itself it might also want some reordering as there's a lot churn in the patches there. Making "XFS: Simplify transaction busy extent tracking" first in that subseries might help quite a bit to reduce that churn - The actual CIL implementation seems to be split into too small patches IMHO. E.g. "xfs: extend the log item to support delayed logging" and "xfs: Introduce the Committed Item List" are two sides of the same coin and splitting it might not make too much sense.