linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/19] pramfs
Date: Sun, 08 Sep 2013 11:34:14 +0200	[thread overview]
Message-ID: <522C4496.2030009@gmail.com> (raw)
In-Reply-To: <522C3DDC.4090209@parallels.com>

Il 08/09/2013 11:05, Vladimir Davydov ha scritto:
> On 09/07/2013 08:22 PM, Marco Stornelli wrote:
>> Il 07/09/2013 16:58, richard -rw- weinberger ha scritto:
>>> On Sat, Sep 7, 2013 at 10:14 AM, Marco Stornelli
>>> <marco.stornelli@gmail.com> 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
>
> I'd like to add that in contrast to pstore, pramfs allows storing any
> files in it, not only system logs. This can be of value even on machines
> w/o special devices like sram/nvram: one can store data that should be
> quickly restored after reboot in conventional ram and use kexec to boot
> to a new kernel. One of the use cases of this could be checkpointing
> time-critical services to ram (using criu.org) to be quickly restored
> after a kernel update providing almost zero-downtime.
>

Yep. I add that if you use your system ram, your bootloader must be 
aware because it mustn't clear your memory after a reboot, indeed you 
can find reference of Pramfs in Uboot documentation:

http://www.denx.de/wiki/view/DULG/PersistentRAMFileSystem

Marco

  reply	other threads:[~2013-09-08  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07  8:14 [PATCH 00/19] pramfs Marco Stornelli
2013-09-07 14:58 ` richard -rw- weinberger
2013-09-07 16:22   ` Marco Stornelli
2013-09-08  9:05     ` Vladimir Davydov
2013-09-08  9:34       ` Marco Stornelli [this message]
2013-09-08  6:49 ` Marco Stornelli
2013-09-08 23:40 ` Dave Chinner
2013-09-09 18:13   ` Marco Stornelli
2013-09-09 23:28     ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=522C4496.2030009@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=vdavydov@parallels.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).