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 16:59:37 +0300 [thread overview]
Message-ID: <1302271177.2834.26.camel@localhost> (raw)
In-Reply-To: <OFADA4774B.BD633326-ONC125786C.00461A66-C125786C.00466AC0@sewerin.de>
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.
> When changing the vol_type attribute to dynamic, the mount time is
> much shorter (about 1 Second).
This is because UBI change the CRC of the whole static volume, this is
where you spend time.
> The point of interest are the timings.
> The static volume is designed for speed up booting and mounting, isn t
> it?
No, I think it was originally designed to store short blobs of data like
a configuration file.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-08 14:02 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 [this message]
2011-04-08 14:10 ` 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=1302271177.2834.26.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