From: "Bradley D. LaRonde" <brad@ltc.com>
To: <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Mounting a in-ROM filesystem efficiently
Date: Thu, 13 Dec 2001 15:52:08 -0500 [thread overview]
Message-ID: <096201c18418$07d86bf0$5601010a@prefect> (raw)
In-Reply-To: <20011213160007.D998D23CCB@persephone.dmz.logatique.fr> <9vb3k4$9kj$1@cesium.transmeta.com>
----- Original Message -----
From: "H. Peter Anvin" <hpa@zytor.com>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, December 13, 2001 3:38 PM
Subject: Re: Mounting a in-ROM filesystem efficiently
> Followup to: <20011213160007.D998D23CCB@persephone.dmz.logatique.fr>
> By author: Thomas Capricelli <orzel@kde.org>
> In newsgroup: linux.dev.kernel
>
> > Ideally, i would give address/length of the fs in ROM to a function, and
I
> > would get a ramdisk configured to read its data exactly there, and not
in
> > ram.
>
> The right thing for you to do is to write a block device driver, and
> then mount that block device like any order device. Your in-use data
> will be copied to RAM (i.e. cached), but it can be dropped and
> re-fetched as necessary. This should be the desired behaviour.
That's one way (q.v. MTD block device), but it adds an unecessary block
layer.
The cramfs patch I mentioned shuns the block layer and instead allows the fs
to read directly from ROM.
Regards,
Brad
next prev parent reply other threads:[~2001-12-13 20:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 16:02 Mounting a in-ROM filesystem efficiently Thomas Capricelli
2001-12-13 16:22 ` Bradley D. LaRonde
2001-12-13 16:41 ` Thomas Capricelli
2001-12-13 17:10 ` Bradley D. LaRonde
2001-12-13 18:02 ` Richard B. Johnson
2001-12-13 18:14 ` Bradley D. LaRonde
2001-12-13 18:34 ` Richard B. Johnson
2001-12-13 18:52 ` Bradley D. LaRonde
2001-12-13 19:41 ` Richard B. Johnson
2001-12-13 20:09 ` Bradley D. LaRonde
[not found] ` <08d701c18412/mnt/tmp/sendmee91d2c0601010a@prefect>
2001-12-18 1:27 ` Pavel Machek
2001-12-14 11:03 ` Catalin Marinas
2001-12-13 17:49 ` David Woodhouse
2001-12-13 18:06 ` Bradley D. LaRonde
2001-12-13 20:38 ` H. Peter Anvin
2001-12-13 20:52 ` Bradley D. LaRonde [this message]
2001-12-14 9:45 ` David Woodhouse
2001-12-14 15:27 ` Bradley D. LaRonde
2001-12-14 16:51 ` David Woodhouse
2001-12-14 17:02 ` Bradley D. LaRonde
2001-12-14 17:03 ` David Woodhouse
2001-12-14 17:12 ` Bradley D. LaRonde
2001-12-14 17:16 ` David Woodhouse
2001-12-14 17:27 ` Bradley D. LaRonde
2001-12-16 9:51 ` Christoph Rohland
2002-01-23 8:01 ` Eric W. Biederman
[not found] <20011214072540.D7457@duron.intern.kubla.de>
2001-12-17 13:24 ` Richard B. Johnson
2001-12-18 12:10 ` Helge Hafting
2001-12-18 14:00 ` Richard B. Johnson
2001-12-18 14:09 ` Alan Cox
2001-12-18 15:21 ` Mr. James W. Laferriere
2001-12-18 20:56 ` H. Peter Anvin
2001-12-18 16:27 ` Kent Borg
2001-12-18 17:05 ` Herman Oosthuysen
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='096201c18418$07d86bf0$5601010a@prefect' \
--to=brad@ltc.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 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.