From: "Alex Lennon" <ajlennon@arcom.co.uk>
To: "Eric W. Biederman" <ebiederman@lnxi.com>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: RE: CPU caching of flash regions.
Date: Tue, 15 May 2001 11:46:10 +0100 [thread overview]
Message-ID: <NEBBKJHOALKOLCFPGELEMEPACKAA.ajlennon@arcom.co.uk> (raw)
In-Reply-To: <m3vgn36gcw.fsf@DLT.linuxnetworx.com>
Eric,
> Actually, the board used for the offending profile is a board with paged
> access to the flash, so it's slightly slower than some others - but the
> overhead shouldn't be too high. And the cache benefit would be more
limited.
> What kind of chip is being used?
Two contiguous Intel Strataflash 28F640's giving 16Mb total
> What bus is it on?
ISA
> And how fast is it?
8Mhz
> Second. What kind of processor, and what kind of chipset are being used?
National Geode GX1 300Mhz with CS5530 support chipset
To generate some figures I knocked together code which reads the 16Mb from
the flash, paging as it goes. Nothing is done with the data. This takes
about 16s
With the hardcoded value of CONFIG_JFFS2_FS_DEBUG set to 2 in
fs/jffs2/nodelist.h
I get jffs2 root fs mount times in excess of 34s.
When I remove the debugging I get mount times of around 26s
Obviously the figures obtained from df need some massaging to take account
of compression
but I get:
/dev/root 14336 3760 10576 26% /
/dev/mtdblock1 1280 644 636 50% /var
/dev/ram0 3963 26 3733 1% /var/tmp
So what does this mean ? Can I expect a fourfold increase in mount time with
a full f/s ?
Should I be comparing a 26s jffs2 mount to an idealistic 4s 4Mb flash read ?
Regards,
Alex
next prev parent reply other threads:[~2001-05-15 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 14:15 CPU caching of flash regions David Woodhouse
2001-05-14 15:51 ` Eric W. Biederman
2001-05-14 16:17 ` David Woodhouse
2001-05-14 16:32 ` Eric W. Biederman
2001-05-15 10:46 ` Alex Lennon [this message]
2001-05-15 14:32 ` Eric W. Biederman
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=NEBBKJHOALKOLCFPGELEMEPACKAA.ajlennon@arcom.co.uk \
--to=ajlennon@arcom.co.uk \
--cc=dwmw2@infradead.org \
--cc=ebiederman@lnxi.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