----- Original Message -----
From: "H. Peter Anvin" <firstname.lastname@example.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 <email@example.com>
> In newsgroup: linux.dev.kernel
> > Ideally, i would give address/length of the fs in ROM to a function, and
> > would get a ramdisk configured to read its data exactly there, and not
> > 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
The cramfs patch I mentioned shuns the block layer and instead allows the fs
to read directly from ROM.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:27 EST