All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Andreas Dilger <adilger@sun.com>, linux-fsdevel@vger.kernel.org
Subject: Re: PG_updatodate vs BH_updatodate
Date: Sun, 23 Nov 2008 21:14:47 +0100	[thread overview]
Message-ID: <m28wra5he0.fsf@gmail.com> (raw)
In-Reply-To: <20081123122124.GH5707@parisc-linux.org> (Matthew Wilcox's message of "Sun\, 23 Nov 2008 05\:21\:24 -0700")

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).

>
> For file data, no this doesn't happen.  But for metadata, it happens
>quite easily.

Could you give me an example of these metadata ?

Thanks

Francis

  reply	other threads:[~2008-11-23 20:14 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 [this message]
2008-11-24 15:56         ` Jörn Engel
2008-11-24 16:42           ` Francis Moreau

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=m28wra5he0.fsf@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=adilger@sun.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.