Date: Thu, 2 Dec 2010 15:51:31 -0500 From: Andrew Duane <aduane@juniper.net> To: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Question about process rlimits Message-ID: <AC6674AB7BC78549BB231821ABF7A9AE907A1E0703@EMBX01-WF.jnpr.net>
next in thread | raw e-mail | index | archive | help
I've been poking at some bugs we have around pushing user memory to/past th= e limits of our box, and decided to try seeing what happens on a stock Free= BSD system (7.1 in this case). Basically I have a program that mallocs big memory chunks and zeros them to= consume both physical and virtual memory. I had expected the program to st= op malloc'ing when brk() reaches the process' RLIMIT_DATA (512MB cur and ma= x). It didn't. It happily malloc'd many gigabytes of memory until I stopped= it. On our 6.2 based product boxes, RLIMIT_DATA correctly stops the malloc from= continuing, just like the manuals say. Am I missing something? -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC6674AB7BC78549BB231821ABF7A9AE907A1E0703>