On 10/07/13 12:00, Matthew Ahrens wrote:
On Mon, Oct 7, 2013 at 11:43 AM, Pawel Jakub Dawidek <[email protected] <mailto:[email protected]>> wrote:On Mon, Oct 07, 2013 at 10:51:26AM -0700, Matthew Ahrens wrote: > Agreed! As we consider creating a platform-independent codebase for > OpenZFS, we will need to define what interfaces it is allowed to use. > Something like libzpool's zfs_context.h + kernel.c, but less hacky. One of the hard parts I recall from my work was GFS and using it for .zfs/ directory. There were countless bugs with stuff like '..' directory (accessed locally and through NFS), automounting snapshots, etc. Good ideas, but to be clear, the GFS stuff (and the ZPL in general) would not be a candidate for inclusion in a platform-independent codebase, at least initially.
For Linux we had to drop the GFS code entirely and implement the .zfs directory using native interfaces. And we should be clear that the ZPL bits aren't part of the platform-independent code today. Although longer term I think a portable FUSE based ZPL would be handy.
Thanks, Brian _______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
