Date: Wed, 8 Jan 2020 21:45:02 -0800 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Jason Evans <jasone@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r354606 - in head: contrib/jemalloc contrib/jemalloc/doc contrib/jemalloc/include/jemalloc contrib/jemalloc/include/jemalloc/internal contrib/jemalloc/src lib/libc/stdlib/jemalloc Message-ID: <1cc79883-382f-dcad-ce0d-f8e26232e394@FreeBSD.org> In-Reply-To: <201911110506.xAB56nFV057050@repo.freebsd.org> References: <201911110506.xAB56nFV057050@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7YRoSZsvX4mwlDnWW1MpadYDkaDVR2xtB Content-Type: multipart/mixed; boundary="kfiX0fwcrTddB1GAYRnY4WFtKBcKzoH0i"; protected-headers="v1" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Jason Evans <jasone@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Message-ID: <1cc79883-382f-dcad-ce0d-f8e26232e394@FreeBSD.org> Subject: Re: svn commit: r354606 - in head: contrib/jemalloc contrib/jemalloc/doc contrib/jemalloc/include/jemalloc contrib/jemalloc/include/jemalloc/internal contrib/jemalloc/src lib/libc/stdlib/jemalloc References: <201911110506.xAB56nFV057050@repo.freebsd.org> In-Reply-To: <201911110506.xAB56nFV057050@repo.freebsd.org> --kfiX0fwcrTddB1GAYRnY4WFtKBcKzoH0i Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Do you plan to get this back in soon? I hope to see it before 12.2 if possible. Is there some way I can help? I'm interested in these changes in 5.2.1 (I think) - Properly trigger decay on tcache destroy. (@interwq, @amosbird) - Fix tcache.flush. (@interwq) - Fix a side effect caused by extent_max_active_fit combined with decay-based purging, where freed extents can accumulate and not be reused for an extended period of time. (@interwq, @mpghf) I have a test case where virtual memory was peaking at 275M on 4.x, 1GB on 5.0.0, around 750M on 5.1.0, and finally 275M again on 5.2.0. The 5.0/5.1 versions appeared to be a widespread leak to us. On 11/10/2019 9:06 PM, Jason Evans wrote: > Author: jasone > Date: Mon Nov 11 05:06:49 2019 > New Revision: 354606 > URL: https://svnweb.freebsd.org/changeset/base/354606 >=20 > Log: > Revert r354605: Update jemalloc to version 5.2.1. > =20 > Compilation fails for non-llvm-based platforms. --=20 Regards, Bryan Drewery --kfiX0fwcrTddB1GAYRnY4WFtKBcKzoH0i-- --7YRoSZsvX4mwlDnWW1MpadYDkaDVR2xtB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE+Rc8ssOq6npcih8JNddxu25Gl88FAl4Wvd5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 MTczQ0IyQzNBQUVBN0E1QzhBMUYwOTM1RDc3MUJCNkU0Njk3Q0YACgkQNddxu25G l8/SIQf/U1YA7Y9Q7SeW1X8hIeg/o5urK7F0IZZdY0SlFmz2LqC1WjzGWuv7n1B0 VatfmJVJ0S0UI/lucJeCvg/UGfYWA/L4OcIyjLqU9NLk/3IdNX9tw3T49exdPNgi 3W8mbarbxPzAiS56sA3jyT1cS+8tMAQ5YBBBEw85HLgSiKyz1ZmB162MzTdsi162 U8Zrp6PIcAWIZ8yuwV6KzYmYaH85mKVbzpQabpOUok7Yf/8bbpxvF2LEBE9oJX5E JO69wHpGpIo5UmPjDeY2FmW7Wi+J/qXKm2pW/PLs03ggdrwuLjcMclofG4YPcbNX xHecNvYtMdC8d+IwcWJnv/Tr0Sv8fw== =/Jag -----END PGP SIGNATURE----- --7YRoSZsvX4mwlDnWW1MpadYDkaDVR2xtB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1cc79883-382f-dcad-ce0d-f8e26232e394>