From owner-freebsd-hackers@freebsd.org Sun May 19 12:55:17 2019 Return-Path: Delivered-To: freebsd-hackers@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 B407F15AD39C for ; Sun, 19 May 2019 12:55:17 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 7B8808B65D for ; Sun, 19 May 2019 12:55:15 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 87F77220AA for ; Sun, 19 May 2019 08:55:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 19 May 2019 08:55:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=rEzA1dTn3edBxIQYkBycKtoxm1G oNZA7nLX6xClcjoE=; b=my7w83fcDmLZ0LKBY0N874njGPD06Sgkw05yANpDe+v HTLvzAxF/ed8jXbxSDnVueFjX/sbMfv7QmDwoaXWt80eVhIXIIb2hJ4fSJL2V1ET n1TOVcVu7V3vi9kkILPrmw5AZ6Q3adyX5udpChXDvt6ch8+X61RMB3YtVWVVaT+w hC/mFkWScHWhcrDswHBZq/QdJz2edrbmmfNryaMePw5OdNRskMNqiA0XWpoCE6MS fW1cwhM5e0PA497AVZ4D9ghBwKCM29kAR2qNhajWj99c+HGhHDcOs+eek9+g80x5 M0LA9e4yE24u1XXMSLqFNzozvNP3ofczK5J7C7VNUEw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=rEzA1d Tn3edBxIQYkBycKtoxm1GoNZA7nLX6xClcjoE=; b=sr9t+a1c7c6HGuroH7eVZY PeEImpZUhjJobzedPzz+Amvkj9BQI76Lp/rCEa2RnMhVC5hH+hsAEI6FNObcW0KU IAkOHL5HFzxoYasf+0QiOaDSUTkddwG7hThBkoLkV6pOjjZ+wncGe9V/RCYTn84p /ifGkK0K2XSlBHDp+X31yg342gCjl5tLoO9uG57WX4p4qm6DE/bpzoXfj6WimEQw 3M/WiE8nPiewhheDL5abXs/lgjYh2OrUHbewjrhVGxt5NTJu+klbWJB4CfrTnKkW 0B65Uaz3D1v20nbelvyw6u7EibquzCGOTQhv49b8S1oCJ4lH/Z+CZPZYrwVdEaEw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddtiedgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehgtd erredtredvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshes iiihgihsthdrnhgvtheqnecukfhppeekvddrjedtrdeluddruddtudenucfrrghrrghmpe hmrghilhhfrhhomhepthgvtghhqdhlihhsthhsseiihiigshhtrdhnvghtnecuvehluhhs thgvrhfuihiivgeptd X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id B11528005B for ; Sun, 19 May 2019 08:55:08 -0400 (EDT) Date: Sun, 19 May 2019 13:55:06 +0100 From: tech-lists To: freebsd-hackers@freebsd.org Subject: Re: total configured swap exceeds maximum Message-ID: <20190519125505.GB6971@rpi3.zyxst.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 7B8808B65D X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=my7w83fc; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=sr9t+a1c; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.25 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-9.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[zyxst.net]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; MX_GOOD(-0.01)[in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; IP_SCORE(-3.38)[ip: (-9.13), ipnet: 66.111.4.0/24(-4.51), asn: 11403(-3.20), country: US(-0.06)]; RCVD_IN_DNSWL_LOW(-0.10)[25.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2019 12:55:17 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 19, 2019 at 12:06:38PM +0200, Wojciech Puchar wrote: >got this after configuring 160GB in 2 page partitions on 32GB RAM system. > > >warning: total configured swap (36700158 pages) exceeds maximum >recommended amount (32536376 pages). >warning: increase kern.maxswzone or reduce amount of swap. > > >what should i set kern.maxswzone to ? it is 0 > ># sysctl kern.maxswzone >kern.maxswzone: 0 Hi, Not sure if this answers your question, but my experience of swap was that it "likes"[1] (4 or 8 or 16GB) * N(umber of swapfiles/partitions)=20 and N=3D1 is usual for a system not doing heavy compiling work like poudrie= re.=20 It doesn't "like" 32GB or 64GB etc etc So on one poudriere system there is 32GB ram and 2*16GB swap partitions and one 16GB swapfile. On another there is 192GB RAM and 3* 16GB swap partitions. On a regular workstation with 8GB there's just one 8GB swap partition which is almost never used it seems. If it's one huge swapfile, it never seems to clear after the build completes. I have no idea why this might be. Then there's the thing about dump/panic. IIRC doesn't total swap have to be at least size_of_ram ? Like I say, I don't know if the above is "correct" or not. It's just my experience. [1] by which I mean "is effective" [2] swap partition or file is on SSD hardware --=20 J. --K8nIJk4ghYZn606h Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAlzhUh8ACgkQs8o7QhFz NAUJNw/9Efr8NVTghKAftLQzj7f39R/T6VZhEGvM9Qex6sBpTM3zih6DekcKOrNS fY8tTHr/ETJe2uOZLgOoW07dtQ4vaAD06R39OkJ++rWmBq4dEHPQR5gVixx5Lzge Ziwx0ND7GnGl1Xo5lFVIp65GwVbfwweqbY9G7eF6vC/mh6AcE/hnJnGbpLpAlIEC sQmA6xedKIV9VGETzJYPoZe7Blu7OuAJHBcIlCXVYREIxxdIykTIHaEhUj+tu48f IzjReyWgR1n9ah2+v0anLZMOvI6fqsIftJNBHRdkHM4pnSPS2Rb19XEB3FNs71Rr Dwc+NmvppRq0t4pKZs9gO4Yy8Bxo3C0paYuGenooLD14xmv2oTSd8MobQkf/M04+ W7nYpxcwt4Y3rLTC/zKxcLZF5I+UBmMYeGhifdUDZHkT3pNSPuTVo/xFS9SaqS3f Zb+YQr0GbPkB953EkIVgRyuW58xe97sXP3dVKYswub6xz30NAHTD8BXJlb9XyU6U cHhjui+/uPfoqwpN8kasyYFfLB4cSSe14jpVjTU7tWsLI1s2FBU6F8Bd+QxKcYAa Df07vJhTu7mDhh060byJlu+Q1j+jGVyuvS0OkN8x7Dg330ylMSMh0juwJVR36R/i GHlm7yDtJ/z/XLDy4H0D9GW/HzEOldgnVeeMI3ugRj9V7xHgWgY= =WIuP -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h--