From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ralph Ulrich <eulenreich@gmx.de>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: The... reiser4 with no ambiguity
Date: Thu, 18 Dec 2008 00:49:53 +0300 [thread overview]
Message-ID: <49497401.40005@gmail.com> (raw)
In-Reply-To: <gi6uhv$akc$1@ger.gmane.org>
Ralph Ulrich wrote:
> Edward Shishkin Sunday 14 December 2008 20:17:
>
>>> I know you stress this quiet often in your mails. Or is it just your
>>> focussing for now to get reiser4 mainline?
>>> Is it not possible to introduce new extended features in reiser4 and
>>> hide these features vfs?
>>>
>> Yes, it is possible, but, again, those features should implement
>> some new (optimal, efficient, safe, reliable, etc.) form of data
>> storage.
>>
>
> I have the idea to rewrite reiser4 code to another
> language
I am a bit disappointed: I wanted to concentrate efforts
on the Linux port..
> (probably D: has clean syntax, has classes and
>
yup, object-oriented means would be a plus.
> garbage collection) and then to have a demon system in
> user space where I can experiment to implement
> sql - database features. My aim is a winfs (Microsoft)
> like system where you have both a filesystem api
> and a full featured database.
>
> Could reiser4 fit well to my purpose ?
>
You might want a high-performance reiser4 storage level
with EOTTL technology.
File plugins and some methods (plug.file) of item plugins
are heavily integrated with the Linux vm subsystem, so you
will need to rewrite them.
> As of now all plugin types have to be "hard-formatted"
> on the partition. You cannot introduce
> new plugins to an existing filesystem, yes?
>
mm.. We can.
There is a notion of compatible development model "4.X.Y":
http://lwn.net/Articles/226251 (Appendix D)
Ask, if something is not clear.
> The first part of my work would be to enable a special place
> on disk for definitions of used plugins.
>
Sorry, can not understand the above.
Common notes:
1. As Flex already said, this project will take a lot of
man-hours. I would add it might be of the same order that
was spent for the original Reiser's project.
2. You might want the plugin design document.
I have promised it will be ready in this September..
Sigh.. Coming soon..
Edward.
next prev parent reply other threads:[~2008-12-17 21:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 21:34 The reiser4 programming style is recursive? Ralph Ulrich
2008-12-10 21:41 ` Teran McKinney
2008-12-10 22:07 ` Ralph Ulrich
2008-12-10 22:21 ` David Backeberg
2008-12-11 0:09 ` Ralph Ulrich
2008-12-11 4:49 ` Toby Thain
2008-12-10 22:23 ` Edward Shishkin
2008-12-11 0:23 ` Ralph Ulrich
2008-12-11 16:57 ` Edward Shishkin
2008-12-11 17:37 ` Ralph Ulrich
2008-12-11 18:12 ` Edward Shishkin
2008-12-11 19:05 ` Ralph
2008-12-11 22:56 ` Edward Shishkin
2008-12-12 16:21 ` Ralph
2008-12-13 19:30 ` Edward Shishkin
2008-12-14 15:24 ` The... reiser4 with no ambiguity Ralph Ulrich
2008-12-14 19:17 ` Edward Shishkin
2008-12-16 0:59 ` Ralph Ulrich
2008-12-17 21:49 ` Edward Shishkin [this message]
2008-12-18 12:28 ` Ralph Ulrich
2008-12-21 13:38 ` Edward Shishkin
2008-12-11 0:46 ` The reiser4 .... why it is the future Ralph Ulrich
2008-12-11 11:35 ` The reiser4 .... what it really means Ralph Ulrich
2008-12-11 12:22 ` Ralph Ulrich
2008-12-11 14:36 ` Alexander Lyamin
2008-12-11 17:11 ` The reiser4 ....SDK for experiments outside kernel Ralph
2008-12-11 19:10 ` Edward Shishkin
2008-12-11 19:56 ` Ralph
2008-12-11 23:03 ` Edward Shishkin
2008-12-11 23:04 ` Christian Stroetmann OntoLab
2008-12-12 0:54 ` Ralph
2008-12-11 14:56 ` The reiser4 .... what it really means Christian Stroetmann OntoLab
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=49497401.40005@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=eulenreich@gmx.de \
--cc=reiserfs-devel@vger.kernel.org \
/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.