Date: Sun, 30 Jan 2005 22:41:27 -0500 From: Louis LeBlanc <FreeBSD@keyslapper.net> To: freebsd-questions@freebsd.org Subject: Re: having 1.5GB RAM I cannot allocate more than 512MB RAM in 4.10 Message-ID: <20050131034127.GA1178@keyslapper.net> In-Reply-To: <20050130150732.GA63409@gothmog.gr> References: <20050129120037.2E16A16A4D3@hub.freebsd.org> <1107027374.41fbe5ae47d36@webmail.uoi.gr> <41FC6144.90405@incubus.de> <1107067917.41fc840d574dd@webmail.uoi.gr> <20050130150732.GA63409@gothmog.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 01/30/05 05:07 PM, Giorgos Keramidas sat at the `puter and typed:
> On 2005-01-30 08:51, dkouroun@cc.uoi.gr wrote:
> >
> > Guys thanks for the help but it doesn't want to work!
>=20
> Actually, it works, but you are limited by the maximum allowable data
> size of the VM system.
>=20
> > Infact my data size setting in /etc/login.conf is unlimited by
> > default.
>=20
> True, but this won't work. Even if you set datasize to a large number
> of bytes, i.e. 8589934592 (800 MB), you are limited by the internal
> kernel limit for the maximum data size.
>=20
> This is defined in /usr/src/sys/i386/include/vmparam.h as:
>=20
> #define MAXDSIZ (512UL*1024*1024) /* max data si=
ze */
>=20
> When the setting of login.conf is applied, the following code runs from
> `src/sys/kern/kern_resource.c' (the implementation of the setrlimit(2)
> syscall):
>=20
> int
> kern_setrlimit(td, which, limp)
> struct thread *td;
> u_int which;
> struct rlimit *limp;
> {
> [...]
> case RLIMIT_DATA:
> if (limp->rlim_cur > maxdsiz)
> limp->rlim_cur =3D maxdsiz;
> if (limp->rlim_max > maxdsiz)
> limp->rlim_max =3D maxdsiz;
> break;
>=20
> Thus, the maximum data segment size is limited by the value of
> `maxdsiz'. The `maxdsiz' limit is tunable at boot time, by setting the
> "kern.maxdsiz" option in your `/boot/loader.conf' file.
What system are you getting that from? I don't see that sysctl var in
5.3:
# sysctl kern.maxdsiz
sysctl: unknown oid 'kern.maxdsiz'
# uname -a
FreeBSD keyslapper.net 5.3-RELEASE-p3 FreeBSD 5.3-RELEASE-p3 #3: Sun
Jan 30 22:16:29 EST 2005 root@keyslapper.net:/usr/obj/usr/src/sys/KEYSLAPPE=
R i386
I have the same limitations and the same apparently unlimited
configuration mentioned by the OP. I also have nothing resembling
MAXDSIZ in my kernel config.
Lou
--=20
Louis LeBlanc FreeBSD-at-keyslapper-DOT-net
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
Key fingerprint =3D C5E7 4762 F071 CE3B ED51 4FB8 AF85 A2FE 80C8 D9A2
Pardo's First Postulate:
Anything good in life is either illegal, immoral, or fattening.
--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFB/ajnr4Wi/oDI2aIRApNnAJ0emnBfuuz+3SUbAq4319YeZEV9rgCfWEb+
cgU2DCxlZ7iEP+wZA9ezjQY=
=ip1w
-----END PGP SIGNATURE-----
--gBBFr7Ir9EOA20Yy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050131034127.GA1178>