From owner-freebsd-current@freebsd.org Wed Sep 9 21:40:16 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F346D3DD821 for ; Wed, 9 Sep 2020 21:40:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BmwRN4MKlz3dLT; Wed, 9 Sep 2020 21:40:16 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1kG7p2-000K0n-HZ; Thu, 10 Sep 2020 00:40:08 +0300 Date: Thu, 10 Sep 2020 00:40:08 +0300 From: Slawa Olhovchenkov To: Ryan Moeller Cc: freebsd-current@freebsd.org Subject: Re: vfs.zfs.min_auto_ashift and OpenZFS Message-ID: <20200909214008.GB2033@zxy.spb.ru> References: <9592fb23-ef97-f0a2-5968-f10ae404e761@gmail.com> <37b914c8-6fb6-7c1c-9497-ae1402b8dd40@daemonic.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4BmwRN4MKlz3dLT X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Wed, 09 Sep 2020 21:40:17 -0000 On Wed, Sep 09, 2020 at 11:55:14AM -0400, Ryan Moeller wrote: > > On 9/8/20 4:31 PM, Niclas Zeising wrote: > > On 2020-05-02 02:20, Matthew Macy wrote: > >> OpenZFS doesn't have the same ashift optimization logic that FreeBSD > >> has. It's something that needs to be resolved before the code can be > >> integrated downstream. > > > > So currently all pools created with OpenZFS will use 512 bit > > alignment, at least if the underlying storage device uses 512bit > > sectors (which most drives tend to do)? > > > > If this is the case, it feels like a pessimisation. > > > > Regards > > > The vdev ashift optimizations from FreeBSD were put in OpenZFS before > the import into base. That sysctl does work now. Ugly hack w/ geom_noop required again?