>From: "Darren J Moffat" <[EMAIL PROTECTED]>
>...
>> The other problem is that you basically need a global unique registry
>> anyway so that compress algorithm 1 is always lzjb, 2 is gzip, 3 is ....
>> etc etc. Similarly for crypto and any other transform.
>
>I've two thoughts on that:
>1) if there is to be a registry, it should be hosted by OpenSolaris
> and be open to all and
>
>2) there should be provision for a "private number space" so that
> people can implement their own whatever so long as they understand
> that the filesystem will not work if plugged into something else.
>
>Case in point for (2), if I wanted to make a bzip2 version of ZFS at
>home then I should be able to and in doing so chose a number for it
>that I know will be safe for my playing at home. I shouldn't have
>to come to zfs-discuss@opensolaris.org to "pick a number."
I'm not sure we really need a registry or a number space.
Algorithms should have names, not numbers.
The zpool should contain a table:
- 1 lzjb
- 2 gzip
- 3 ...
but it could just as well be:
- 1 gzip
- 2 ...
- 3 lzjb
the zpool would simply not load if it cannot find the algorithm(s) used
to store data in the zpool (or return I/O errors on the files/metadata it
can't decompress)
Global registries seem like a bad idea; names can be made arbitrarily
long to make uniqueness. There's no reason why the algorithm can't
be renamed after creating the pool might a clash occur; renumbering
would be much harder.
Casper
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
