|Jason Evans||Apr 4, 2012 9:56 pm|
|John Baldwin||Apr 5, 2012 6:32 am|
|Konstantin Belousov||Apr 5, 2012 10:52 am|
|Jason Evans||Apr 5, 2012 11:55 am|
|Konstantin Belousov||Apr 5, 2012 12:09 pm|
|Jason Evans||Apr 5, 2012 3:47 pm|
|David O'Brien||Apr 12, 2012 11:40 am|
|Jason Evans||Apr 12, 2012 1:19 pm|
|David O'Brien||Apr 13, 2012 3:42 pm|
|Jason Evans||Apr 13, 2012 7:34 pm|
|Doug Barton||Apr 20, 2012 10:33 am|
|Pedro Giffuni||Apr 20, 2012 11:17 am|
|Doug Barton||Apr 20, 2012 1:35 pm|
|Pedro Giffuni||Apr 20, 2012 2:13 pm|
|Doug Barton||Apr 20, 2012 2:56 pm|
|David O'Brien||Apr 20, 2012 5:32 pm|
|Pedro Giffuni||Apr 20, 2012 6:05 pm|
|Doug Barton||Apr 21, 2012 12:22 am|
|Pedro Giffuni||Apr 21, 2012 2:19 pm|
|From:||John Baldwin (jh...@freebsd.org)|
|Date:||Apr 5, 2012 6:32:44 am|
On Thursday, April 05, 2012 12:56:45 am Jason Evans wrote:
I have the current version of jemalloc integrated into libc as contrib/jemalloc:
This is the first update to FreeBSD's jemalloc in over two years, and the
differences are huge (faster, better introspection, hopefully fewer
bugs). This has been stable for me across numerous buildworld/installworld
iterations, as well as when running several benchmarks. There's a bugfix to openpam in the patch that des says will be obsoleted by the next
vendor import, so I'm planning to let that settle before committing. In the meanwhile, I'm hoping for some review sanity checks on the following aspects
of the patch:
* Are the symbol versioning specifications right, and are the compatibility
symbols for _malloc_options and _malloc_message workable?
* Is it acceptable to check this in directly to trunk without using a vendor
branch? For the import workflow I have planned, a vendor branch would just be extra work with no benefit that I can see.
* Is the light editing of the jemalloc manual page sufficient? Keeping the
changes minimal will make regular imports less work, but the result is less tailored to FreeBSD.
* Will the utrace feature be missed? I removed it some time ago, mainly because
traces are impossibly large for most real-world use cases.
I will only speak to this one. I do still find this useful (I used it most recently a week or so ago). It would be nice to keep if it is not a major pain to maintain.
-- John Baldwin
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"