[lkml]   [2001]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Patch (repost): cramfs memory corruption fix
On Monday 08 January 2001 13:11, David Woodhouse wrote:
> said:
> > Also, if you care about memory usage, you're likely to be much better
> > off using ramfs rather than something like "ext2 on ramdisk". You
> > won't get the double buffering.
> That'll be even more useful once we can completely configure out all
> support for block devices too.

While the topic is raised..., I've hacked up cramfs for linear addressing to
kill the "double buffering" effiect. However as David mentions the block
device support thing is an issue here. What is a reasonable way to allow a
cramfs partition to access the device directly, like the patch that I wrote,
and be picked up in a reasonable way by the init system?

(Current system does some non-cool things like find out it's cramfs from
/dev/rom <also a patch>, and within cramfs never accesses that block device
anymore..., it's sort of silly, and _not_ the right way to do it.)

Shane Nay.
(Patches referenced here can be found at: , contributed
by various authors: Rob Leslie, Brad Laronde, and myself. If you want the
mkcramfs with xip, just ask.)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.057 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site