public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Subject: Re: Disadvantage of using yaffs checkpointing ?
Date: Tue, 2 Mar 2010 15:31:02 +1300	[thread overview]
Message-ID: <201003021531.02989.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <cf70f0211003011801r33027ec8s78c9326f9d058c46@mail.gmail.com>

On Tuesday 02 March 2010 15:01:08 Shivdas Gujare wrote:
> Hi All,
>
> I am very new to mtd & yaffs and working on boottime optimization and
> found that yaffs checkpointing helps to mount
> yaffs2 very quickly. I tried it, and was able to save almost 4sec for
> 128MB partitioned nand.
>
> Since everything looks very good If I use yaffs checkpointing feature
> but have a doubt, are there any disadvantage of using check-pointing
> by default in final product?
>
> I understood that, check-pointing only disables boot time nand block
> scanning & marking it bad if found,
> and takes "system snapshot" while using "umount /dev/mtdblockN" which
> it use in next boot.
> So, If I decided to use "checkpointing" with "umount" while powering
> off the device in final product,
> are there going to be any problems I will face avoiding block scanning?
>
> Thanks lot for any help.
>

You would do better asking yaffs questions on the yaffs list.

http://www.aleph1.co.uk/mailman/listinfo/yaffs

-- Charles

  reply	other threads:[~2010-03-02  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02  2:01 Disadvantage of using yaffs checkpointing ? Shivdas Gujare
2010-03-02  2:31 ` Charles Manning [this message]
2010-03-02  6:38   ` Shivdas Gujare

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=201003021531.02989.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --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