From: Pavel Machek <pavel@ucw.cz>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 01/16 v5] pramfs: documentation
Date: Mon, 3 Jan 2011 08:45:27 +0100 [thread overview]
Message-ID: <20110103074526.GA2687@ucw.cz> (raw)
In-Reply-To: <4D0A5377.1020007@gmail.com>
Hi!
> +But the disk-based fs over non-volatile RAM block driver approach has
> +some drawbacks:
> +
> +1. Complexity of disk-based fs: disk-based filesystems such as ext2/ext3/ext4
> + were designed for optimum performance on spinning disk media, so they
> + implement features such as block groups, which attempts to group inode data
> + into a contiguous set of data blocks to minimize disk seeking when accessing
> + files. For RAM there is no such concern; a file's data blocks can be
Yes, and they are also used on 99% of machines out there -> well
debugged.
Is there fsck for pramfs available, for example?
> + This increases the efficient use of space on the media, i.e. more
> + space is dedicated to actual file data storage and less to meta-data
> + needed to maintain that file data.
So... how big is overhead of pramfs compared to ext2?
Can pramfs handle powerdown at arbitrary time?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2011-01-03 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 17:59 [PATCH 01/16 v5] pramfs: documentation Marco Stornelli
2011-01-03 7:45 ` Pavel Machek [this message]
2011-01-03 9:54 ` 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=20110103074526.GA2687@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=tim.bird@am.sony.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.