From: Hans Reiser <reiser@namesys.com>
To: "Artem B. Bityuckiy" <dedekind@oktetlabs.ru>
Cc: reiserfs-list@namesys.com
Subject: Re: ReiserFS on large-scale flash
Date: Wed, 25 May 2005 10:31:07 -0700 [thread overview]
Message-ID: <4294B65B.3070003@namesys.com> (raw)
In-Reply-To: <4294B43C.2070200@oktetlabs.ru>
Artem B. Bityuckiy wrote:
> Hello,
>
> I'm designing new flash file system. And I'm thinking about the
> possibility to write plugins for ReiserFS to implement it (I know, it
> sounds crazy). I didn't thoroughly explore is it possible or not yet.
>
> I'm almost certain that it is impossible to do this with the current
> Reiser4 and more changes are needed. Flash devices just has another
> model, not the same as block devices. In a nutshell, you can't write
> twice to the same block (out-of-place writing property) and you must
> erase a several consecutive blocks before re-using any block (read
> here: http://en.wikipedia.org/wiki/Flash_memory).
>
> Currently there are no Flash file systems which are usable on large
> scale flashes, at least in Linux. And there is a real need in such FS.
>
> So, I'd like to know, are Reisre4 developers interested in this? Will
> I have some assistance from them if I find some Reiser4 limitation? Is
> it worth starting exploring Reiser4 or better just start new FS?
>
> Thanks.
>
Sure, go for it.
next prev parent reply other threads:[~2005-05-25 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 12:54 improving Reiserfs Performance Jos Houtman
[not found] ` <4294783C.5040001@darthvader.us>
[not found] ` <42947BCA.9080702@hyves.nl>
2005-05-25 15:55 ` Yiannis Mavroukakis
2005-05-25 16:24 ` Jos Houtman
2005-05-25 17:22 ` ReiserFS on large-scale flash Artem B. Bityuckiy
2005-05-25 17:31 ` Hans Reiser [this message]
2005-05-25 17:33 ` Artem B. Bityuckiy
2005-05-26 0:36 ` improving Reiserfs Performance John Dong
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=4294B65B.3070003@namesys.com \
--to=reiser@namesys.com \
--cc=dedekind@oktetlabs.ru \
--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.