From: David Woodhouse <dwmw2@infradead.org>
To: ebiederman@lnxi.com (Eric W. Biederman)
Cc: linux-mtd@lists.infradead.org, ajlennon@arcom.co.uk
Subject: Re: CPU caching of flash regions.
Date: Mon, 14 May 2001 17:17:45 +0100 [thread overview]
Message-ID: <4987.989857065@redhat.com> (raw)
In-Reply-To: <m38zk07wtz.fsf@DLT.linuxnetworx.com>
ebiederman@lnxi.com said:
> What kind of scenario are we talking about? Do the pages get read
> multiple times? Of is it just that that copy_from needs to be more
> highly optimized like memcpy? I suspect that before the whole
> interface changes you should experiment and see what really needs to
> be done.
This is during the initial mount of JFFS2. Nothing should be read twice -
but we should at least be able to fill cache lines and do burst reads from
the flash chips, shouldn't we?
> As for interface changes I would suggest an additional opertation
> memory_barrier that forces the flush if needed.
The original plan involved no interface changes - I was suggesting that the
map driver would DTRT with the caches internally.
> But I really think you should be able to get it working faster simply
> by optimizing the copy_from routine.
Most of the copy_from routines use memcpy_fromio(), which on i386 is just
a memcpy(). It ought to be fairly close to optimal.
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.
--
dwmw2
next prev parent reply other threads:[~2001-05-14 16:13 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 [this message]
2001-05-14 16:32 ` Eric W. Biederman
2001-05-15 10:46 ` Alex Lennon
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=4987.989857065@redhat.com \
--to=dwmw2@infradead.org \
--cc=ajlennon@arcom.co.uk \
--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