| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Jun 2009 00:38:55 +0200 From: Pavel Machek <pavel@....cz> To: Tim Bird <tim.bird@...sony.com> Cc: Marco <marco.stornelli@...il.com>, Jamie Lokier <jamie@...reable.org>, Linux Embedded <linux-embedded@...r.kernel.org>, Linux Kernel <linux-kernel@...r.kernel.org>, Linux FS Devel <linux-fsdevel@...r.kernel.org>, Daniel Walker <dwalker@....ucsc.edu> Subject: Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem 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/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists