linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: Canella Matteo <Matteo.Canella@mta.it>
Cc: "Bityutskiy Artem \(Nokia-M/Helsinki\)"
	<Artem.Bityutskiy@nokia.com>,
	"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: UBI FS mounting time
Date: Wed, 22 Jul 2009 12:19:04 +0300	[thread overview]
Message-ID: <4A66D988.4050503@nokia.com> (raw)
In-Reply-To: <BD9F3F3F5A6CCF4BA032B9FED4DD312E5D09531F0B@mta-digimail.MTA.INT>

Canella Matteo wrote:
> Just to understand if we're doing things in the right way...
> we need more than 6 secs to mount 1 GB Nand Flash. 
> Does this sound a normal timing?

Yes

> This is the dmesg of the flash mounting:
> 
> [    6.694626] UBI: attaching mtd10 to ubi2
> [    6.698594] UBI: physical eraseblock size:   131072 bytes (128 KiB)
> [    6.705712] UBI: logical eraseblock size:    126976 bytes
> [    6.711154] UBI: smallest flash I/O unit:    2048
> [    6.715894] UBI: sub-page size:              512
> [    6.720533] UBI: VID header offset:          2048 (aligned 2048)
> [    6.726564] UBI: data offset:                4096
> [   12.802282] UBI: attached mtd10 to ubi2
> [   12.806179] UBI: MTD device name:            "nand"
> [   12.814531] UBI: MTD device size:            1024 MiB
> [   12.820304] UBI: number of good PEBs:        8185
> [   12.825069] UBI: number of bad PEBs:         7
> [   12.829495] UBI: max. allowed volumes:       128
> [   12.834144] UBI: wear-leveling threshold:    4096
> [   12.838891] UBI: number of internal volumes: 1
> [   12.843425] UBI: number of user volumes:     1
> [   12.847860] UBI: available PEBs:             0
> [   12.852325] UBI: total number of reserved PEBs: 8185
> [   12.857340] UBI: number of PEBs reserved for bad PEB handling: 81
> [   12.863479] UBI: max/mean erase counter: 6/3
> [   12.867807] UBI: background thread "ubi_bgt2d" started, PID 911

The possibility exists to double the eraseblock size by treating 2 eraseblocks as
though it was 1.  That should halve the UBI load time to 3 seconds but it would
use a bit more memory in UBIFS.  Of course you could double again, with yet
more memory required by UBIFS.

  reply	other threads:[~2009-07-22  9:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 17:00 UBI FS mounting time Bosi Daniele
2009-07-22  6:44 ` Adrian Hunter
2009-07-22  7:12   ` Corentin Chary
2009-07-22  7:38     ` Adrian Hunter
2009-07-22  7:57       ` Corentin Chary
2009-07-22  8:12         ` Adrian Hunter
2009-07-22  8:30           ` Artem Bityutskiy
2009-07-22  8:36             ` Artem Bityutskiy
2009-07-22  9:34         ` Jamie Lokier
2009-07-22  7:22   ` Canella Matteo
2009-07-22  8:10   ` Canella Matteo
2009-07-22  9:19     ` Adrian Hunter [this message]
2009-07-22 14:32       ` LEB size configuration (was: UBI FS mounting time) Canella Matteo
2009-07-22 14:53         ` LEB size configuration Artem Bityutskiy
2009-07-22 15:12           ` Canella Matteo
2009-07-22 15:15             ` Artem Bityutskiy
2009-07-22  9:30 ` UBI FS mounting time Artem Bityutskiy

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=4A66D988.4050503@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=Matteo.Canella@mta.it \
    --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;
as well as URLs for NNTP newsgroup(s).