From: Martin Jambor <jamborm@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: File and device pages and buffers
Date: Mon, 18 Apr 2005 02:09:51 +0200 [thread overview]
Message-ID: <8e70aacf05041717093deeb825@mail.gmail.com> (raw)
There is one thing about cache pages and buffers that puzzles me and
that I have not found in any documenatation and that is not quite
obvious from the source.
What is the relationship between:
a) pages and their buffers associated with the device (tybically
bh->bdev->bd_inode and its mapping) and
b) pages and their buffers associated with files on that device.
I am almost certain they are not the same but at the same time the
relationship seems to be quite important, otherwise we wouldn't have
such dark functions as unmap_underlying_metadata (why on earth is it
called this way? - Does metadata mean, in true kernel naming confusion
spirit, device pages/blocks?).
Can anyone tell me what the relationship exactly is and what one has
to be aware of when manipulating either of these?
Thank you very much in advance,
Martin Jambor
next reply other threads:[~2005-04-18 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 0:09 Martin Jambor [this message]
2005-04-21 20:16 ` File and device pages and buffers Martin Jambor
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=8e70aacf05041717093deeb825@mail.gmail.com \
--to=jamborm@gmail.com \
--cc=linux-fsdevel@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).