From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Subject: Documentation on address_space_operations?
Date: Sat, 13 Oct 2001 17:19:13 -0700 [thread overview]
Message-ID: <200110140019.RAA12016@adam.yggdrasil.com> (raw)
I would appreciate any specific pointers to documentation
on the exact semantics of the functions declared in struct
address_space_operations. The exact division of labor between
writepage, sync_page, prepare_write, commit_write, and direct_IO
is not obvious to me, to say the least.
This is especially relevant to me because the ramdisk code
was changed to use struct address_space_operations around 2.4.11-pre6,
causing my change that allowed the ramdisk contents to be usable even
if filesystems that had different block sizes were compiled into the
kernel (for example, if you compile in cramfs and romfs with the stock
kernels, you initial ramdisk cannot be in romfs format because the
block size change between cramfs and romfs will cause all data to be lost).
A couple of years ago, I had posted my fix for this to linux-kernel based
on old IO method, but the change was never integrated into the official
kernels. I would like to try to develop and updated fix for the new
ramdisk code. (I would also like to port the change that somebody made
around 2.3.43 to have the ramdisk driver drop pages that consists of all
zeroes, although that is less important.)
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
reply other threads:[~2001-10-14 0:19 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=200110140019.RAA12016@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--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
all inboxes | Powered by JetHome®