From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Stornelli Subject: Re: [PATCH 00/19] pramfs Date: Sat, 07 Sep 2013 18:22:18 +0200 Message-ID: <522B52BA.6030202@gmail.com> References: <522AE04C.6000002@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux FS Devel , Vladimir Davydov , Linux Kernel To: richard -rw- weinberger Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Il 07/09/2013 16:58, richard -rw- weinberger ha scritto: > On Sat, Sep 7, 2013 at 10:14 AM, Marco Stornelli > wrote: >> Hi all, >> >> this is an attempt to include pramfs in mainline. At the moment pramfs >> has been included in LTSI kernel. Since last review the code is more >> or less the same but, with a really big thanks to Vladimir Davydov and >> Parallels, the development of fsck has been started and we have now >> the possibility to correct fs errors due to corruption. It's a "young" >> tool but we are working on it. You can clone the code from our repos: >> >> git clone git://git.code.sf.net/p/pramfs/code pramfs-code >> git clone git://git.code.sf.net/p/pramfs/Tools pramfs-Tools > > I'm a bit confused, what kind of non-volatile RAM is your fs targeting? > Wouldn't it make sense to use pstore like > arch/powerpc/platforms/pseries/nvram.c does? > Usually battery-backed SRAM, but actually it can be used in any piece of ram directly accessible and it provides a normal and complete fs interface. Usually I do the fs test remapping my system ram. You can find documentation here: http://pramfs.sourceforge.net Marco