From: Artem Bityutskiy <dedekind@infradead.org>
To: Meeta Mishra <Meeta.Mishra@gnss.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Query regarding JFFS2 init
Date: Thu, 19 Jul 2007 09:55:34 +0300 [thread overview]
Message-ID: <1184828134.3531.175.camel@sauron> (raw)
In-Reply-To: <9D98C51005D80D43A19A3DF329A61D6901A91C05@INDEXCH2003.gmi.domain>
On Thu, 2007-07-19 at 11:08 +0530, Meeta Mishra wrote:
> Hi,
>
> I want to know what actually happens when sbin/init is invoked in JFFS2.
>
>
> I'm using small page Nand device with a 12MB JFFS2 partition (which has
> 5.6 MB JFFS2 image). Kernel boots up from Nand flash and comes to
> sbin/init; the total execution of sbin/init is taking 13 sec (which
> seems huge to me).
>
> I traced the read calls during sbin/init execution and found that approx
> 13 MB of data is being read which is taking approx 7.8 sec (out of 13
> sec). Does anyone has any idea about the 13 MB data that's being read?
13 Megs are read because of checking - JFFS2 has to check all data just
after it has been mounted.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-07-19 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 5:38 Query regarding JFFS2 init Meeta Mishra
2007-07-19 6:55 ` Artem Bityutskiy [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=1184828134.3531.175.camel@sauron \
--to=dedekind@infradead.org \
--cc=Meeta.Mishra@gnss.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