From owner-freebsd-stable@freebsd.org Thu Feb 18 08:03:08 2016 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 70840AABD90 for ; Thu, 18 Feb 2016 08:03:08 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A57118EE for ; Thu, 18 Feb 2016 08:03:08 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 592D9AABD8F; Thu, 18 Feb 2016 08:03:08 +0000 (UTC) Delivered-To: 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 58BCDAABD8E for ; Thu, 18 Feb 2016 08:03:08 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 1C4AB18ED for ; Thu, 18 Feb 2016 08:03:07 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 04A522842B; Thu, 18 Feb 2016 09:02:58 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8FA5028423; Thu, 18 Feb 2016 09:02:56 +0100 (CET) Message-ID: <56C57AAF.9060507@quip.cz> Date: Thu, 18 Feb 2016 09:02:55 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Doug Hardie , Lowell Gilbert CC: stable@freebsd.org, Efra?n D?ctor , hiren panchasara Subject: Re: intr using Swap References: <56C4AF81.3040202@motumweb.com> <87f6fb602e0ad11b7600c70a08d74c30@dweimer.net> <56C4C244.8070805@motumweb.com> <56C4F7E9.9090405@motumweb.com> <20160217230138.GJ89208@strugglingcoder.info> <44d1rusuxs.fsf@lowell-desk.lan> <49F794B1-937F-4AEA-90CF-7C19AFF7EFE2@lafn.org> <447fi2sse9.fsf@lowell-desk.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 18 Feb 2016 08:03:08 -0000 Doug Hardie wrote on 02/18/2016 07:50: > >> On 17 February 2016, at 17:45, Lowell Gilbert wrote: >> >> Doug Hardie writes: [...] >> Your observations are more useful, but I'm still not sure they indicate >> a problem that needs to be solved. There are clearly cases where >> significant quantities of swap can get used up storing copies of clean >> pages backing files on disk. Unless that slows down bringing in new >> pages that need to be read or written, I don't think that's a problem. > > > Well, the problem is quite significant for me in that eventually the system runs out of swap and starts killing processes. Its not quite random, but I haven't spent much time trying to figure out how it selects those to kill. The specific system unfortunately is remote (about a 3 hour drive) and when sshd gets killed, I have no option other than having someone go on site to reboot it. Was sshd ever killed? I think FreeBSD has some "exceptions" implemented and some processes have higher value - not to be killed so easily. I had some system without swap and there were many processes killed every few days, but never sshd. Miroslav Lachman