From: Thomas Gleixner <gleixner@autronix.de>
To: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: jffs2_scan_make_ino_cache() in scan.c very slow
Date: Thu, 21 Feb 2002 22:58:30 +0100 [thread overview]
Message-ID: <02022122583010.18560@thomas> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLAEKJFBAA.joakim.tjernlund@lumentis.se>
On Thursday, 21. February 2002 15:34, Joakim Tjernlund wrote:
>
> > Sorry. Can you make sure it still applies to the current CVS tree and
> > resend it?
> Well, I not using the current CVS at the moment. It will take some time
> until I upgrade again.
I tried it with current CVS and there is no difference without or with
optimizing. Mount time for a 8MB NAND partition in all variants ~11 sec. on a
74MHz ARM7.
--
Thomas
__________________________________________________
Thomas Gleixner, autronix automation GmbH
auf dem berg 3, d-88690 uhldingen-muehlhofen
fon: +49 7556 919891 , fax: +49 7556 919886
mail: gleixner@autronix.de, http://www.autronix.de
next prev parent reply other threads:[~2002-02-21 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 13:03 Update on my problem Chris Fowler
2002-02-21 14:05 ` jffs2_scan_make_ino_cache() in scan.c very slow Joakim Tjernlund
2002-02-21 14:18 ` David Woodhouse
2002-02-21 14:34 ` Joakim Tjernlund
2002-02-21 15:34 ` Joakim Tjernlund
2002-02-21 15:47 ` David Woodhouse
2002-02-21 16:14 ` Joakim Tjernlund
2002-02-21 21:58 ` Thomas Gleixner [this message]
2002-02-21 22:05 ` Joakim Tjernlund
2002-02-21 22:22 ` Thomas Gleixner
2002-02-21 22:27 ` Joakim Tjernlund
2002-02-21 22:44 ` Thomas Gleixner
2002-02-21 22:49 ` Joakim Tjernlund
2002-02-21 22:43 ` jffs2_scan_make_ino_cache() in scan.c very slow, new improvment Joakim Tjernlund
2002-02-22 10:56 ` Joakim Tjernlund
2002-02-21 19:27 ` Update on my problem Russ Dill
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=02022122583010.18560@thomas \
--to=gleixner@autronix.de \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox