From owner-freebsd-bugs@freebsd.org Sat Oct 6 07:59:59 2018 Return-Path: Delivered-To: freebsd-bugs@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 864C010B0AE9 for ; Sat, 6 Oct 2018 07:59:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 143AF89D94 for ; Sat, 6 Oct 2018 07:59:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CD6E510B0AE1; Sat, 6 Oct 2018 07:59:58 +0000 (UTC) Delivered-To: bugs@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 BC0CF10B0AE0 for ; Sat, 6 Oct 2018 07:59:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D27989D92 for ; Sat, 6 Oct 2018 07:59:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BB8DF2189 for ; Sat, 6 Oct 2018 07:59:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w967xvtR058361 for ; Sat, 6 Oct 2018 07:59:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w967xvhm058360 for bugs@FreeBSD.org; Sat, 6 Oct 2018 07:59:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229764] Default settings allow system to wire all ram Date: Sat, 06 Oct 2018 07:59:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: FreeBSD@ShaneWare.Biz X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2018 07:59:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229764 --- Comment #2 from Shane --- (In reply to Andriy Gapon from comment #1) I'm not looking to change anything as memory is being allocated, I'm only looking at the sysctl settings, specifically arc_max being limited. Initial= ly the default settings but also when assigning a new value. Currently we have defaults and allow assigning values that let a system get into a non-respon= sive state. On a machine with 8GB of physical RAM, max_wired is 2.4GB and arc_max is 7G= B - that's RAM minus 1GB, so out of the box an 8GB system is allowed to wire mo= re than 9GB, well maybe not allowed but two unrelated areas assuming they can allocate. I know from experience that a system with 8GB that has over 7GB w= ired only responds to the reset button. In this configuration, I expect sysctl should prevent arc_max being more than 5GB. If max_wired is only user wired allocations, then kernel wiring is another factor to be added into the equation. So initally, as max_wired is 30% of RAM, the default arc_max should not be = set higher than 70% of RAM. When sysctl assigns a new value to arc_max the phys= ical RAM and max_wired (and kernel wiring?) should be considered to check if the= new value would allow the total wired RAM to be too high. --=20 You are receiving this mail because: You are the assignee for the bug.=