Subject: Re: Increasing SHMMAXPGS
To: Perry E. Metzger <perry@wasabisystems.com>
From: Ignatios Souvatzis <is@netbsd.org>
List: tech-kern
Date: 05/19/2002 18:52:44
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 19, 2002 at 12:31:55PM -0400, Perry E. Metzger wrote:
>=20
> David Brownlee <abs@netbsd.org> writes:
> > 	We default to SHMMAXPGS=3D1024, which seems rather small given this
> > 	is the maximum limit and changes to it shouldn't affect the amount
> > 	of memory in use unless an application takes advantage of a higher
> > 	limit.
> >=20
> > 	Ogle (to give an example) likes a SHMMAXPGS of 16384.
> >=20
> > 	Would anyone object to increasing the default to 16384 for all
> > 	platforms?
>=20
> Yes. SHMMAXPGS should be nuked from orbit -- it should dynamically
> size itself. (We should also somehow garbage collect segments that are
> no longer associated with running processes.)

Uhm - but those could be accessed later by a new process, can't they?

	-is
--=20
seal your e-mail: http://www.gnupg.org/

--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE859hbPCRcZ/VMtk4RAuLBAJ9NArU3Tx/Vqy66ovXztNZL52D5oACfWsbz
R1chKJYfw5ZsPkTJp2IRo+I=
=pms7
-----END PGP SIGNATURE-----

--BXVAT5kNtrzKuDFl--