From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 23 Apr 2007 15:23:45 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id l3NMNffB031057 for ; Mon, 23 Apr 2007 15:23:43 -0700 Date: Mon, 23 Apr 2007 23:23:40 +0100 From: Christoph Hellwig Subject: Re: review [1 of 3]: lazy superblock counters - core kernel Message-ID: <20070423222340.GA23870@infradead.org> References: <20070419231459.GX48531920@melbourne.sgi.com> <20070423220010.GA18325@infradead.org> <20070423221622.GL32602149@melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070423221622.GL32602149@melbourne.sgi.com> Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: David Chinner Cc: Christoph Hellwig , xfs-dev , xfs-oss On Tue, Apr 24, 2007 at 08:16:23AM +1000, David Chinner wrote: > > > + INT_SET(sb->sb_fdblocks, ARCH_CONVERT, mp->m_sb.sb_fdblocks); > > > + XFS_SB_UNLOCK(mp, s); > > > > This is really quite nasty. Should we at least force a cache flush here? > > Well, that is what it's doing - xfs_log_sbcount() flushes the counters and > logs the changes to the superblock. If that fails (very rare) we've already > got the current values in mp->m_sb and so all we need to do is push them > into the disk superblock and write it. Sorry, should have been more detailed. I meant the disk cache, as in blkdev_issue_flush, to make sure the data hits the disk, even if it doesn't go through a transaction which would normally do that. (in the barriers case)