From owner-freebsd-stable@freebsd.org Thu Jul 27 15:42:21 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 043D6DCDAE6 for ; Thu, 27 Jul 2017 15:42:21 +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 B24A17EDD2; Thu, 27 Jul 2017 15:42:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1dakHT-000Fr6-Mm; Thu, 27 Jul 2017 18:00:51 +0300 Date: Thu, 27 Jul 2017 18:00:51 +0300 From: Slawa Olhovchenkov To: Alexander Motin Cc: Mike Tancsa , FreeBSD-STABLE Mailing List Subject: Re: Mega ZFS MFCs Message-ID: <20170727150051.GF18123@zxy.spb.ru> References: <088a85d2-ac64-3b43-eec5-3b21c06eb360@sentex.net> <0a0d4479-2cda-f8ae-965d-ff8bf0e4c3f5@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0a0d4479-2cda-f8ae-965d-ff8bf0e4c3f5@FreeBSD.org> 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-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2017 15:42:21 -0000 On Thu, Jul 27, 2017 at 04:29:52PM +0300, Alexander Motin wrote: > Hi Mike, > > On 27.07.2017 16:21, Mike Tancsa wrote: > > I noticed quite a few MFCs to RELENG_11 around zfs yesterday and today. > > First off, thank you for all these fixes/enhancements! Of the some 60 > > MFCs, are there any particular ones to be more aware of when updating > > servers ? > > The most complicated and invasive to me looks r321610 "8021 ARC buf data > scatter-ization". It took 5 fix commits to make it behave in head, but > Andriy told me it should be good now, and I run it on my systems too. > > > Are there any more to come, or is now a good time to test things out ? > > I've merged all we had in head (except couple gptzfsboot commits > significantly increasing its size, that could break POLA). Next round > will any way go to head first, so stable/11 should probably be idle for > a month at least and should be good for testing now. Ant chance for PR218043 and D7538?