public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Sergei Sharonov <sergei.sharonov@halliburton.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI Used In Commercial Products ??
Date: Thu, 1 Nov 2007 00:57:10 +0000	[thread overview]
Message-ID: <20071101005710.GB21550@mail.shareable.org> (raw)
In-Reply-To: <loom.20071031T224633-341@post.gmane.org>

Sergei Sharonov wrote:
> 2 hours of mount time after I used ftp to transfer large file.

Wow!

> I really hope UBI+UBIFS will overcome this problem. Still there is a
> concern here since UBI scales linearly. Can somebody plz post UBI
> scan time for large flash array?

The only way to get sub-linear scaling is to designate a sub-linear
subset of eraseblocks which are read at scanning/mount time.

Doing that at the same time as wearing all eraseblocks equally is
quite tricky, and probably requires a phase tree and multi-headed
logging structure, like LogFS (I'm not sure if LogFS actually does
both, though).

Such a structure is not particularly simple, and will be present in
the best flash filesystems eventually.  So I wonder if UBI is really a
good place to have a second copy of those algorithms.

I like the idea of UBI, to abstract block allocation and wear tracking
from the filesystem, but it seems the sub-linear scan time requirement
is a tricky one to do without implementing a non-trivial
filesystem-like algorithm in UBI itself.

I'll be delighted to read that the problem's been solved, when it has
been solved, though :-)

-- Jamie

  reply	other threads:[~2007-11-01  0:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 18:58 UBI Used In Commercial Products ?? Johnson, Charles F
2007-10-31 22:09 ` Sergei Sharonov
2007-10-31 22:20   ` Johnson, Charles F
2007-10-31 23:01     ` Sergei Sharonov
2007-11-01  0:57       ` Jamie Lokier [this message]
2007-11-01  1:56       ` Josh Boyer
2007-11-02  0:36       ` David Woodhouse
2007-11-01  0:47     ` Jamie Lokier

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=20071101005710.GB21550@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sergei.sharonov@halliburton.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