public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: simon polette <spolette@gmail.com>
Cc: linux-mtd@lists.infradead.org, spolette@adetelgroup.com
Subject: Re: Load UBI faster
Date: Fri, 15 May 2009 15:00:13 +0300	[thread overview]
Message-ID: <1242388813.27996.234.camel@localhost.localdomain> (raw)
In-Reply-To: <72795ccb0905130803y25acae9bwde94ed86d0dbb4f2@mail.gmail.com>

On Wed, 2009-05-13 at 17:03 +0200, simon polette wrote:
> My NAND is 256MB but I use only a 130MB partition for UBI/UBIFS.
> So I implemented the on-flash BBT, that made me save 120ms which is a
> sizeable improvement.
> On the other hand, skipping crc calculation for header doesn't seem to
> save much time (perhaps ~10ms so it's difficult to measure the
> difference).

Well, you could try profiling your system and see where you can
try to optimize things.

But I think the bottleneck is the flash reading. If you may
improve it - cool.

UBI has to scan the media, this is in it's design. You would
need to develop UBI2 to fix that:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_scalability

On thing you may do is to lessen the amount of eraseblocks by
joining your physical erasblocks on driver level, and report
eraseblock size 256KiB, instead of 128KiB. Then UBI would have
to read twice as less. But the drawback is that if one PEB is
bad, you waste its pair, which is not bad.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

      parent reply	other threads:[~2009-05-15 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06  7:26 Load UBI faster simon polette
2009-05-07  5:22 ` Artem Bityutskiy
2009-05-07  5:28   ` Artem Bityutskiy
2009-05-13 15:03     ` simon polette
2009-05-13 20:10       ` Corentin Chary
2009-05-15 12:00       ` 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=1242388813.27996.234.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=spolette@adetelgroup.com \
    --cc=spolette@gmail.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