Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-28 Thread Ben Morrow
Quoth Unga unga...@yahoo.com: I think you may be reading too much into the malloc manpage.� When it mentions the use of per-thread small-object caches to avoid locking it's talking about performance, not thread safety.� Allocations of all sizes are thread-safe, the library just assumes

Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-28 Thread Jeremy Chadwick
On Wed, Mar 27, 2013 at 10:39:16PM -0700, Unga wrote: I think you may be reading too much into the malloc manpage.? When it mentions the use of per-thread small-object caches to avoid locking it's talking about performance, not thread safety.? Allocations of all sizes are thread-safe, the

Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-27 Thread Unga
- Original Message - From: Ian Lepore i...@freebsd.org To: Unga unga...@yahoo.com Cc: freebsd-stable@freebsd.org freebsd-stable@FreeBSD.org Sent: Wednesday, March 27, 2013 2:06 PM Subject: Re: FreeBSD 9.1 excessive memory allocations On Tue, 2013-03-26 at 11:35 -0700, Unga

Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-27 Thread Ronald Klop
On Wed, 27 Mar 2013 19:33:46 +0100, Unga unga...@yahoo.com wrote: - Original Message - From: Ian Lepore i...@freebsd.org To: Unga unga...@yahoo.com Cc: freebsd-stable@freebsd.org freebsd-stable@FreeBSD.org Sent: Wednesday, March 27, 2013 2:06 PM Subject: Re: FreeBSD 9.1 excessive

Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-27 Thread Ian Lepore
On Wed, 2013-03-27 at 11:33 -0700, Unga wrote: - Original Message - From: Ian Lepore i...@freebsd.org To: Unga unga...@yahoo.com Cc: freebsd-stable@freebsd.org freebsd-stable@FreeBSD.org Sent: Wednesday, March 27, 2013 2:06 PM Subject: Re: FreeBSD 9.1 excessive memory

Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-27 Thread Unga
I think you may be reading too much into the malloc manpage.  When it mentions the use of per-thread small-object caches to avoid locking it's talking about performance, not thread safety.  Allocations of all sizes are thread-safe, the library just assumes that huge allocations are rare