public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Lawnick <nospam_lawnick@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] JFFS2-Summary support for u-boot
Date: Mon, 29 Sep 2008 11:34:02 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080929T112829-943@post.gmane.org> (raw)
In-Reply-To: 1222680893.31048.8.camel@gentoo-jocke.transmode.se

Joakim Tjernlund <joakim.tjernlund <at> transmode.se> writes:

> 
> On Mon, 2008-09-29 at 08:45 +0000, Michael Lawnick wrote:
> > Hi *,
> > 
> > please feel free to correct me if I tell sh**:
> > As far as I was told, bad JFFS2 boot performance of u-boot is result of not
> > supporting summary. (Because there is no JFFS2 but only JFFS support?)
> 
> It is not missing SUMMARY, it is excessive scanning of empty flash
> blocks. Look at jffs2/scan.c, it only scan the first 4KB or before
> declaring the block empty.

Ok, did I get you correct:
The performance difference between u-boot and linux is based on skipping
senseless scans of empty blocks?
I've taken a little look into scan.c
The comment "The code lacks more or less any comment, and is still arcane and
difficult to read in places." doesn't make me happy.

Has anybody tried to (and succeeded in) speed up u-boot?

Michael

  reply	other threads:[~2008-09-29 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  8:45 [U-Boot] JFFS2-Summary support for u-boot Michael Lawnick
2008-09-29  9:34 ` Joakim Tjernlund
2008-09-29 11:34   ` Michael Lawnick [this message]
2008-09-29 11:54     ` Joakim Tjernlund
2008-09-29 12:49       ` Michael Lawnick
2008-09-29 14:02         ` Joakim Tjernlund
2008-09-30  7:40           ` Michael Lawnick
2008-10-07  1:23             ` Detlev Zundel
2008-09-29 14:05     ` Detlev Zundel
2008-09-29 18:13       ` Michael Lawnick

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=loom.20080929T112829-943@post.gmane.org \
    --to=nospam_lawnick@gmx.de \
    --cc=u-boot@lists.denx.de \
    /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