From: Christian Stroetmann <stroetmann@ontolinux.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/17] pramfs: persistent and protected RAM filesystem
Date: Sun, 10 Jun 2012 13:20:55 +0200 [thread overview]
Message-ID: <4FD48317.50706@ontolinux.com> (raw)
In-Reply-To: <4FD46521.5070900@gmail.com>
On Sun, June 10, 2012 Marco Stornelli wrote:
> Hi all,
>
> after the merge of pramfs in the LTSI kernel and after the "hot topic"
> NVM Mapping API, here a new submission of pramfs code. Even if the
> code won't be in mainline the review is really useful to me, so any
> comment is welcome.
Hello
I think we have here two cases:
1. "A block of non-volatile RAM separate for normal system memory",
[documentation Pramfs] and
2. The whole RAM is non-volatile and so the whole situation is changed,
and an NVM Mapping API is needed and "hotly" discussed.
For 1. your solution is a very good concept that is getting around
issues solely related with specific optimizations for disc-based file
systems, like the 2 problems described in the documentation of Pramfs, but
for 2. there is no need for a file system anymore, as we use it today
while working with a computer system, because data needs not to be
written to a file system at all, and so the file system will become
something like a backup system in the most common use cases of a
computing device, if I should describe it a little bit too provocative.
In this case your approach taken to handle the 2 problems mentioned in
the documentation of Pramfs would have to be driven further by focusing
more on the management of the RAM, the power, and the long-term data
storage (backup) for harmonizing Pramfs with them. A further point is to
make Pramfs bootable, if this not already possible somehow.
>
>
> The patch series is based on 3.5-rc2.
>
> Pramfs documentation:
>
> http://pramfs.sourceforge.net
>
> Git repo:
>
> git://pramfs.git.sourceforge.net/gitroot/pramfs/pramfs
>
> Marco
Have fun
Christian Stroetmann
next prev parent reply other threads:[~2012-06-10 11:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 9:13 [PATCH 00/17] pramfs: persistent and protected RAM filesystem Marco Stornelli
2012-06-10 11:20 ` Christian Stroetmann [this message]
2012-06-11 6:28 ` Marco Stornelli
2012-06-13 18:57 ` Florian Weimer
2012-06-14 6:17 ` Marco Stornelli
2012-06-14 6:17 ` Marco Stornelli
2012-06-16 6:57 ` Marco
-- strict thread matches above, loose matches on Subject: below --
2011-01-06 12:00 Marco Stornelli
2011-01-06 14:03 ` Peter Zijlstra
2011-01-06 16:26 ` Marco Stornelli
2011-01-06 16:58 ` Marco Stornelli
2011-01-06 18:22 ` Luck, Tony
2011-01-06 18:31 ` Marco Stornelli
2011-01-11 13:33 ` Pavel Machek
2011-01-11 19:01 ` Marco Stornelli
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=4FD48317.50706@ontolinux.com \
--to=stroetmann@ontolinux.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.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.