From: DMcLeod <dmcleod@bittware.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 access time
Date: Thu, 17 Jan 2008 11:06:41 -0500 [thread overview]
Message-ID: <478F7D11.30606@bittware.com> (raw)
In-Reply-To: <20080116183458.2c997320@zod.rchland.ibm.com>
Josh Boyer wrote:
> On Wed, 16 Jan 2008 08:57:50 -0500
> DMcLeod <dmcleod@bittware.com> wrote:
>
>
>> Hi all,
>>
>> We are using uClinux git 2.6.23. We have 4 2.5MB files sitting in a
>> directory on a ~40MB jffs2 partition (on NOR flash). The very first time
>> we do an 'ls' in that directory, the response takes literally minutes.
>> After the initial delay, any accesses to those files are very
>> quick.,,
>>
>
> That is normal for large files. JFFS2 has do the CRC checking on all
> the nodes for those large files. That is a lot of nodes to check. You
> might want to look into using the eraseblock summary feature.
>
>
>> Originally, we started off with the Microtronix 1.4 kernel and
>> it did not have this problem. The pre-git version of uClinux-dist had
>> this problem but not as severe - it was more like 40 seconds to list the
>> contents of that directory.
>>
> I have no idea what those two kernels are, but older JFFS2 used to do
> all the CRC checking at mount time. So mount would be slow and runtime
> access would be relatively quick.
>
The Microtronix kernel is the kernel built by Altera's Quartus 6.1
suite. By "pre-git" version, we just meant the packaged version from
nioswiki, rather than getting it from the git server.
At any rate, it turns out that having the verbosity level set to 2 in
the jffs2 section of menuconfig was our problem. The kernel was so
dragged down by having to bombard /proc/kmsg with jffs2 printk's that it
caused the huge delays we were seeing. We set verbosity back to 0 and
all is well.
Thanks :-)
> josh
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
next prev parent reply other threads:[~2008-01-17 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 13:57 JFFS2 access time DMcLeod
2008-01-17 0:34 ` Josh Boyer
2008-01-17 16:06 ` DMcLeod [this message]
2008-01-17 8:47 ` Ricard Wanderlof
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=478F7D11.30606@bittware.com \
--to=dmcleod@bittware.com \
--cc=jwboyer@gmail.com \
--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