From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Nikita V. Youshchenko" <nyoushchenko@mvista.com>
Cc: Richard Weinberger <richard@nod.at>,
Rob Taylor <rtaylor@mvista.com>,
Alexander Kaliadin <akaliadin@mvista.com>,
linux-mtd@lists.infradead.org, Pavan Jadhav <pjadhav@mvista.com>
Subject: Re: ubi_update_fastmap: could not find an early PEB
Date: Wed, 27 Jun 2012 15:15:33 +0300 [thread overview]
Message-ID: <1340799333.1799.15.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <201206271507.42980@zigzag.lvk.cs.msu.su>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Wed, 2012-06-27 at 15:07 +0400, Nikita V. Youshchenko wrote:
> > Especially the size of both pools used by fastmap needs to be discussed
> > more. If the pool size is too small UBI was to write the fastmap very
> > often. A too large pool means that attaching takes longer because
> > fastmap has to rescan more PEBs.
>
> I'd prefer to see those configurable.
I agree, all parameters should be in the fastmap anchor instead of being
hard-coded. It is OK to hard-code the default values for the
auto-format, but if the UBI image is created with ubinize - the user
should be able to tune for himself.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-27 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 16:05 ubi_update_fastmap: could not find an early PEB Nikita V. Youshchenko
2012-06-22 16:32 ` Richard Weinberger
2012-06-22 17:26 ` Nikita V. Youshchenko
2012-06-22 17:37 ` Richard Weinberger
2012-06-22 18:46 ` Nikita V. Youshchenko
2012-06-22 18:49 ` Richard Weinberger
2012-06-27 10:56 ` Artem Bityutskiy
2012-06-27 11:00 ` Richard Weinberger
2012-06-27 11:07 ` Nikita V. Youshchenko
2012-06-27 12:15 ` 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=1340799333.1799.15.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=akaliadin@mvista.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nyoushchenko@mvista.com \
--cc=pjadhav@mvista.com \
--cc=richard@nod.at \
--cc=rtaylor@mvista.com \
/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