All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koji Sato <koji-sG5X7nlA6pw@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: Physical block addresses?
Date: Thu, 31 Jan 2008 15:25:05 +0900	[thread overview]
Message-ID: <47A169C1.3070001@osrg.net> (raw)
In-Reply-To: <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi, Sivan.

> I am trying to figure out whether NILFS uses physical block addresses
> as pointers in inodes and indirect blocks, but I could not figure this
> out from the papers.
> 
> Does it? If so, I assume that when cleaning a segment and copying live
> data to a new segment, each relocated block causes the propagation of
> dirty blocks (because some other blocks point to the old segment, so
> they need to be modified, and so on. Is that correct?

NILFS version 2 uses virtual block numbers to point to blocks. The
virtual block numbers are translated into physical disk addresses when
they are referenced. This mechanism prevents cascading updates of the
file system when cleaning segments because only the
virtual-to-physical mappings are updated.

Thanks.

-- 
Koji Sato
Open Source Software Computing Project
NTT Cyber Space Laboratories
Nippon Telegraph and Telephone Corporation

      parent reply	other threads:[~2008-01-31  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 17:48 Physical block addresses? Sivan Toledo
     [not found] ` <196f72b10801280948uc9e1275o6c4bf1bf56cd26c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-31  6:25   ` Koji Sato [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=47A169C1.3070001@osrg.net \
    --to=koji-sg5x7nla6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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 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.