public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Zhao Forrest <forrest.zhao@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: A question about UBIFS
Date: Mon, 16 Jun 2008 12:21:30 +0300	[thread overview]
Message-ID: <4856309A.2070409@nokia.com> (raw)
In-Reply-To: <ac8af0be0806160016p85be687n50110e2b9ce637df@mail.gmail.com>

Zhao Forrest wrote:
>> Zhao Forrest wrote:
>>> Hi Artem,
>>> I have a basic question about NAND flash page update in UBIFS/UBI,
>>> take the following as an example:
>>> 1 a NAND flash with page size of 4KB, erase block size of 256KB, so
>>> there're 64 pages within an erase block
>>> 2 page 0 - page 10 has invalid data content, page 11 - page 63 has
>>> valid data content from FS's point of view
>>> 3 UBIFS attempts to update(or rewrite) page 11
>>> My question is how page 11 is updated by UBIFS/UBI?
>>> I only read the design docs of UBI and guess that for this particular
>>> case a new physical eraseblock is got by UBI, then new content of page
>>> 11 is written to page 11 of new physical eraseblock, page 12 - page 63
>>> in original physical eraseblock are copied to new physical eraseblock,
>>> lastly the mapping between logical eraseblock and physical eraseblock
>>> is updated. Am I right?
>> Right. All updates are out-of-place.
>>
> So when only page 11 is rewritten, are pages 12-63 rewritten at the same time?
> Or page 11 is updated by wandering tree mechanism, and pages 12-63 are
> untouched?

The latter (12-63 are untouched).

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2008-06-16  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  4:16 A question about UBIFS Zhao Forrest
2008-06-11  6:34 ` Adrian Hunter
2008-06-11  7:56   ` Zhao Forrest
2008-06-11  8:19     ` Nancy
2008-06-16  6:42 ` Artem Bityutskiy
2008-06-16  7:16   ` Zhao Forrest
2008-06-16  9:21     ` Artem Bityutskiy [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=4856309A.2070409@nokia.com \
    --to=artem.bityutskiy@nokia.com \
    --cc=forrest.zhao@gmail.com \
    --cc=linux-mtd@lists.infradead.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