Re: [PATCH] xfs: wait for direct I/O to complete in fsync and write

xfs

Re: [PATCH] xfs: wait for direct I/O to complete in fsync and write_inod

To:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject:	Re: [PATCH] xfs: wait for direct I/O to complete in fsync and write_inode
From:	Dave Chinner <david@xxxxxxxxxxxxx>
Date:	Wed, 14 Apr 2010 09:40:15 +1000
Cc:	xfs@xxxxxxxxxxx
In-reply-to:	<20100306132018.GA31360@xxxxxxxxxxxxx>
References:	<20100306132018.GA31360@xxxxxxxxxxxxx>
User-agent:	Mutt/1.5.20 (2009-06-14)

On Sat, Mar 06, 2010 at 08:20:18AM -0500, Christoph Hellwig wrote:
> 
> We need to wait for all pending direct I/O requests before taking care of
> metadata in fsync and write_inode.

Sorry, I missed this one when scaning the list for outstanding
patches yesterday. The concept looks fine, though:

> Note that the write_inode hunk will causes conflicts when merging with
> mainline, I'm not sure how to best deal with that.

I don't think it applies to the current xfs-dev tree any more,
either.  Can you rebase it?

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [PATCH] xfs: wait for direct I/O to complete in fsync and write_inode, Dave Chinner <=

Previous by Date:	Re: Kernel crash in xfs_iflush_cluster (was Somebody take a look please!...), Janos Haar
Next by Date:	Re: Kernel crash in xfs_iflush_cluster (was Somebody take a look please!...), Dave Chinner
Previous by Thread:	FELICITATION!!!!!!FELICITATION!!!!!!FELICITATION!!!!!!, ERIC BIGNAND
Next by Thread:	Re: ext34_free_inode's mess, Eric Sandeen
Indexes:	[Date] [Thread] [Top] [All Lists]