From owner-freebsd-bugs Fri Feb 16 12:56:50 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA05223 for bugs-outgoing; Fri, 16 Feb 1996 12:56:50 -0800 (PST) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA05216 for ; Fri, 16 Feb 1996 12:56:48 -0800 (PST) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.1) id MAA02539; Fri, 16 Feb 1996 12:56:42 -0800 (PST) Received: from localhost by newport.ece.uci.edu (8.7.1) id MAA12845; Fri, 16 Feb 1996 12:56:40 -0800 (PST) Message-Id: <199602162056.MAA12845@newport.ece.uci.edu> To: "Garrett A. Wollman" cc: freebsd-bugs@freebsd.org Subject: Re: malloc() prob in 2.1R? In-reply-to: Your message of "Fri, 16 Feb 1996 15:49:42 EST." <9602162049.AA21188@halloran-eldar.lcs.mit.edu> Date: Fri, 16 Feb 1996 12:56:38 -0800 From: Steven Wallace Sender: owner-bugs@freebsd.org Precedence: bulk > Not at all surprising. The memory allocator in 2.1 allocates memory > for the next power of two greater than or equal to (size + > malloc_overhead). So, the next power of two greater than or equal to > (4096 + a_small_amount) is 8192. -current uses a different allocator > and doesn't over-allocate in this way. > That is STUPID! (perhaps easy to implement, but stupid nevertheless) Boy I'm glad phk put his new malloc in. This is a HUGE memory waster! (I'm gonna compile 2.1 libc using -current malloc) Steven