From: Marco Stornelli <marco.stornelli@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/19] pramfs
Date: Sat, 07 Sep 2013 18:22:18 +0200 [thread overview]
Message-ID: <522B52BA.6030202@gmail.com> (raw)
In-Reply-To: <CAFLxGvw1mJ5GSWMMZhznU0jJn4pvM+jthyLAtKnL_WvGALB6dg@mail.gmail.com>
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
Marco
next prev parent reply other threads:[~2013-09-07 16:22 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 [this message]
2013-09-08 9:05 ` Vladimir Davydov
2013-09-08 9:34 ` Marco Stornelli
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=522B52BA.6030202@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.