xfs
[Top] [All Lists]

Re: review: don't hold ilock when calling vn_iowait

To: David Chinner <dgc@xxxxxxx>
Subject: Re: review: don't hold ilock when calling vn_iowait
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 24 Apr 2007 10:10:00 +0100
Cc: Timothy Shimmin <tes@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
In-reply-to: <20070424030826.GG48531920@xxxxxxxxxxxxxxxxx>
References: <20070422230303.GX32602149@xxxxxxxxxxxxxxxxx> <20070423214338.GA17561@xxxxxxxxxxxxx> <20070423231706.GO32602149@xxxxxxxxxxxxxxxxx> <1A5D0CA3BA5C7CF8B7241F39@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20070424030826.GG48531920@xxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.2i
On Tue, Apr 24, 2007 at 01:08:26PM +1000, David Chinner wrote:
> > It would be nice if this could be clearer somehow.
> 
> Yes, we should be looking to rip all this cruft out because most of
> it is redundant - the generic inode writeback does most of this
> for us anyway.

In theory it does the same thing.  The problem is that it's really
hard to verify.

Btw, before starting with this bit there's another item on my TODO
list to simplify xfs_sync_inodes, and that's getting rid
of the vp == NULL case totally.  Per definition all vp == NULL
inodes are on mp->m_del_inodes.  So instead of letting xfs_sync_inodes
deals with them we should always call into xfs_finish_reclaim_all
after cleaning the latter up a little and veryfing we get
the same behaviour.


<Prev in Thread] Current Thread [Next in Thread>