From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Chris Dukes <pakrat@www.uk.linux.org>,
The Doctor What <docwhat@gerf.org>,
reiserfs-list@namesys.com
Subject: Re: Is it good for a PDA fs?
Date: Sun, 23 Jun 2002 00:56:30 +0400 [thread overview]
Message-ID: <3D14E47E.5080300@namesys.com> (raw)
In-Reply-To: 20020622230748.A1981@namesys.com
Oleg Drokin wrote:
>Hello!
>
>On Sat, Jun 22, 2002 at 09:50:33PM +0400, Hans Reiser wrote:
>
>
>>>faster. The tail merging might save space, but I would like to see
>>>a study of its effects on the longevity of compact flash.
>>>I think, but could be mistaken, than you want JFFS or JFFS2.
>>>
>>>
>>I also have a sharp zaurus with 256M CF......
>>Currently the CF uses VFAT, yes?
>>I bet it has the same wear issues, and no space savings....
>>
>>
>
>CF is different story. They fight level of wearing in underlying layer.
>
Meaning that they hide it in the device driver, and the FS does not need
to be aware of it?
>And on high level they emulate IDE.
>Zaurus also have compact flash memory directly accessible by CPU, that
>one can be access via MTD devices in Linux. There you can actually
>control wering by yourself. But reiserfs (v3) is not very suited for that
>JFFS & JFFS2 do.
>
>And you can format CF with reiserfs without any problems
>But do not expect that windows or digital cameras would understand
>that ;)
>Also - in conjunctions with PDAs - reiserfs is quite memory (RAM) hungry,
>so using it on 32M ram box is somewhat questionable.
>
>And static 32M journal (that's 13% off your CF size, btw)
>
Our journal resizing patch is waiting for the next pre1 to go in, yes?
Regardless of all of this, it really would not surprise me if a
filesystem design for CFs does a better job than we do at CFs.....
It is so annoying that it is taking so long for 2.4.19..... I respect
it, and it is probably the right thing for the users, but our
performance is suffering a lot for the lack of these patches in the
mainstream kernel.....
>
>
>
>>The zaurus has a non-standard kernel though, and it is based off of some
>>rather old release (2.4.4?). You would want to apply their kernel
>>extensions to 2.4.18 or later I think before using reiserfs.... If you
>>do so, and get it working, let me know, the only reason I haven't used
>>reiserfs on my CF is that I don't know where to get a recent kernel with
>>their (presumably useful to the PDA) extensions....
>>
>>
>
>Building ARM kernels is easy.
>I always build kernels for my ARM toys myself.
>
>and I bet that Zaurus kernel is based off some -rmk kernel with
>may be minor patches (sources of these should be available at Sharp
>of course).
>So getting (making) new kernel should be trivial.
>
I think I probably care more about downloading and trying the latest
kalendar than installing a new kernel on it.;-) It is nice to have ssh
running on it now.... After our July 11 DARPA presentation though I
will recompile the kernel, and maybe try reiserfs on an MMC, and test
how the user interface and docs are for journal relocation/resizing.....
>Especially if they use some decent bootloader that allows to have
>several kernels.
>
>
>
--
Hans
next prev parent reply other threads:[~2002-06-22 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 16:52 Is it good for a PDA fs? The Doctor What
2002-06-22 16:57 ` Chris Dukes
2002-06-22 17:50 ` Hans Reiser
2002-06-22 19:07 ` Oleg Drokin
2002-06-22 20:56 ` Hans Reiser [this message]
2002-06-23 6:50 ` Oleg Drokin
2002-06-23 7:18 ` Hans Reiser
2002-06-23 7:45 ` Oleg Drokin
2002-06-23 8:17 ` Hans Reiser
2002-06-25 17:35 ` The Doctor What
2002-06-26 4:56 ` Oleg Drokin
2002-06-28 20:50 ` Olivier
2002-06-28 23:22 ` Jose Alberto Guzman
2002-06-28 23:35 ` Chris Dukes
2002-06-29 6:13 ` Oleg Drokin
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=3D14E47E.5080300@namesys.com \
--to=reiser@namesys.com \
--cc=docwhat@gerf.org \
--cc=green@namesys.com \
--cc=pakrat@www.uk.linux.org \
--cc=reiserfs-list@namesys.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.