Date: Sat, 24 Jan 2004 19:46:11 -0800 From: Kris Kennaway <kris@obsecurity.org> To: descarte@fruitbat.demon.co.uk Cc: questions@freebsd.org Subject: Re: FreeBSD AMD64 malloc(), mmap() Message-ID: <20040125034611.GA15570@xor.obsecurity.org> In-Reply-To: <E1AkXJA-000JS3-0Z@anchor-post-35.mail.demon.net> References: <E1AkXJA-000JS3-0Z@anchor-post-35.mail.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 24, 2004 at 11:35:20PM +0000, descarte@fruitbat.demon.co.uk wro= te: >=20 > Hi. I can't find a direct answer for these two linked questions, hence > the query to this email address. >=20 > We're looking into FreeBSD running on Athlon64 processors to give us the > ability to handle seriously huge datasets. We did buy a G5 machine, but > their implementation of BSD seems still only able to malloc() up to a > 4Gb process limit which is hardly what their advertising says! >=20 > Therefore, does the AMD64 FreeBSD port allow you to malloc() or mmap() > past this 4Gb per process limit. We're typically wanting to address up > to 256Gb in a single process. >=20 > Thanks in advance for any light you can shed on this. I believe the answer is 'yes', but you should ask on the freebsd-amd64 mailing list. Kris --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAEzwDWry0BWjoQKURAkrGAKCxXN+dL9AfVIj/j9rmlqayqdhtJgCg38Jw bLltJ/M9hyqjjqZzwMRkXXY= =Eas6 -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040125034611.GA15570>