Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem [LWN.net]

From:		Pavel Machek <pavel-AT-ucw.cz>
To:		Tim Bird <tim.bird-AT-am.sony.com>
Subject:		Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem
Date:		Tue, 23 Jun 2009 00:38:55 +0200
Message-ID:		<20090622223855.GA25996@elf.ucw.cz>
Cc:		Marco <marco.stornelli-AT-gmail.com>, Jamie Lokier <jamie-AT-shareable.org>, Linux Embedded <linux-embedded-AT-vger.kernel.org>, Linux Kernel <linux-kernel-AT-vger.kernel.org>, Linux FS Devel <linux-fsdevel-AT-vger.kernel.org>, Daniel Walker <dwalker-AT-soe.ucsc.edu>
Archive-link:		Article, Thread

On Mon 2009-06-22 23:57:53, Pavel Machek wrote:
> On Mon 2009-06-22 14:50:01, Tim Bird wrote:
> > Pavel Machek wrote:
> > >> block of fast non-volatile RAM that need to access data on it using a
> > >> standard filesytem interface."
> > > 
> > > Turns a block of fast RAM into 13MB/sec disk. Hmm. I believe you are
> > > better with ext2.
> > 
> > Not if you want the RAM-based filesystem to persist over a kernel
> > invocation.
> 
> Yes, you'll need to code Persistent, RAM-based _block_device_. 

More politely said: "I believe you would be better off modifying
ramdisk to include the functionality for persistence."  New filesystem
should not really be neccessary. ext2 for performance, ext3 if you
need robustness from journalling, maybe something else makes sense,
too.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo...
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Log in to post comments)