public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: michael <trimarchi@gandalf.sssup.it>
To: DMcLeod <dmcleod@bittware.com>
Cc: linux-mtd@lists.infradead.org, Will Wagner <will_wagner@carallon.com>
Subject: Re: First access to mounted jffs2 partition is slow
Date: Tue, 12 Feb 2008 19:03:56 +0100	[thread overview]
Message-ID: <47B1DF8C.4090500@gandalf.sssup.it> (raw)
In-Reply-To: <47B1D5A7.4000509@bittware.com>

Hi,
> Will Wagner wrote:
>   
>> Hello,
>>
>> I have an ARM11 system with a JFFS2 partition in NAND flash. It works 
>> but the first time it is accessed after mounting it can be very slow.
>>
>> These are the steps I am performing:
>>
>> # flash_eraseall /dev/mtd4
>> Erasing 128 Kibyte @ 5fe0000 -- 99 % complete.
>> # time mount /dev/mtdblock4 /flash -t jffs2
>> real    0m 1.25s
>> user    0m 0.01s
>> sys     0m 0.13s
>> # time ls flash		- with an empty filsystem, this takes no time
>> real    0m 0.00s
>> user    0m 0.01s
>> sys     0m 0.00s
>> # cp /sdcard/bigfile flash/	- bigfile is ~8MB
>> # umount /flash
>> # time mount /dev/mtdblock4 /flash -t jffs2
>> real    0m 2.63s
>> user    0m 0.01s
>> sys     0m 0.50s
>> # time ls flash		- first time we do this it takes a long time
>> bigfile
>> real    0m 11.79s
>> user    0m 0.00s
>> sys     0m 0.18s
>> # time ls flash		- subsequent reads are fast
>> bigfile
>> real    0m 0.00s
>> user    0m 0.01s
>> sys     0m 0.00s
>>
>>     
I think that is a problem of jffs2 and I think that is related to the 
time spent during the fstat64 system but
I'm not sure. I have little experince with jffs2.

Regards Michael

      reply	other threads:[~2008-02-12 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 11:33 First access to mounted jffs2 partition is slow Will Wagner
2008-02-12 12:05 ` Matthieu CASTET
2008-02-12 17:21 ` DMcLeod
2008-02-12 18:03   ` michael [this message]

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=47B1DF8C.4090500@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=dmcleod@bittware.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=will_wagner@carallon.com \
    /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