linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Matthew Wilcox" <matthew@wil.cx>,
	"Andreas Dilger" <adilger@sun.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: PG_updatodate vs BH_updatodate
Date: Mon, 24 Nov 2008 17:42:48 +0100	[thread overview]
Message-ID: <38b2ab8a0811240842y5032ab6fhad5201333c47af5d@mail.gmail.com> (raw)
In-Reply-To: <20081124155633.GB3051@logfs.org>

On Mon, Nov 24, 2008 at 4:56 PM, Jörn Engel <joern@logfs.org> wrote:
> On Sun, 23 November 2008 21:14:47 +0100, Francis Moreau wrote:
>> Matthew Wilcox <matthew@wil.cx> writes:
>> > On Sun, Nov 23, 2008 at 01:14:52PM +0100, Francis Moreau wrote:
>> >
>> >> Are there any cases where a page can be partially uptodate ?
>> >
>> > Consider a filesystem with 1k blocks and a system with a page size of 4k.
>> > You have a buffer_head for each of the four blocks that are being kept
>> > in the page, and you want to track their dirty state independently.
>>
>> Sorry but I'm confused since you're taking about the dirty state
>> (tracked by BH_Dirty bit) and I was taking about the uptodate state
>> (tracked by BH_Uptodate bit).
>
> Think page cache, except that the granularity is not pages but 1k
> blocks.  If your filesystem wants to read an indirect block, 1k is read
> into the cache, the other 3k (or 63k) of the page remain as they were.
>

So if I understand you correctly, we can update a page cache partially
only when the
filesystems needs to read its metadata. But not when reading a page of data.

That's pretty what Matthew answered I think but I'm confused about the
dirty bit of the
buffer header he mentioned.

Thanks
-- 
Francis
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-11-24 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 22:03 PG_updatodate vs BH_updatodate Francis Moreau
2008-11-23  4:19 ` Andreas Dilger
2008-11-23 12:14   ` Francis Moreau
2008-11-23 12:21     ` Matthew Wilcox
2008-11-23 20:14       ` Francis Moreau
2008-11-24 15:56         ` Jörn Engel
2008-11-24 16:42           ` Francis Moreau [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=38b2ab8a0811240842y5032ab6fhad5201333c47af5d@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=adilger@sun.com \
    --cc=joern@logfs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).