From: Steve Longerbeam <stevel@mvista.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: new special filesystem for consideration in 2.6/2.7
Date: Mon, 08 Mar 2004 09:57:04 -0800 [thread overview]
Message-ID: <404CB3F0.2020701@mvista.com> (raw)
In-Reply-To: <20040305220950.GA5352@openzaurus.ucw.cz>
Pavel Machek wrote:
>Hi!
>
>
>
>>(PRAMFS). It was originally developed for three major consumer
>>electronics companies for use in their smart cell phones
>>and other consumer devices.
>>
>>An intro to PRAMFS along with a technical specification
>>is at the SourceForge project web page at
>>http://pramfs.sourceforge.net/. A patch for 2.6.3 has
>>been released at the SF project site.
>>
>>
>
>Well, I'd certainly love to see some usable linux cell phones.
>(Well, one such beast in my pocket would probably be enough :-)
>(Is there a way to make linux cell phone without second
>cpu just for GSM stack?)
>
one of the chips used in their cell phones is the TI OMAP1510.
It has an embedded TMS320c55 DSP as well as an ARM 925.
>
>Comments about pramfs: RAM is not really random access,
>you'll find that doing byte-sized random reads is way slower
>than linear read,
>but you are right that it is very different from disk.
>
>
>How do you handle powerfail in the middle of write?
>
good question, I don't - not in software anyway. But the companies
I mentioned may have implemented some kind of h/w safe shutdown,
but I'm not sure.
>Do you run fsck or do you have some kind of logging?
>
If you mean journaling, no, pramfs is not a journaling fs.
And you're right, I still need to write an fsck for pramfs.
At this point there is no way to recover a corrupt fs.
Steve
next prev parent reply other threads:[~2004-03-08 17:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 18:57 new special filesystem for consideration in 2.6/2.7 Steve Longerbeam
2004-03-05 18:09 ` Steve Longerbeam
2004-03-05 18:42 ` Dave Jones
2004-03-05 18:59 ` Steve Longerbeam
2004-03-07 3:06 ` Mike Fedyk
2004-03-18 19:28 ` Tim Bird
2004-03-05 22:09 ` Pavel Machek
2004-03-08 17:57 ` Steve Longerbeam [this message]
2004-03-08 22:35 ` Pavel Machek
2004-03-07 9:49 ` Christoph Hellwig
2004-03-07 10:10 ` Willy Tarreau
2004-03-08 18:42 ` Steve Longerbeam
2004-03-11 12:34 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 18:53 Steve Kenton
2004-03-07 3:07 ` Mike Fedyk
2004-03-08 0:07 Stephen M. Kenton
2004-03-08 18:37 ` Steve Longerbeam
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=404CB3F0.2020701@mvista.com \
--to=stevel@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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