From: Artem Bityutskiy <dedekind1@gmail.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>,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: LEB size configuration
Date: Wed, 22 Jul 2009 17:53:18 +0300 [thread overview]
Message-ID: <4A6727DE.4020005@gmail.com> (raw)
In-Reply-To: <BD9F3F3F5A6CCF4BA032B9FED4DD312E5D09531F36@mta-digimail.MTA.INT>
On 07/22/2009 05:32 PM, Canella Matteo wrote:
> Hi Adrian, thank you for your reply,
>
>> 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.
>
> I'm a little bit jammed... I surfed all the docs and faqs but I can't find the answers.
> I'm trying to double the logical erase block size.
> I've a 1Gb NAND flash.
>
> Here's my steps:
>
> Looking to the old dmesg of the flash mounting I see:
> [ 6.705712] UBI: logical eraseblock size: 126976 bytes
>
> First question: Why LEB size needs to be smaller than PEB size? PEB size is 128KiB = 131072 byte. Is it mandatory to have LEB size smaller than PEB size? How much smaller?
You cannot improve your UBI attach time without doing coding,
unfortunately. If you are ready to do coding, you should really
go through UBI documentation. It answers your question.
> Whatever, I try to double this value:
> mkfs.ubifs -m 2048 -e 253952 -c 4096 -o ubifs.img
Sorry, but you really should spend more time reading docs if you want to
improve UBI/UBIFS. From what I see you do not really distinguish between
UBI and UBIFS.
> the "-e" option is the LEB size (126976 * 2 = 253952)
> "-c" option is the max LEB count, so I guess 4096 for 1 Gigabyte is the right number.
The suggested change should be done either on MTD level, or on UBI level.
The FAQ entry I wrote for you briefly explains how one could do this on
UBI level.
...
> Here I've got an error and the logical eraseblock size that isn't what I expected (126976 instead of 253952).
Yes, you have created UBIFS image for larger LEB, but UBI does not support
it, so you see errors because of that disagreement.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-07-22 14:56 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
2009-07-22 14:32 ` LEB size configuration (was: UBI FS mounting time) Canella Matteo
2009-07-22 14:53 ` Artem Bityutskiy [this message]
2009-07-22 15:12 ` LEB size configuration 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=4A6727DE.4020005@gmail.com \
--to=dedekind1@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=Matteo.Canella@mta.it \
--cc=adrian.hunter@nokia.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;
as well as URLs for NNTP newsgroup(s).