public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: UBI Used In Commercial Products ??
Date: Wed, 31 Oct 2007 23:01:07 +0000 (UTC)	[thread overview]
Message-ID: <loom.20071031T224633-341@post.gmane.org> (raw)
In-Reply-To: B1EDF20A6EAAD74EA65E46F774F1784502C6D843@orsmsx413.amr.corp.intel.com

Hi,
> JFFS2 has been modified to sit on top of UBI.

Yes, I know. Is that better then JFFS2 on top of mtdblock device?
  
> One thought here is that I would think that mounting is a fairly rare
> occurance.  
> You're much more likely to coming back from suspend.  Notice the
> difference in time it takes from my HP iPAQ to power-on normally vs a
> cold boot.  It is very different. 

Still one must plan for the worst case and the worst case for me
was about 2 hours of mount time after I used ftp to transfer large file.
I suspect ftp was writing really small jffs2 nodes.
Disclaimer: that was about 2 years ago and jffs2 might have improved,
processor (ARM9) was not a speed demon either.
If you do that on your iPAQ (create large file with lots of small nodes)
and then cold boot it - would you be willing to wait for an hour for it to 
become usable again?

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?

Regards,

Sergei Sharonov

  reply	other threads:[~2007-10-31 23:01 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 [this message]
2007-11-01  0:57       ` Jamie Lokier
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=loom.20071031T224633-341@post.gmane.org \
    --to=sergei.sharonov@halliburton.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