On Monday 27 October 2008 12:15:30 Bernhard Reutner-Fischer wrote: > On Mon, Oct 27, 2008 at 02:21:55PM +0100, Bernd Schmidt wrote: > >Rob Landley wrote: > >> So svn 23660 broke arm with my .config, but if I change my .config from > >> MALLOC=y to MALLOC_STANDARD=y it works again. > >> > >> Does anybody understand the difference between the "MALLOC" > >> and "MALLOC_SIMPLE" options? The make help is not being useful here. > >> > >> Off to try MALLOC_SIMPLE... > > > >MALLOC_SIMPLE has disastrously bad performance. It should be removed. > > ------------------------------------------------------------------------ > r8199 | andersen | 2003-12-30 02:41:14 +0100 (Tue, 30 Dec 2003) | 4 > lines > > Update and restore malloc-simple. Slow as molasses, but trivially > simple and releases memory immediately when asked to do so. > -Erik > > Let me hide __libc_free_aligned for now (there is no immediately > obvious reason why that would be a public weak function, would anybody > know?) > > We could remove it later, after the release, but not right now.
Actually, rather than removing it, perhaps add this patch to the help text? (svn diff, so patch -p0). Rob
Index: extra/Configs/Config.in =================================================================== --- extra/Configs/Config.in (revision 23803) +++ extra/Configs/Config.in (working copy) @@ -442,14 +442,17 @@ config MALLOC_SIMPLE bool "malloc-simple" help - "malloc-simple" was written from scratch for uClibc, and is the - simplest possible (and therefore smallest) malloc implementation. - This uses only the mmap() system call to allocation memory, and does - not use the brk() system call at all, making it a fine choice for - MMU-less systems with very limited memory. It is rather dumb, and - certainly isn't the fastest. But it is 100% standards compliant, - thread safe, and very small. + "malloc-simple" is trivially simple and slow as molasses. It + was written from scratch for uClibc, and is the simplest possible + (and therefore smallest) malloc implementation. + This uses only the mmap() system call to allocate and free memory, + and does not use the brk() system call at all, making it a fine + choice for MMU-less systems with very limited memory. It's 100% + standards compliant, thread safe, very small, and releases freed + memory back to the OS immediately rather than keeping it in the + process's heap for reallocation. It is also VERY SLOW. + config MALLOC_STANDARD bool "malloc-standard" depends on ARCH_USE_MMU
_______________________________________________ uClibc mailing list uClibc@uclibc.org http://busybox.net/cgi-bin/mailman/listinfo/uclibc
