From owner-freebsd-arm@freebsd.org Wed Aug 15 01:35:59 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 E3B04106D960 for ; Wed, 15 Aug 2018 01:35:58 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EEDA71FA8; Wed, 15 Aug 2018 01:35:58 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w7F1aCqv055654 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 14 Aug 2018 18:36:13 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w7F1aC90055653; Tue, 14 Aug 2018 18:36:12 -0700 (PDT) (envelope-from fbsd) Date: Tue, 14 Aug 2018 18:36:12 -0700 From: bob prohaska To: Warner Losh Cc: Mark Millard , freebsd-arm , Mark Johnston , bob prohaska Subject: Re: RPI3 swap experiments (grace under pressure) Message-ID: <20180815013612.GB51051@www.zefox.net> References: <20180812173248.GA81324@phouka1.phouka.net> <20180812224021.GA46372@www.zefox.net> <20180813021226.GA46750@www.zefox.net> <0D8B9A29-DD95-4FA3-8F7D-4B85A3BB54D7@yahoo.com> <20180813185350.GA47132@www.zefox.net> <20180814014226.GA50013@www.zefox.net> 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-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 01:35:59 -0000 On Tue, Aug 14, 2018 at 05:50:11PM -0600, Warner Losh wrote: [big snip] > > So, philosophically, I agree that the system shouldn't suck. Making it > robust against suckage for extreme events that don't match the historic > usage of BSD, though, is going to take some work. > You've taught me a lot in the snippage above, but you skipped a key question: What do modern sysadmins in datacenter environments want their machines to do when overloaded? The overloads could be malign or benign, they might even be profitable. In the old days the rule seemed to be "slow down if you must, but don't stop". Page first, swap second, kill third. Has that changed? Perhaps the jobs aborted by OOMA can be restarted by another machine in the cloud? Then OOMA makes a great deal more sense. Thanks for reading! bob prohaska