From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Subject: Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem Date: Mon, 15 Jun 2009 19:44:28 +0200 Message-ID: <4A36887C.1050906@gmail.com> References: <4A33A7A2.1050608@gmail.com> <4A3681C2.5010508@am.sony.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Linux FS Devel , Linux Embedded , linux-kernel@vger.kernel.org, Daniel Walker To: Tim Bird Return-path: Received: from mail-bw0-f213.google.com ([209.85.218.213]:65196 "EHLO mail-bw0-f213.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754462AbZFORsZ (ORCPT ); Mon, 15 Jun 2009 13:48:25 -0400 In-Reply-To: <4A3681C2.5010508@am.sony.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Tim Bird wrote: > Marco wrote: >> This is a second attempt at mainlining Pramfs. The first attempt was >> back in early 2004 by MontaVista. Since then the kernel code has almost >> been completely rewritten. So my first item on the list was porting the >> code on a recent kernel version. After that I added the XIP support. > > It's very nice to see this technology revived. > > Is the information at: > http://pramfs.sourceforge.net/ > and > http://pramfs.sourceforge.net/pramfs-spec.html > still valid - particularly the latter? Yep. at 99%. I've done some modifications due to the porting and there will be some ones due to this review. I tried to talk with Steve Longerbeam to update the site but without success. I'd like to update it. > > It would be very nice to see this get mainlined. I believe that > one of the main uses for this is to store crash information > over a reboot so the next kernel (not in crashing state) can have > a better chance of dealing with it. As such, I think > it's important to keep the code paths for Pramfs short, synchronous, > and unentangled with other kernel systems (block IO, page cache, etc.). > Yes, I quite agree. I think that this kind of feature would be very useful especially for the embedded world. Marco