Date: Sat, 9 Oct 2010 01:20:13 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-amd64@freebsd.org Subject: Re: linux32 sysctl limits? Message-ID: <20101008222013.GT2392@deviant.kiev.zoral.com.ua> In-Reply-To: <20101008221701.GA89977@troutmask.apl.washington.edu> References: <20101008221701.GA89977@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--KsUBxXnnTURmGdap Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 08, 2010 at 03:17:01PM -0700, Steve Kargl wrote: > 'man linux' does not list or describe the following sysctl > variables. >=20 > compat.linux32.maxvmem: 0 > compat.linux32.maxssiz: 67108864 > compat.linux32.maxdsiz: 536870912 >=20 > Are there any limitations with setting these to > say 1G for stack and 4G for data on a system with > 16G of memory? The linux ABI processes are 32bit, so you cannot reallistically assign 4Gb to maxdsiz. The space between data (bss) end and stack bottom is used for mappings, so it should be kept large enough. --KsUBxXnnTURmGdap Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyvmRwACgkQC3+MBN1Mb4inLwCg5PZQIU1cbWlOctQl18MgIDn+ eYYAoNEl+wfibkeAzIsFg669MPInN1Bo =f3H3 -----END PGP SIGNATURE----- --KsUBxXnnTURmGdap--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101008222013.GT2392>