All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@lazybastard.org>
To: Jason Lunz <lunz@falooley.org>
Cc: Felix Fietkau <nbd@openwrt.org>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] block2mtd oops in erase function.
Date: Wed, 21 Feb 2007 14:47:54 +0000	[thread overview]
Message-ID: <20070221144754.GC464@lazybastard.org> (raw)
In-Reply-To: <20070221030254.GA11044@avocado.homenet>

On Tue, 20 February 2007 22:02:54 -0500, Jason Lunz wrote:
> On Tue, Feb 20, 2007 at 09:55:13PM +0000, Jörn Engel wrote:
> > Is it ok if I just pass this URL?
> > http://kernel.org/git/?p=linux/kernel/git/joern/misc.git
> > 
> > The top three patches are test-worthy.
> 
> I'm running with all three. everything seems fine.

Great!

> Mount time of a ~56M jffs2 partition went from ~72s to ~54s.

Ouch!  While this is a significant improvement, 54s is still quite bad.
The 512MiB partition on the OLPC is mounting in ~3.4s with JFFS2 and
~60ms with LogFS.  Imo 3.4s is already bad, and 54s is way beyond.

Now where is time lost?  One candidate is erase block summary, enabling
it usually gives roughly a 6x performance improvement.  That would get
you down to ~9s.

Another next thing I suspect is the erase size.  The default is 4KiB,
which is rather small.  Can you try setting it to 64KiB or maybe even
128KiB?

Instead of passing "block2mtd=/dev/foo", you can pass
"block2mtd=/dev/foo,64KiB" if my memory doesn't fail me.

Changing the erase size to a multiple of the previous erase size should
be fine with JFFS2 (a smaller erase size could lead to data loss), but
you likely won't get better performance unless you recreate the
filesystem.  Maybe something like

$ mount /dev/mtdX /mnt -t jffs2
$ (cd /mnt && tar cvpf /tmp/foo.tgz .)
$ umount /mnt
$ flash_eraseall /dev/mtdX
$ mount /dev/mtdX /mnt -t jffs2
$ (cd /mnt && tar vpf /tmp/foo.tgz)
$ umount /dev/mtdX

Unless you are happy with the current mount time, of course.  Noone is
forcing you to change anything.

Jörn

-- 
Do not stop an army on its way home.
-- Sun Tzu

  parent reply	other threads:[~2007-02-21 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 21:29 [PATCH] block2mtd oops in erase function Felix Fietkau
2007-02-19 22:20 ` Jörn Engel
2007-02-19 22:30   ` Jörn Engel
2007-02-20  2:27     ` Felix Fietkau
2007-02-20 10:53       ` Jörn Engel
2007-02-20 21:35         ` Jason Lunz
2007-02-20 21:55           ` Jörn Engel
     [not found]             ` <20070221030254.GA11044@avocado.homenet>
2007-02-21 14:47               ` Jörn Engel [this message]
2007-02-21 15:42                 ` Jason Lunz
2007-02-21 16:02                   ` Jörn Engel
2007-02-21 20:26                     ` Jason Lunz
2007-02-21 21:43                       ` Jörn Engel

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=20070221144754.GC464@lazybastard.org \
    --to=joern@lazybastard.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lunz@falooley.org \
    --cc=nbd@openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.