From: Shane Nay <shane@agendacomputing.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Nicolas Pitre <nico@cam.org>, <mstumpf@pobox.com>, <mtd@infradead.org>
Subject: Re: MTD, generic physmap memory, MTD_BLOCK
Date: Mon, 18 Dec 2000 21:31:43 +0000 [thread overview]
Message-ID: <0012182131432A.11759@www.easysolutions.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0012172223230.15911-100000@imladris.demon.co.uk>
On Sunday 17 December 2000 22:24, David Woodhouse wrote:
> Unless there's something missing (or I'm being dim) that code doesn't do
> XIP. It still copies from the cramfs into the page provided to
> cramfs_readpage.
>
> What you want to do is make up some struct pages to represent the pages
> of the ROM chip and pre-populate the page cache with those pages directly
> - marked readonly, of course.
Hehe, no, it's not an XIP implementation. I think I mentioned in my message,
even if I didn't make it clear (probably not) that this only made cramfs read
directly off of the flash, taking one layer of abstraction out. It kills the
buffer, and the copy to buffer that would usually be associated with a dev
device, so it speeds up performance of cramfs on a flash device. It's _only_
a performance hack at this point.
But we are working on XIP for cramfs. But this requires either expanding the
inode, or stealing a bit or two away from GIDS, or UIDs. This is only a
"linear addressing" patch.
Thanks,
Shane.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-12-19 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 16:48 MTD, generic physmap memory, MTD_BLOCK Michael Stumpf
2000-12-13 19:02 ` Nicolas Pitre
2000-12-16 1:04 ` Shane Nay
2000-12-17 22:24 ` David Woodhouse
2000-12-18 21:31 ` Shane Nay [this message]
2000-12-19 9:24 ` David Woodhouse
2000-12-18 22:35 ` Shane Nay
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 13:32 Michael Stumpf
2000-12-19 2:51 ` Shane Nay
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=0012182131432A.11759@www.easysolutions.net \
--to=shane@agendacomputing.com \
--cc=dwmw2@infradead.org \
--cc=mstumpf@pobox.com \
--cc=mtd@infradead.org \
--cc=nico@cam.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