From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Jörn Engel" <joern@logfs.org>,
linux-mtd@lists.infradead.org
Subject: Re: Jffs2 and big file = very slow jffs2_garbage_collect_pass
Date: Fri, 18 Jan 2008 17:17:34 +0100 [thread overview]
Message-ID: <4790D11E.6060201@parrot.com> (raw)
In-Reply-To: <20080118064852.026b0c82@zod.rchland.ibm.com>
Josh Boyer wrote:
> On Fri, 18 Jan 2008 10:39:29 +0100
> Matthieu CASTET <matthieu.castet@parrot.com> wrote:
>
>
>> In my case the mount is ok : less than 5-10s.
>> The platform used is an arm926 @247 Mhz
>
> Ok, so running at 247MHz your board has to calculate the CRCs on 41324
> nodes before the file can be opened. I have no idea how long that
> should really take, but you're doing about 57 nodes per second if it's
> taking 12 minutes.
>
> As Jörn and David suggested, do some profiling to see where it is
> spending most of it's time.
>
I sent a mail, but because of Message has a suspicious header, the
message wait moderator approval.
In summary,
the code spend lot's of time in the rbtree code (7 minutes) and 4
minutes in jffs2_get_inode_nodes.
Matthieu
54366 rb_prev 543,6600
28345 rb_next 283,4500
8602 default_idle 71,6833
10251 __raw_readsl 40,0430
49648 jffs2_get_inode_nodes 11,8097
251 s3c2412_nand_devready 7,8438
1222 crc32_le 4,8492
next prev parent reply other threads:[~2008-01-18 16:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:12 Jffs2 and big file = very slow jffs2_garbage_collect_pass Matthieu CASTET
2008-01-17 16:26 ` Jörn Engel
2008-01-17 17:43 ` Josh Boyer
2008-01-18 9:39 ` Matthieu CASTET
2008-01-18 12:48 ` Josh Boyer
2008-01-18 16:17 ` Matthieu CASTET [this message]
2008-01-18 17:55 ` Josh Boyer
2008-01-18 18:17 ` Jörn Engel
2008-01-21 15:57 ` Matthieu CASTET
2008-01-21 21:25 ` Jörn Engel
2008-01-21 22:16 ` Josh Boyer
2008-01-21 22:29 ` Jörn Engel
2008-01-22 8:57 ` Matthieu CASTET
2008-01-22 12:03 ` Jörn Engel
2008-01-22 13:24 ` Ricard Wanderlof
2008-01-22 15:05 ` Jörn Engel
2008-01-23 9:23 ` Ricard Wanderlof
2008-01-23 10:19 ` Jörn Engel
2008-01-23 10:41 ` Ricard Wanderlof
2008-01-23 10:57 ` Jörn Engel
2008-01-23 11:57 ` Ricard Wanderlof
2008-01-23 13:01 ` Jörn Engel
2008-01-23 13:16 ` Ricard Wanderlof
2008-01-23 14:06 ` Jörn Engel
2008-01-23 14:25 ` Ricard Wanderlof
2008-01-21 22:36 ` Glenn Henshaw
2008-01-18 17:20 ` Glenn Henshaw
2008-01-18 18:39 ` Jamie Lokier
2008-01-18 21:00 ` Jörn Engel
2008-01-19 0:23 ` Jamie Lokier
2008-01-19 2:38 ` Jörn Engel
2008-01-17 23:22 ` David Woodhouse
2008-01-18 9:45 ` Matthieu CASTET
2008-01-18 18:20 ` Jamie Lokier
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=4790D11E.6060201@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--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 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.