From owner-freebsd-arm@freebsd.org Mon Mar 5 19:50:48 2018 Return-Path: Delivered-To: freebsd-arm@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 A59D8F4AA5E for ; Mon, 5 Mar 2018 19:50:48 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [174.136.99.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oneyou.mgm51.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41C416ABC7 for ; Mon, 5 Mar 2018 19:50:47 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from sentry.24cl.com (sentry.24cl.com [IPv6:2001:558:6017:94:c582:1d99:a986:7609]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 3zw9W46rfHzWCVy for ; Mon, 5 Mar 2018 14:50:40 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mgm51.com; s=mgm51-02; t=1520279441; bh=Xcck9AmDoygF956rn8R49gAxG5QCgGlQBgoabl9TZQ0=; h=Subject:Cc:From:Message-ID:Date; b=Chxuhx9jRfwufoMw33Hm+/2wiI+ZNjSA1o5XELiAAyn9nXCHJBT93TNOpOhtRSpV5 vE84L07CwtbBahUJrxIOxivKqWpRHQX6B36RaLGoz8Fkn4/yDdld50c7Swa6faDOn1 vzJhVV4MaDnD4p5gvIPrV5LRTyrn+hAHOt4YPT5HwP2xwrRgdkc1OMKlKijsHQ3stz bkRHfgGTF0CCbwfRZ6Ngl4yzFxRsKRGwW+8DX24cVbFY+GsMNFK+nTQ/zhSdcOf9cp cB5tMNq1WnEX4ED8649Zs/IdZKhM36lbPmj1+xmXWRXEiBM7r9H28lzXuk+3kuhBdg EqH880Ni4NXGg== Received: from [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f] (unknown [IPv6:fdcf:b715:2f4d:1:b404:fcf5:70aa:786f]) by sentry.24cl.com (Postfix) with ESMTP id 3zw9W36kPDzkB4D for ; Mon, 5 Mar 2018 14:50:39 -0500 (EST) Subject: Re: Is maximum swap usage tunable? Cc: freebsd-arm@freebsd.org References: <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net> From: Mike Message-ID: Date: Mon, 5 Mar 2018 14:50:23 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305183331.GB47820@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 19:50:48 -0000 On 3/5/2018 1:33 PM, bob prohaska wrote: > On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: >> On 3/4/2018 11:57 PM, bob prohaska wrote: >>> On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: >>>> make -j4 buildworld >>> [snip] >[snip] >> >> # swapctl -l >> Device: 1024-blocks Used: >> /dev/md99 1048576 13248 >> >> ======= >> > Was swapctl run during the swap shortage, or after? In my observation swap > seems to be freed very quickly once make gives up, a few seconds usually. > Catching the swap shortage at its peak seems to require either watchful > waiting at a top window or more clever logging than I know how to implement. > Running gstat into a log file records device activity, which is interesting, > but one still has to rake through the log. > swapctl was run after the build had stopped. Oh I wish there were an option on swapctl to show min and max swap usage since the last time said stats were reset. :) >> >> I plan to try again, same hardware but with 2GB swap space. >> > Please post what you learn... Yup. It's running now. 2GB swap on USB-connected spinning rust.