From: David Woodhouse <David.Woodhouse@mvhi.com>
To: Jason Gunthorpe <jgg@ualberta.ca>
Cc: mtd@infradead.org
Subject: Re: FFS2 and MTDs (flash)
Date: Mon, 05 Jul 1999 20:47:58 +0100 [thread overview]
Message-ID: <E111Eic-0002Ka-00@devel2.axiom.internal> (raw)
jgg@ualberta.ca said:
> It is not a huge deal, but if you are accessing the same memory again
> and again to do lookups like FFS2 does then a caching in system ram
> does speed things, and you get it for free ;>
>
I was thinking that the CPU L1/L2 cache will have much the same effect, but
I suppose on the type of systems we're talking about, there's not going to be
a usefully large CPU cache. Shame; it seemed like quite a nice idea.
It'd be nice to retain the option of doing it for those systems where it makes
sense - and I think the way you're doing it should allow that. So we can look
into it later if we want to.
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk
next reply other threads:[~1999-07-05 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-05 19:47 David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-07-05 19:06 FFS2 and MTDs (flash) David Woodhouse
1999-07-05 19:33 ` Jason Gunthorpe
1999-07-05 19:35 ` Rogier Wolff
1999-07-05 18:26 Loop Devices over NFS don't work? David Woodhouse
1999-07-05 18:45 ` FFS2 and MTDs (flash) Jason Gunthorpe
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=E111Eic-0002Ka-00@devel2.axiom.internal \
--to=david.woodhouse@mvhi.com \
--cc=jgg@ualberta.ca \
--cc=mtd@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