From: Namhyung Kim <namhyung@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: A question on block_prepare_write()
Date: Sat, 23 Oct 2010 22:44:42 +0900 [thread overview]
Message-ID: <1287841482.1681.36.camel@leonhard> (raw)
Hello,
I see block_prepare_write() has local variable wait[2] to keep track of
buffer_heads which are not up-to-date. But I'm wondering how it could be
guaranteed there will be no more than 2 such buffer_heads? Is there any
restriction on the usage of the function? Using MAX_BUF_PER_PAGE instead
of the magic number 2 is just useless? I couldn't find any comments or
documentation on this.
Any of your comments would be greatly appreciated. TIA. :-)
--
Regards,
Namhyung Kim
next reply other threads:[~2010-10-23 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 13:44 Namhyung Kim [this message]
2010-10-23 17:40 ` A question on block_prepare_write() Andrew Morton
2010-10-23 18:00 ` Namhyung Kim
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=1287841482.1681.36.camel@leonhard \
--to=namhyung@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).