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: Sun, 14 Dec 2008 22:17:04 +0300 [thread overview]
Message-ID: <49455BB0.7000300@gmail.com> (raw)
In-Reply-To: <gi38gg$56v$1@ger.gmane.org>
Ralph Ulrich wrote:
> Edward Shishkin Samstag 13 Dezember 2008 20:30:
>
>> I don't know such vfs doctrine. Who is the keeper of this doctrine?
>> :-)))
>>
> Please, do not be too ironicle here, because I am not an insider and english is not my motherlanguage. I meant there was a discussion that in the linux mainline kernel there should not be a filesystem which has files that can have files. A file as directory was introduced to unifiy namespace by namesys.
>
>
>> Subfiles mean one more step in the procedure of name resolution.
>> You should return an allocated inode to vfs for every such subfile.
>> So subfiles also can not be hidden. There is a temptation to cheat
>> vfs, so it will think that it deals with usual files, but such
>> cheating doesn't lead to happy end..
>>
>> xattrs is ugly, but working solution,
>> subfiles are nice, but it doesn't work.. ;)
>>
>
> First of all I have to understand reiser4 with no ambiguity:
>
> Are reiser4 file-plugins _only_ to handle data effective at low-level (like your compression plugin).
Nop.
There can be new features, which
. come from vfs;
. are not related to data storage improvements;
. require a new reiser4 plugin.
A good example - xattrs.
> 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.
> In reiser4 there is no such possibility to introduce a new kind of file which is hidden from vfs?
>
Yes, it is. For example, there are two regular file plugins in reiser4.
Both are intensively used, but vfs doesn't know about them.
> Semantics of reiser5 are totally out of scope here, but I thought of them as implementable above/on reiser4
Yes, I have pushed some technical concepts of r5 to r4 a year ago..
> - reiser4 as the technical grounds for reiser5 (as announced by namesys).
>
> Ralph
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2008-12-14 19:17 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 [this message]
2008-12-16 0:59 ` Ralph Ulrich
2008-12-17 21:49 ` Edward Shishkin
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=49455BB0.7000300@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.