From owner-freebsd-current@freebsd.org Thu Dec 20 19:58:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1295E13524E2; Thu, 20 Dec 2018 19:58:56 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABECB6ADC6; Thu, 20 Dec 2018 19:58:55 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com [209.85.166.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 80C94E799; Thu, 20 Dec 2018 19:58:55 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it1-f176.google.com with SMTP id g85so3807078ita.3; Thu, 20 Dec 2018 11:58:55 -0800 (PST) X-Gm-Message-State: AA+aEWZryGy8f7KjeQhhQgVskCY9ywn6Hcb0uBwcZREoc6U2nf15BO9O FR1rd5eT95gKg8Go4bNd01POe9gwrLdcJz6Efgs= X-Google-Smtp-Source: ALg8bN4O7b0j6vR1+AkhII0UFSXDVmhFTywoC06WTavp+8HhZ7fr4ThuoFHI04anvt+Qm2vcH8Uehi/NTDmTA5JDIf4= X-Received: by 2002:a24:9005:: with SMTP id x5mr45809itd.102.1545335934972; Thu, 20 Dec 2018 11:58:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Matthew Macy Date: Thu, 20 Dec 2018 11:58:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The future of ZFS in FreeBSD To: Warner Losh Cc: freebsd-fs , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: ABECB6ADC6 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.965,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 19:58:56 -0000 On Thu, Dec 20, 2018 at 9:33 AM Warner Losh 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