Date: Thu, 20 Dec 2018 11:58:43 -0800 From: Matthew Macy <mmacy@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-fs <freebsd-fs@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: The future of ZFS in FreeBSD Message-ID: <CAPrugNrLOq-qkuwzkG-9NhGuU0e6zDdYaqQs=n5aaj6utG0SbQ@mail.gmail.com> In-Reply-To: <CANCZdfoVFPOzGcyLWuv64%2BGx3%2BjUWB7Aanxy_t2xfcQ80wtGoA@mail.gmail.com> References: <CAPrugNriggEMMnLTZtf6xNQNYajBYNMnGdN96-ejDYQonoOhgw@mail.gmail.com> <CANCZdfoVFPOzGcyLWuv64%2BGx3%2BjUWB7Aanxy_t2xfcQ80wtGoA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 20, 2018 at 9:33 AM Warner Losh <imp@bsdimp.com> wrote: > > > Matt, > > This is a fairly comprehensive plan. Kudos for putting it together. > > The big question here is do you have a complete list of FreeBSD-specific changes that will be lost in the cut-over? We've heard about TRIM support and maybe NFSv4, but are there others that can be identified? > > Once you have that list, it wouldn't be hard to throw the initial email with some tweaks from the replies into a FCP so everybody knows the plan, and we have it ratified in case people come along later and 'forget'. The general intent is that we not lose anything. TRIM is the only piece of code that really needs resolution upstream causing us to lose it temporarily. Failure to upstream FreeBSD's TRIM support has been a recurring source of bugs when integrating new features. As for NFSv4 I've forked the ACL bits in to the OS dependent code - I'll make a note to make sure that nothing regresses there. This is yet another example of why there will be a 3 month period for users to try the port before we cut over. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPrugNrLOq-qkuwzkG-9NhGuU0e6zDdYaqQs=n5aaj6utG0SbQ>