From: "Nancy Isaac" <nancy.isaac@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: JFFS2 Questions
Date: Thu, 31 Jul 2008 17:27:54 -0700 [thread overview]
Message-ID: <1bcc666d0807311727u1be8bc41t41ee6b8741f6b6cf@mail.gmail.com> (raw)
Please let me know if I have emailed the wrong group with these questions.
I have been working on bringing up an embedded system with 8313
processor, 128MB ram, 32MB NOR and 512MB NAND flash.
We are using 2.6.21 kernel. We boot out of NOR using u-boot and
program the NAND flash with jffs2 images for kernel and root file
system.
My first question is very basic. my rootfs.jffs2 image is 59MB when I
create it using mkfs.jffs2 and do an ls -l on the file.
What is the size of the image stored in the NAND flash? I have
compression enabled, so I expected it to be still 50MB. When I do a
du on the root file system after it's been mounted on the NAND flash,
it shows the size as 114MB. I am wondering about the difference
because I need to figure out how much space to allocate to accomodate
an upgrade. Do I base it on the 59MB size or the 114MB size?
The second question is about the boot time. With the 59MB file
system, it takes about 5 minutes to boot up and mount the file system.
I know that JFFS2 is slower for boot up due to the scanning that
happens at the beginning, but 5 minutes seems too long and makes me
think I am doing something really wrong. I added printk time stamps
to see if I can see where the time is being spent. It looks like the
kernel bootup is pretty fast (30secs), but after I get to "Freeing
unused kernel memory", it stays there for a long time with no output
to the screen and then finally the init scripts start running and I
get some output. Are there any other tools I can use to figure out
what's going on at this time?
Thanks
Nancy
reply other threads:[~2008-08-01 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1bcc666d0807311727u1be8bc41t41ee6b8741f6b6cf@mail.gmail.com \
--to=nancy.isaac@pobox.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®