Date: Mon, 12 Dec 2005 08:50:01 +0800 From: David Xu <davidxu@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: Claus Guttesen <kometen@gmail.com>, Jason Evans <jasone@canonware.com>, current@freebsd.org Subject: Re: New libc malloc patch Message-ID: <439CC939.5080703@freebsd.org> In-Reply-To: <439CC5DA.3080103@elischer.org> References: <B6653214-2181-4342-854D-323979D23EE8@canonware.com> <Pine.LNX.4.53.0511291121360.27754@regurgitate.ugcs.caltech.edu> <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <b41c75520512031245q48521143m@mail.gmail.com> <7318D807-9086-4817-A40B-50D6960880FB@canonware.com> <b41c75520512040451t360eb01u@mail.gmail.com> <12CA5E15-D006-441D-A24C-1BCD1A69D740@canonware.com> <439CC5DA.3080103@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: >> >> No new problems in the malloc code have been found for some time >> now. It has been tested on i386, sparc64, arm, and amd64. In my >> opinion, the malloc patch is ready to be committed. I am now >> working on the assumption that new problems are more likely >> application bugs than malloc bugs. This seems like a good time to >> start sharing the debugging load with the community. =) >> >> So, how about it? Can this patch go in now? > > > > I may have missed it but some benchmark numbers could be good. > > Is there no way to make it an option for a while? > that would get good testing AND a fallback for people. > I also would like to see any benchmark number, in fact, I had plan to import ptmalloc in the past, the malloc problem had been discussed several times in thread@ list. Also, it would be nice if a fallback can be provided :-) David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?439CC939.5080703>