xfs
[Top] [All Lists]

Re: TAKE 949916 - direct read vs delalloc

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: TAKE 949916 - direct read vs delalloc
From: Nathan Scott <nathans@xxxxxxx>
Date: Sat, 18 Mar 2006 14:27:06 +1100
Cc: linux-xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20060317175719.GA6619@xxxxxxxxxxxxx>; from hch@xxxxxxxxxxxxx on Fri, Mar 17, 2006 at 05:57:19PM +0000
References: <20060317053019.C44EF49F168A@xxxxxxxxxxxxxxxxxxxxxxx> <20060317175719.GA6619@xxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Fri, Mar 17, 2006 at 05:57:19PM +0000, Christoph Hellwig wrote:
> On Fri, Mar 17, 2006 at 04:30:19PM +1100, Nathan Scott wrote:
> > Flush and invalidate dirty pages at the start of a direct read also,
> > else we can hit a delalloc-extents-via-direct-io BUG.
> 
> If this is needed it should be done in the filemap.c code.

Hmm, maybe, maybe not.

filemap.c code doesn't know much about delayed allocation, so
this won't bite other filesystems.  We do the same thing on
write and always have, so having it inside XFS is OK by me.

cheers.

-- 
Nathan


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