From owner-freebsd-current@freebsd.org Sun Mar 25 10:42:07 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 E13CBF60D88 for ; Sun, 25 Mar 2018 10:42:07 +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 7D1D07F36B; Sun, 25 Mar 2018 10:42:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f0366-0008SB-KE; Sun, 25 Mar 2018 13:41:58 +0300 Date: Sun, 25 Mar 2018 13:41:58 +0300 From: Slawa Olhovchenkov To: Bryan Drewery Cc: Peter Jeremy , Jeff Roberson , FreeBSD current , Andriy Gapon Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180325104158.GB6612@zxy.spb.ru> References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> <20180320070745.GA12880@server.rulingia.com> <2b3db2af-03c7-65ff-25e7-425cfd8815b6@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b3db2af-03c7-65ff-25e7-425cfd8815b6@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-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 25 Mar 2018 10:42:08 -0000 On Fri, Mar 23, 2018 at 04:21:32PM -0700, Bryan Drewery wrote: > On 3/20/2018 12:07 AM, Peter Jeremy wrote: > > > > On 2018-Mar-11 10:43:58 -1000, Jeff Roberson wrote: > >> Also, if you could try going back to r328953 or r326346 and let me know if > >> the problem exists in either. That would be very helpful. If anyone is > >> willing to debug this with me contact me directly and I will send some > >> test patches or debugging info after you have done the above steps. > > > > I ran into this on 11-stable and tracked it to r326619 (MFC of r325851). > > I initially got around the problem by reverting that commit but either > > it or something very similar is still present in 11-stable r331053. > > > > I've seen it in my main server (32GB RAM) but haven't managed to reproduce > > it in smaller VBox guests - one difficulty I faced was artificially filling > > ARC. > > > > Looking at the ARC change you referred to from r325851 > https://reviews.freebsd.org/D12163, I am convinced that ARC backpressure > is completely broken. On my 78GB RAM system with ARC limited to 40GB and > doing a poudriere build of all LLVM and GCC packages at once in tmpfs I > can get swap up near 50GB and yet the ARC remains at 40GB through it > all. It's always been slow to give up memory for package builds but it > really seems broken right now. Can you test: revert all 'needfree' related commits and applay https://reviews.freebsd.org/D7538 ?