From: Sukadev Bhattiprolu <sukadev@us.ibm.com>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Pagewriteback clarification
Date: Wed, 28 Sep 2005 16:57:37 -0700 [thread overview]
Message-ID: <20050928235736.GA26480@us.ibm.com> (raw)
In-Reply-To: <17210.24512.240624.67693@gargle.gargle.HOWL>
Thanks for your response. Yes I was referring to filesystems/Locking.
|
| No, callers of ->writepage() should assure that
|
| - page is locked, and
|
| - writeback bit is clear on that page.
|
| Which means that no IO is going on against this page. When
| Documentation/filesystems/Locking talks about "currently-in-progress
| I/O" it means any IO going to or fro the device, and "blocking against
| in-progress I/O" means blocking due to device queue congestion.
So is that referring to I/Os to/from the device from say pages other than
the one in ->writepage().
I was guessing that the test_set_buffer_locked() in __block_write_full_page()
is testing if I/O is in progress for a buffer belonging to this page. Is
that not the case ?
next prev parent reply other threads:[~2005-09-28 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 1:57 Pagewriteback clarification Sukadev Bhattiprolu
2005-09-28 9:17 ` Nikita Danilov
2005-09-28 23:57 ` Sukadev Bhattiprolu [this message]
2005-09-29 0:24 ` Badari Pulavarty
2005-09-29 8:47 ` Nikita Danilov
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=20050928235736.GA26480@us.ibm.com \
--to=sukadev@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nikita@clusterfs.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