| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 4/7] xfs: use ranged writeback and invalidation for direct IO |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 28 Aug 2014 17:40:47 -0700 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1409226551-16570-5-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1409226551-16570-1-git-send-email-david@xxxxxxxxxxxxx> <1409226551-16570-5-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
On Thu, Aug 28, 2014 at 09:49:08PM +1000, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > Now we are not doing silly things with dirtying buffers beyond EOF > and using invalidation correctly, we can finally reduce the ranges of > writeback and invalidation used by direct IO to match that of the IO > being issued. > > Bring the writeback and invalidation ranges back to match the > generic direct IO code - this will greatly reduce the perturbation > of cached data when direct IO and buffered IO are mixed, but still > provide the same buffered vs direct IO coherency behaviour we > currently have. > > Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> Looks correct, although I wonder if it's really worth the risk exposing us to the crazy details of the page cache invalidation range notations.. Reviewed-by: Christoph Hellwig <hch@xxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/7] xfs: don't zero partial page cache pages during O_DIRECT writes, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 5/7] xfs: don't log inode unless extent shift makes extent modifications, Christoph Hellwig |
| Previous by Thread: | [PATCH 4/7] xfs: use ranged writeback and invalidation for direct IO, Dave Chinner |
| Next by Thread: | [PATCH 5/7] xfs: don't log inode unless extent shift makes extent modifications, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |