From: Akshat Aranya <aaranya@gmail.com>
To: linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@netapp.com>
Subject: Difference between release_page() and launder_page()
Date: Fri, 30 Apr 2010 08:05:21 -0400 [thread overview]
Message-ID: <w2re48344781004300505z22894e4fqff4c8fdf048d747d@mail.gmail.com> (raw)
Hi Trond and others,
I've been trying to figure out meaning of release_page() vs.
launder_page() by looking at the source code and the history behind
it. Here's what I could piece together so far:
1. Before launder_page() was added, release_page() was intended to do
the file system's writeback.
2. This would cause a deadlock for NFS because in some cases, the
inode lock would be taken after the page lock to process write
requests to the server.
3. The page writeback was moved to nfs_launder_page() instead of
nfs_release_page() to avoid the deadlock.
4. This, however, misses pages that are clean but unstable (?). To
allow writeback of these pages, writeback was added back to
nfs_release_page()
Do I have the picture correct? Could you explain how in NFS some
pages end up being dirty while others end up being clean-but-unstable?
Thanks,
Akshat
reply other threads:[~2010-04-30 17:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=w2re48344781004300505z22894e4fqff4c8fdf048d747d@mail.gmail.com \
--to=aaranya@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@netapp.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).