From: akorolev <alexey.korolev@intel.com>
To: Semih Hazar <semih.hazar@indefia.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Slow NAND + JFFS2
Date: Wed, 25 Apr 2007 18:44:08 +0400 [thread overview]
Message-ID: <462F6938.90903@intel.com> (raw)
In-Reply-To: <462F45B1.8020007@indefia.com>
Hi,
You may try to clarify if compression is off.
> Hi,
>
> I'm using a 256 MiB NAND Flash from ST -> Manufacturer ID: 0x20, Chip
> ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit) with JFFS2. The filesystem is
> mounted as rootfs and the size is around 60 megs.
>
> Filesystem operations seem very slow to me. Such as:
>
> It takes almost 1 and a half minutes to copy a 30 meg file.
> Mounting the filesystem takes around 1 minute.
>
> # ls -lh
> -rw-r--r-- 1 root root 30.3M Jan 1 00:05 gcc.tgz
> # time cp gcc.tgz 1
> real 1m 22.37s
> user 0m 0.09s
> sys 1m 22.22s
> #
>
>
> This seemed really slow to me, but I don't have any other benchmarks.
> Can someone comment on these values ?
>
> The processor is at32ap7000 from Atmel, running at 160 MHz.
> I'm running kernel 2.6.20.1 with cpu related patches from Atmel and our
> own nand patches which are almost the replica of at91_nand.c (I can send
> it if you need)
>
> I also changed the read enable and write enable pulse timings according
> to the minimum values stated in NAND flash's datasheet.
>
> If this copy/mount time are really slow as I think, where should I check
> ? Is this a JFFS2 related issue or should I try to find some problems in
> our nand driver or ... ?
>
> Best regards,
> Semih Hazar
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
next prev parent reply other threads:[~2007-04-25 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 12:12 Slow NAND + JFFS2 Semih Hazar
2007-04-25 12:23 ` Josh Boyer
2007-04-25 14:44 ` akorolev [this message]
2007-04-25 15:36 ` Semih Hazar
2007-04-25 16:09 ` Haavard Skinnemoen
2007-04-25 16:17 ` Semih Hazar
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=462F6938.90903@intel.com \
--to=alexey.korolev@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=semih.hazar@indefia.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 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.