From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian.Ruppert@sewerin.de
Cc: linux-mtd@lists.infradead.org, Detlev Zundel <dzu@denx.de>
Subject: Re: time to mount static volume seems to be too long
Date: Fri, 08 Apr 2011 17:10:47 +0300 [thread overview]
Message-ID: <1302271847.2834.34.camel@localhost> (raw)
In-Reply-To: <1302271177.2834.26.camel@localhost>
On Fri, 2011-04-08 at 16:59 +0300, Artem Bityutskiy wrote:
> Hello,
>
> On Fri, 2011-04-08 at 14:48 +0200, Bastian.Ruppert@sewerin.de wrote:
> > [ubifs]
> > mode=ubi
> > image=/opt/rfsb/build/images/image.ubifs
> > vol_id=0
> > vol_size=46080KiB
> > vol_type=static
> > vol_name=rootfs
> > vol_flags=autoresize
> >
> > I can mount the rootfs, but with this configuration the rootfs mount
> > time is about 8 Seconds for the image in a 71MB Partition.
>
> IMHO, it makes little sense to use UBIFS on top of static volumes.
> Static volumes were really meant to store raw blob of data, where you
> want UBI to protect it with CRC for you.
>
> UBIFS has its own CRC protection, so with static volume you get double
> CRC. Note, to force UBIFS checking data CRC on read you need to use
> "chk_data_crc" option, see here:
>
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_checksumming
>
> IOW, you do not need double-work.
BTW, if you appreciate the help from community and want to contribute,
it'd be nice if you wrote a short text to our FAQ:
"why a dynamic volume is faster to access than a static volume of the
same size?"
You can add it to this web page:
http://www.linux-mtd.infradead.org/faq/ubi.html
To do this, clone
http://git.infradead.org/mtd-www.git
edit faq/ubi.xml, type "make", make sure it compiles. Then open it with
your browser, check it looks good in html form, then send the patch.
Thanks! :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-08 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 12:48 time to mount static volume seems to be too long Bastian.Ruppert
2011-04-08 13:59 ` Artem Bityutskiy
2011-04-08 14:10 ` Artem Bityutskiy [this message]
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=1302271847.2834.34.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Bastian.Ruppert@sewerin.de \
--cc=dzu@denx.de \
--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