| To: | Dave Chinner <david@xxxxxxxxxxxxx>, darrick.wong@xxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH 2/6] xfs: ioends require logically contiguous file offsets |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 7 Mar 2016 08:26:44 -0800 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1457300990-18300-3-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1457300990-18300-1-git-send-email-david@xxxxxxxxxxxxx> <1457300990-18300-3-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Mon, Mar 07, 2016 at 08:49:46AM +1100, Dave Chinner wrote: > From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx> > > We need to create a new ioend if the current writepage call isn't > logically contiguous with the range contained in the previous ioend. > Hopefully writepage gets called in order of increasing file offset. This looks reasonable, but how did we manage to get away without this for so long? I think as-is we do not actually require it - for setting i_size we just care about the highest offset, and for unwritten extent conversion we just need the lowest and highest offset, and we were making use of that fact in direct I/O extensively before I rewrote that code not to use ioends. So this looks fine to me, but the description could use some better wording. Signed-off-by: Christoph Hellwig <hch@xxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/6] xfs: reinitialise per-AG structures if geometry changes during recovery, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 4/6] xfs: use named array initializers for log item dumping, Christoph Hellwig |
| Previous by Thread: | [PATCH 2/6] xfs: ioends require logically contiguous file offsets, Dave Chinner |
| Next by Thread: | Re: [PATCH 2/6] xfs: ioends require logically contiguous file offsets, Darrick J. Wong |
| Indexes: | [Date] [Thread] [Top] [All Lists] |