Re: Q about VSZ wrt NPTL

--===============0237128285==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="KDt/GgjP6HVcx58l"
Content-Disposition: inline


--KDt/GgjP6HVcx58l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Apr 29, 2004 at 08:08:54PM -0700, Sameer Suhas Deokule wrote:
> I am looking for information/answer as to any rationale behind choosing the default

> stacksize to be 10MB in RHEL3.0. i.e why 10. why not 1 MB or some other
> value ? Is it related to the processor OR the typical recursion nesting OR
> something else....? 

For single threaded applications (the ones the kernel sets up the stack for)
Linux historically always picked 8 Mb as stack; in RHEL3 we needed to extend
that somewhat to give a nett stack of 8Mb (we randomize the stack pointer
somewhat)

I assume you are aware of the posix function you can call before you create
threads that sets the stack size for those threads; if you really care about
stack size I would suggest to always call that and not depend on the OS
default.

--KDt/GgjP6HVcx58l
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAkgPYxULwo51rQBIRAoYPAJ4vi3XVTm8IxJ2HO/sXoeAwO1XuQQCgg4mI
ooYtzZtczIoaZPInG1B2jJk=
=agbz
-----END PGP SIGNATURE-----

--KDt/GgjP6HVcx58l--



--===============0237128285==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline