Date: Thu, 14 Jun 2007 18:16:17 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-hackers@freebsd.org Subject: Re: Reason for doing malloc / bzero over calloc (performance)? Message-ID: <f4rpkm$2jh$1@sea.gmane.org> In-Reply-To: <Pine.LNX.4.43.0706131025290.25469@hymn01.u.washington.edu> References: <20070613080334.GR89502@hoeg.nl> <Pine.LNX.4.43.0706131025290.25469@hymn01.u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6B7B45A5406C5DD96ADE7C60 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable youshi10@u.washington.edu wrote: > Hmmm... I wonder what the Mach kernel in OSX does to allocate memory > then. I'll have to take a look at OpenDarwin's source sometime and see > what it does. Following the link chain from the benchmark link posted in this thread I've come to the information that it's similar to -CURRENT: small allocations are carved from the local pool, big ones from prezeroed pages (from kernel). --------------enig6B7B45A5406C5DD96ADE7C60 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGcWnWldnAQVacBcgRAjZRAKDdNOcmX6zaUuNUqN9gVsN2jQ0TkQCgpHa4 E6oL4kOgo2bBffzDHmPZRKk= =OUXN -----END PGP SIGNATURE----- --------------enig6B7B45A5406C5DD96ADE7C60--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f4rpkm$2jh$1>