From: Jeff Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Marc Perkel <marc@perkel.com>, Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: WinFS beta out
Date: Wed, 31 Aug 2005 12:01:25 -0400 [thread overview]
Message-ID: <4315D455.1050100@suse.com> (raw)
In-Reply-To: <43150100.40304@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> I didn't have any role in the reiser3 acls. I would never have designed
> them the way they got written. If you want high performance acls,
> sponsor me to supervise the work for reiser4, and they will be very high
> performance. Making them high performance in reiser4 is straightforward
> and easy.
I would have also rather designed them differently, as another item
associated with the key. One of the strengths of the reiserfs design was
the btree that allows nodes of various types. ACLs should have been
implemented this way, extents could have been implemented this way.
Unfortunately, when I tried doing that, I found that the implementation
does not at all live up to the design. The implementation can handle the
four core items, and those alone. The addition of a new item type causes
the system to panic. Those issues could have been fixed, but we still
would have been left with a filesystem that would panic if mounted on an
older kernel -- since reiserfs also has no concept of feature versioning.
The current implementation is hardly what I had envisioned ACLs and
xattrs being on reiserfs -- but was the only solution we could find to
still allow the filesystem to be mounted on an earlier kernel.
An ideal solution would have been to introduce reiserfs v3.7 with a new
magic, and add feature versioning to the superblock, similar to the way
ext[23] does it. I felt that would have been met with much, much more
resistance than the implementation I ultimately presented.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFDFdRVLPWxlyuTD7IRAmPpAJ9MoA9ge/yHyM4UvMdvSU25VMvYLwCcDoWt
qxZLg1eK8TExLasF287oWJc=
=7QFY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-08-31 16:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 4:36 WinFS beta out Gregory Maxwell
2005-08-30 5:42 ` Jake Maciejewski
2005-08-30 6:35 ` Hans Reiser
2005-08-30 13:39 ` LiFe
2005-08-30 15:45 ` Marc Perkel
2005-08-30 22:10 ` Lexington Luthor
2005-08-30 23:00 ` Christian Iversen
2005-08-31 1:06 ` Hans Reiser
2005-08-31 1:18 ` Christian Iversen
2005-08-31 10:44 ` LiFe
2005-08-31 13:45 ` michael chang
2005-09-01 8:24 ` LiFe
[not found] ` <b14e81f0050901070453f4d898@mail.gmail.com>
2005-09-01 14:04 ` michael chang
2005-08-31 0:59 ` Hans Reiser
2005-08-31 4:59 ` Marc Perkel
2005-08-31 5:46 ` David Masover
2005-08-31 7:13 ` Hans Reiser
2005-08-31 13:44 ` michael chang
2005-08-31 14:36 ` Fundind Reiser Development Marc Perkel
2005-08-31 19:54 ` Hans Reiser
2005-08-31 14:38 ` Funding " Marc Perkel
2005-08-31 21:44 ` WinFS beta out Hans Reiser
2005-08-31 14:32 ` Marc Perkel
2005-08-31 16:01 ` Jeff Mahoney [this message]
2005-08-31 17:32 ` changing label of disk Bedros Hanounik
2005-08-31 18:15 ` evilninja
2005-08-31 20:05 ` WinFS beta out Hans Reiser
2005-08-31 20:35 ` Marc Perkel
2005-08-31 17:45 ` Adrian Ulrich
[not found] ` <b14e81f00508301124ebf9ab9@mail.gmail.com>
2005-08-31 2:02 ` michael chang
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=4315D455.1050100@suse.com \
--to=jeffm@suse.com \
--cc=marc@perkel.com \
--cc=reiser@namesys.com \
--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.