From: Andrea Arcangeli <andrea@suse.de>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
pbadari@us.ibm.com, linux-fsdevel@vger.kernel.org,
sct@redhat.com
Subject: Re: kjournald() with DIO
Date: Fri, 16 Sep 2005 02:18:44 +0200 [thread overview]
Message-ID: <20050916001844.GQ4122@opteron.random> (raw)
In-Reply-To: <1126826924.3885.6.camel@dyn9047017116.beaverton.ibm.com>
On Thu, Sep 15, 2005 at 04:28:44PM -0700, Mingming Cao wrote:
> Isn't direct-io and buffered IO being serialized by i_sem? If so, the
page faults aren't serialized by i_sem, so if a page fault happens the
vm may unmap the pte under memory pressure marking the page dirty. But
we have the guarantee that such dirty bit in the pte was set after we
were inside write() so we can drop it (or we can as well leave it), it's
undefined.
but the point is that the buffered-io fallback happens after the
invalidate, so it shouldn't matter if we drop dirty buffers or dirty
pages in the invalidate, they should be re-generated.
So overall I believe it's semantically equivalent if we drop the dirty
bits or not. Clearly not dropping them is a bit less intrusive, but
current code seems ready to drop them by calling ->invalidatepage
(destructive) instead of creating a blocking version of ->releasepage
(non destructive).
next prev parent reply other threads:[~2005-09-16 0:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 23:23 kjournald() with DIO Badari Pulavarty
2005-09-12 23:37 ` Andrew Morton
2005-09-13 0:06 ` Badari Pulavarty
2005-09-13 0:29 ` Andrew Morton
2005-09-13 16:52 ` Badari Pulavarty
2005-09-13 23:07 ` Andrew Morton
2005-09-14 17:23 ` Mingming Cao
2005-09-14 18:18 ` Andrew Morton
2005-09-14 21:40 ` Mingming Cao
2005-09-14 22:02 ` Andrew Morton
2005-09-15 11:11 ` Suparna Bhattacharya
2005-09-15 18:52 ` Andrew Morton
2005-09-15 15:03 ` Badari Pulavarty
2005-09-15 19:22 ` Andrea Arcangeli
2005-09-15 20:00 ` Andrew Morton
2005-09-15 20:20 ` Andrea Arcangeli
2005-09-15 20:35 ` Andrew Morton
2005-09-15 20:49 ` Badari Pulavarty
2005-09-15 21:06 ` Andrea Arcangeli
2005-09-15 21:20 ` Andrew Morton
2005-09-15 22:22 ` Badari Pulavarty
2005-09-15 21:03 ` Andrea Arcangeli
2005-09-15 21:26 ` Andrew Morton
2005-09-15 22:04 ` Andrea Arcangeli
2005-09-15 23:28 ` Mingming Cao
2005-09-16 0:18 ` Andrea Arcangeli [this message]
2005-09-13 17:53 ` Mingming Cao
2005-09-16 13:42 ` Stephen C. Tweedie
2005-09-21 18:22 ` Mingming Cao
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=20050916001844.GQ4122@opteron.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.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;
as well as URLs for NNTP newsgroup(s).