From owner-freebsd-current@freebsd.org Tue Jun 5 21:49:06 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 6F28FFF8B34 for ; Tue, 5 Jun 2018 21:49:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 027FC76840; Tue, 5 Jun 2018 21:49:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io0-x236.google.com with SMTP id d22-v6so5204466iof.13; Tue, 05 Jun 2018 14:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Rb2IpsyQeqoMYr5FlUPMHnG5puOsYPpCf9fCQE6Scns=; b=CNSzFLs8sdeTZwg5N/7/1u/bOJgP7L4ahNWiOEsZeITJGn0+TIrP3FFIzIyMWypvxs O56YoVJSJCR/3SoQKQgTFh8LXjKJisNOQ4NuSO8tpMpxwG3FoZHw7FJxiL2OWIfHZgxp 1c+Hj3P2sRpsBTRe3cNq/gbyCM/ADC2u0tnTwAq7atL4jj9cq7ZTI+i/KYoIbXVN5hRq hyFAwHQ3dv5ad87jRgd64hg6y68H60Qkd88i4DOcmG1WhhizqS0KbpO8J0v9RfNs4ywp nLCH2XY4f6L31QDAUDNyKlowgvRFnIw8zZYBRdZGEcxbhzi7DTz3ey4UHoxGugMvbkgV MXvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Rb2IpsyQeqoMYr5FlUPMHnG5puOsYPpCf9fCQE6Scns=; b=U0DCjUXlEu5Im4rwgwxp7eSwSgQRP8b+6t1gI+erP/YiwILtf/m/CoJ3UgnfCZGzvx Q2UA1WlO4wM91L7VTiRR6lZKiWiItDXg61mcw7FnkZyrtVd7NGV4nn7eliLjdzf48O9s hE7mpi1JDeYIdM4V9z97iiBG39uSwq/dyaiEupmbK9W6J4FOz6PWXX3iJgKHqSjdxv6o HKeFZIoI8cUKHEdQ+LFHrMuLuPgm2Q5DPnqLlX4X+y0Qo/38r7Aj2Qb6v2j4Lzi69R0/ D1Fa8vjXoPiUOgmA/yoemMXgCnGEJPVTq/ruWWf7yJRE2GysSQDue5+gOr4ODQ6nBML4 G0LQ== X-Gm-Message-State: APt69E2ijT5z23MZ8Tt0XEJWdnoKg7IRugRYVkxqyzOk14OabTNl1V+U EiK8Ttj+Y+o6pdf9bA/1VK5xKQ== X-Google-Smtp-Source: ADUXVKJlMv/HyFJwulCgeZNq/lLSfDIYR7BOGRRx5QmQSKl9Q/NS4eCHLiBp86TFkgoWtu3LMB2foA== X-Received: by 2002:a6b:3e56:: with SMTP id l83-v6mr394571ioa.75.1528235345226; Tue, 05 Jun 2018 14:49:05 -0700 (PDT) Received: from pesky ([75.98.19.133]) by smtp.gmail.com with ESMTPSA id m14-v6sm1244263iti.36.2018.06.05.14.49.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jun 2018 14:49:04 -0700 (PDT) Sender: Mark Johnston Date: Tue, 5 Jun 2018 17:48:08 -0400 From: Mark Johnston To: Lev Serebryakov Cc: gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180605214808.GA94301@pesky> References: <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 05 Jun 2018 21:49:06 -0000 On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > I complained about this also and alc@ gave me this hint: > > sysctl vm.pageout_update_period=0 > > Really, situation is worse than stated in subject, because processes > are being killed AFTER memory pressure, when here are a lot of free > memory already! > > It looks like very serious bug. The issue was identified earlier this week and is being worked on. It's a regression from r329882 which appears only on certain hardware. You can probably work around it by setting vm.pageout_oom_seq to a large value (try 1000 for instance), though this will make the "true" OOM killer take longer to kick in. The problem is unrelated to the pageout_update_period.