linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org, Subodh Nijsure <sunijsur@cisco.com>
Subject: Re: Run UBIFS on top of IDE mode NAND disk?
Date: Wed, 15 Apr 2009 17:29:23 +0100	[thread overview]
Message-ID: <20090415162923.GC4325@shareable.org> (raw)
In-Reply-To: <1239776240.3390.151.camel@localhost.localdomain>

Artem Bityutskiy wrote:
> Hi,
> 
> On Tue, 2009-04-14 at 23:10 -0700, Subodh Nijsure wrote: 
> > I have board with 4GB NAND memory chip, it is configured to
> > operate in IDE mode. And currently I am creating ext3 file-system
> > on it.  This chip also have on-board controller that does
> > wear-levelling, ECC so the quesitons are:
> >  
> > Can I (Should I) run UBIFS on of it and gain more of wear-levelling or its
> > not worth it? 
> 
> Vs "Can I": if this is raw NAND, you just need an MTD driver for it.
> Then you can use UBI/UBIFS on top of that.
> 
> Vs "Should I": you really should not ask questions like this. It is a
> question of your design. Look at your NAND and how many erase cycles
> each eraseblock survives. Then roughly calculate how many years or
> months it should survive with ext3, which has fixed-position journal
> and inode table and bitmap. Then decide whether you need WL or not.
> Everything depends on your requirements.
> 
> Also, if this is raw NAND, then HW does not hide bad blocks for you,
> right? How will you manage bad eraseblocks then, ext3 cannot do this.
> It just panics in case of any I/O error.

But the on board controller does wear-levelling, he said.

I think the question is whether the on board controller's
wear-levelling is good or not.  If it's low quality, UBI will do it
better.  If the controller is good quality, there's no need for UBI on
top of it.

I guess that two layers of good quality wear levelling just adds more
wear, because they both copy data around.

If it can be used as raw NAND, and the chip really is a NAND with
standard NAND properties, _and_ if it's possible to disable the
controller's wear levelling and get direct NAND access, then at least
you know that UBI provides a good quality wear levelling
implementation, and you have access to some statistics too.

-- Jamie

  reply	other threads:[~2009-04-15 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15  6:10 Run UBIFS on top of IDE mode NAND disk? Subodh Nijsure
2009-04-15  6:17 ` Artem Bityutskiy
2009-04-15 16:29   ` Jamie Lokier [this message]
2009-04-16  5:30     ` Artem Bityutskiy
2009-04-23 18:48 ` Miles Nordin

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=20090415162923.GC4325@shareable.org \
    --to=jamie@shareable.org \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sunijsur@cisco.com \
    /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).