From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_scan_make_ino_cache() in scan.c very slow
Date: Thu, 21 Feb 2002 15:47:03 +0000 [thread overview]
Message-ID: <14794.1014306423@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLOEKKFBAA.joakim.tjernlund@lumentis.se>
joakim.tjernlund@lumentis.se said:
> Setting INOCACHE_HASHSIZE to 14(higher values makes it PANIC at
> mount, don't know why)
Possibly because the superblock union gets too big. What does it say when
it panics?
> and changed the beginning of jffs2_scan_make_ino_cache() to {
> is it OK to make *ic an static variable?
No - consider 'mount /opt & mount /usr' - it has to be per-filesystem. If
it's this which really makes a difference, then we can add the pointer to
the jffs2_sb_info. Can you make it keep a count of how many hits and misses
there are, and print the counts when it's finished mounting?
> Now my mount time is just half of what it used to be!!(well almost :-)
Cool - can you try each of these changes on its own and measure the benefit
of each?
--
dwmw2
next prev parent reply other threads:[~2002-02-21 15:35 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 [this message]
2002-02-21 16:14 ` Joakim Tjernlund
2002-02-21 21:58 ` Thomas Gleixner
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=14794.1014306423@redhat.com \
--to=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