Hello!

So this is interesting, to take a look at a potential directory layout. Are
we saying then that:

module/os/$arch/zfs_znode.c (zfs_vfsops, zfs_vnops)

is where files will go? There are some surprises in there, like

adb.c - are there really any changes at all between platforms?

zfs_vnops - this is where the meat is for ZFS, and has a lot of trickery to
get right? Admittedly I have 39 "#if APPLE" in there myself.

zio_crypt.c - surprised me a bit, but I did have to wrap uio calls.


There is also module/avl that we actually moved into spl/avl as we wanted
to use AVL in certain SPL related support functions. Having two copies
seems undesirable.

Is it worth having a config/os as well for configure.ac ? Actually, how is
configure.ac going to handle the various OS file inclusions ? Right now it
is only Linux from the looks of it.

Is it desirable to include more platforms? Are you guys actually ok with a
module/os/windows/* ?

We will have to work on a local repo, but how will future syncs be done?
Will Windows platform have to PR in changes to Windows files?

Yours excitedly,

Lund


Allan Jude wrote:
> OpenZFS Developers,
> 
> The FreeBSD project is attempting to switch its upstream source of ZFS from
> the illumos repo to ZFS-on-Linux. Since there is not really a shared point
> in history to try to make this switch commit-by-commit, it was decided to
> attempt to just port ZFS-on-Linux over to FreeBSD. In the process, creating
> an OS Dependent directory to separate out source files that are specific to
> Linux or FreeBSD.
> 
> If anyone is available to test these images, or review the code changes in
> the repo (github URL below), your help would be much appreciated.
> 
> -------- Forwarded Message --------
> Subject: CFT for FreeBSD + ZoL
> Date: Fri, 19 Apr 2019 07:46:00 -0400
> From: [email protected]
> To: [email protected], [email protected],
> [email protected]
> 
> FreeBSD Developers,
> 
> We're pleased to make available images allowing testing of FreeBSD using
> ZFS on Linux.  During this development cycle, the ZoL code has been made
> portable, and available in the ports tree as sysutils/zol and
> sysutils/zol-kmod, for userland/kernel bits respectively. While some have
> used these for testing, we felt it necessary to generate some installation
> images which are an easier method of getting up and started using ZoL.
> These images are built against FreeBSD 12-stable and 13-HEAD and will
> install a world / kernel with the base system ZFS disabled and the
> sysutils/zol ports pre-installed.
> 
> It is possible to these with both UFS or ZFS on root, and we're looking for
> feedback on any stability issues or other regressions that you see vs the
> legacy ZFS in base.
> 
> 
> FreeBSD 12-Stable
> 
> https://pkg.trueos.org/iso/freebsd12-zol/
> 
> 
> FreeBSD HEAD
> 
> https://pkg.trueos.org/iso/freebsd13-zol/
> 
> 
> Please report issues on our GitHub tracker at:
> 
> https://github.com/zfsonfreebsd/ZoF
> 
> Thanks and happy testing!
> 

-- 
Jorgen Lundman       | <[email protected]>
Unix Administrator   | +81 (0)90-5578-8500
Shibuya-ku, Tokyo    | Japan


------------------------------------------
openzfs: openzfs-developer
Permalink: 
https://openzfs.topicbox.com/groups/developer/T2b2cb7346ab24f1e-M308d9f1021078717852f7b54
Delivery options: https://openzfs.topicbox.com/groups/developer/subscription

Reply via email to