All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] Does uboot EBS(erase block summary) to reduce JFFS2 scaning time?
Date: Tue, 3 Nov 2009 14:30:17 +0100	[thread overview]
Message-ID: <OF71BC4E6C.691DB33D-ONC1257663.00499C8E-C1257663.004A2F36@transmode.se> (raw)
In-Reply-To: <20091103132108.E06963F6EC@gemini.denx.de>

Wolfgang Denk <wd@denx.de> wrote on 03/11/2009 14:21:08:
>
> Dear Joakim Tjernlund,
>
> In message <OF0C7E2190.C549E7B4-ONC1257663.003B88C7-C1257663.
> 003BFEAC at transmode.se> you wrote:
> > >
> > > HeLei <leon.he@msn.com> wrote on 03/11/2009 09:21:04:
> > > >
> > > > Thank you, Jocke
> >
> > > > > - impl. a better crc32(use the one from linux)
> > >
> > > Attaching a very crude port of linux crc32. This boots a linux img
> > > for me and handles the environment crc as well. Feel free
> > > to clean it up and submit to u-boot.
> > >
> > >      Jocke
> >
> > So I could not help myself, here is a better port of crc32 to u-boot.
> > You will probably get at small conflict due to LINK_OFF, just remove
> > the LINK_OFF stuff for now.
> > Could you test and report?
> > Do you have a little or big endian target?
>
> I understand you will resend this patch with a proper Subject: for
> real review on the list?

Yes, I just wanted some external testing but this seems not to happen.

>
> You also might want to explain in which way this patch is "more
> efficient" - in terms of memory footprint, or execution time, or
> both? And by how much? Tested in which envrionment(s) ?

hmm, I did this optimization many years ago for JFFS2 in linux. I don't
have any numbers but I can give you some hints w.r.t number of insn
in the inner loop(later though). Footprint will be higher.

 Jocke

  reply	other threads:[~2009-11-03 13:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  6:37 [U-Boot] Does uboot EBS(erase block summary) to reduce JFFS2 scaning time? HeLei
2009-11-03  7:41 ` Joakim Tjernlund
2009-11-03  8:21   ` HeLei
2009-11-03  9:08     ` Joakim Tjernlund
2009-11-03  9:21       ` HeLei
2009-11-03  9:29         ` Joakim Tjernlund
2009-11-03  9:39           ` HeLei
2009-11-03  9:52             ` Joakim Tjernlund
2009-11-03 10:02               ` HeLei
2009-11-03  9:20     ` Joakim Tjernlund
2009-11-03  9:26       ` HeLei
2009-11-03  9:35         ` Joakim Tjernlund
2009-11-03 10:55       ` Joakim Tjernlund
2009-11-03 11:08         ` HeLei
2009-11-03 11:13           ` Joakim Tjernlund
2009-11-03 11:21             ` HeLei
2009-11-03 13:21         ` Wolfgang Denk
2009-11-03 13:30           ` Joakim Tjernlund [this message]
2009-11-03 15:57           ` Joakim Tjernlund
2009-11-03  9:43     ` Joakim Tjernlund
2009-11-03 10:01       ` HeLei
2009-11-05  8:33   ` HeLei

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=OF71BC4E6C.691DB33D-ONC1257663.00499C8E-C1257663.004A2F36@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --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 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.