From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 12:36:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93560106566C; Fri, 24 Aug 2012 12:36:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 685228FC16; Fri, 24 Aug 2012 12:36:25 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C2F00B91E; Fri, 24 Aug 2012 08:36:24 -0400 (EDT) From: John Baldwin To: "Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?=" Date: Fri, 24 Aug 2012 07:48:19 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <502831B7.1080309@freebsd.org> <201208141346.12782.jhb@freebsd.org> <86a9xklj3j.fsf@ds4.des.no> In-Reply-To: <86a9xklj3j.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208240748.19737.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 24 Aug 2012 08:36:24 -0400 (EDT) Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 24 Aug 2012 12:36:25 -0000 On Friday, August 24, 2012 5:44:48 am Dag-Erling Sm=C3=B8rgrav wrote: > John Baldwin writes: > > Hmm, this is not true on i386 where the problem is not just the physical > > RAM required, but also address space. (The swap zone is all mapped int= o KVA=20 > > even if it isn't used.) This is why Alan's e-mail specifically > > mentioned amd64, ia64, etc. but not i386 in his list. I think i386 sti= ll > > needs this limit, and I think your commit jumped the gun a bit. >=20 > How about we reinstate the limit on i386, but increase it to 64 MB? > That would increase the theoretical maximum to ~15 GB. People with 8 GB > swap would get a warning, but would be unlikely to run into trouble. >=20 > (or we could increase the limit to 72351744 bytes, which is the precise > amount required to support 16 GB) Note that on i386 you can't get more than 4GB of RAM without PAE, and if you have any modern x86 box with > 4GB of RAM, you are most likely running amd64 on it, not i386. I think i386 would be fine to just keep the limit it had. =2D-=20 John Baldwin