Date: Tue, 22 Oct 2002 10:33:48 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Terry Lambert <tlambert2@mindspring.com> Cc: Danny Braniss <danny@cs.huji.ac.il>, Poul-Henning Kamp <phk@critter.freebsd.dk>, freebsd-hackers@FreeBSD.ORG Subject: Re: malloc Message-ID: <20021022153347.GA92973@dan.emsphone.com> In-Reply-To: <3DB50A5A.F87EDA78@mindspring.com> References: <E183u5Y-0003Yc-00@cse.cs.huji.ac.il> <3DB50A5A.F87EDA78@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 22), Terry Lambert said: > Danny Braniss wrote: > > > If you want GNU malloc behaviour, then you should install the > > > port for the GNU allocator, and use it instead of the system > > > allocator, and you will end up with the same behaviour that your > > > application has on Linux. > > > > what ticked my curiosity was that the linux binary did work, while > > the fbsd binary did the right thing with respect to the admin > > limits and coredumped when the datasize limit was exeeded. > > The FreeBSD malloc uses anonymous pages mmap'ed off of /dev/zero. > > The Linux malloc uses pages added to the process address space via a > call to sbrk. Actually, on FreeBSD only the page directory is mmap'ed. Data returned to the user is allocated via sbrk. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021022153347.GA92973>