public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: David Chinner <dgc@sgi.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com, akpm@osdl.org
Subject: Re: [PATCH 1/2]: Fix BUG in cancel_dirty_pages on XFS
Date: Thu, 25 Jan 2007 11:12:41 +1100	[thread overview]
Message-ID: <45B7F5F9.2070308@yahoo.com.au> (raw)
In-Reply-To: <20070124224654.GN33919298@melbourne.sgi.com>

David Chinner wrote:
> On Thu, Jan 25, 2007 at 12:43:23AM +1100, Nick Piggin wrote:

>>And why not just leave it in the pagecache and be done with it?
> 
> 
> because what is in cache is then not coherent with what is on disk,
> and a direct read is supposed to read the data that is present
> in the file at the time it is issued. 

So after a writeout it will be coherent of course, so the point in
question is what happens when someone comes in and dirties it at the
worst possible moment? That relates to the paragraph below...

>>All you need is to do a writeout before a direct IO read, which is
>>what generic dio code does.
> 
> 
> No, that's not good enough - after writeout but before the
> direct I/O read is issued a process can fault the page and dirty
> it. If you do a direct read, followed by a buffered read you should
> get the same data. The only way to guarantee this is to chuck out
> any cached pages across the range of the direct I/O so they are
> fetched again from disk on the next buffered I/O. i.e. coherent
> at the time the direct I/O is issued.

... so surely if you do a direct read followed by a buffered read,
you should *not* get the same data if there has been some activity
to modify that part of the file in the meantime (whether that be a
buffered or direct write).

>>but in that case you'll either have to live with some racyness
>>(which is what the generic code does), or have a higher level
>>synchronisation to prevent buffered + direct IO writes I suppose?
> 
> 
> The XFS inode iolock - direct I/O writes take it shared, buffered
> writes takes it exclusive - so you can't do both at once. Buffered
> reads take is shared, which is another reason why we need to purge
> the cache on direct I/O writes - they can operate concurrently
> (and coherently) with buffered reads.

Ah, I'm glad to see somebody cares about doing the right thing ;)
Maybe I'll use XFS for my filesystems in future.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2007-01-25  0:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 22:37 [PATCH 1/2]: Fix BUG in cancel_dirty_pages on XFS David Chinner
2007-01-24 12:13 ` Peter Zijlstra
2007-01-24 13:43   ` Nick Piggin
2007-01-24 14:40     ` Peter Zijlstra
2007-01-25  0:05       ` Nick Piggin
2007-01-24 22:46     ` David Chinner
2007-01-25  0:12       ` Nick Piggin [this message]
2007-01-25  0:35         ` David Chinner
2007-01-25  0:47           ` Nick Piggin
2007-01-25  1:52             ` David Chinner
2007-01-25  2:01               ` Nick Piggin
2007-01-25  3:42                 ` David Chinner
2007-01-25  4:25                   ` Nick Piggin
2007-01-25  7:40                     ` David Chinner
2007-01-25 10:26                       ` Nick Piggin
2007-01-24 22:24   ` David Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45B7F5F9.2070308@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox