From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: question regarding the Linux block device cache
Date: Fri, 9 Mar 2007 18:58:55 -0500 [thread overview]
Message-ID: <4ae3c140703091558p5e6625a9t3d2798fd67e7ac1a@mail.gmail.com> (raw)
In-Reply-To: <4ae3c140703091424i25a0a3fcm6ba9d7bf348d04b6@mail.gmail.com>
I read the code and found that a block buffer is not necessarily freed
even if the corresponding inode is released. Looks like block buffer
can stay around as long as the system still has free memory. Is my
understanding correct?
-x
On 3/9/07, Xin Zhao <uszhaoxin@gmail.com> wrote:
> Hi,
>
> I am working on a file system that allow multiple files to share data
> blocks. That is, a data block can be shared by two or more files. Now
> my question is: suppose file A and B share the same data block D. Now
> a process open file A and read block D, then this process closes file
> A. If another process open file B and read block D right after the
> first process closes A, is the data of block D read from some cache or
> has to be loaded from disk again? I think this has to do with the
> Linux block device buffer cache. But I am not quite familiar with this
> part.
>
> Can someone help me or direct me to the right place to find the answer?
>
> Thanks in advance!
>
> -x
>
prev parent reply other threads:[~2007-03-09 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 22:24 question regarding the Linux block device cache Xin Zhao
2007-03-09 23:58 ` Xin Zhao [this message]
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=4ae3c140703091558p5e6625a9t3d2798fd67e7ac1a@mail.gmail.com \
--to=uszhaoxin@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).