Date: Mon, 20 Apr 2020 16:41:26 +0800 From: Li-Wen Hsu <lwhsu@freebsd.org> To: sgk@troutmask.apl.washington.edu Cc: Gordon Bergling <gbergling@googlemail.com>, freebsd-current <freebsd-current@freebsd.org>, Jason Evans <jasone@freebsd.org> Subject: Re: Outdated jemalloc in CURRENT Message-ID: <CAKBkRUx5DgDyDSim81ScCJKeMmFf7vXs613D1=h=TfF1ekXBmg@mail.gmail.com> In-Reply-To: <20200418152152.GA64335@troutmask.apl.washington.edu> References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> <20200418142003.GA64067@troutmask.apl.washington.edu> <20200418150108.GA14089@lion.0xfce3.net> <20200418152152.GA64335@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 18, 2020 at 11:22 PM Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote: > > > > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: > >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: > >>> Hi everyone! > >>> > >>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some > >>> performance regressions that was fixed in 5.2.1. > >>> > >>> Are there some issues that blocking update jemalloc to recent version? > >>> > >> > >> ------------------------------------------------------------------------ > >> r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines > >> > >> Revert r354605: Update jemalloc to version 5.2.1. > >> > >> Compilation fails for non-llvm-based platforms. > >> > >> ------------------------------------------------------------------------ > >> r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines > >> > >> Update jemalloc to version 5.2.1. > >> > > > > I am not sure, that this info is correct. As far as I remember the > > update for jemalloc was reverted due to build problems, on some > > architecture. An updated revision has still to be commited to -CURRENT. > > > > Those two commits confirm your memory. 5.2.1 was committed > in r354605. 5.2.1 was reverted with r354606 where the reason > for reverting is stated. As 5.2.1 has not been re-committed > and there is nothing in reviews.freebsd.org for review, one > may expect the reason in r354606 still stands. > > PS: Please, do not top-post. > PPS: Please, wrap your messages to something less than 80 characters. I think it's fine to (and hope we can) update it again as the previous error was on outdated gcc which is not existing anymore: https://lists.freebsd.org/pipermail/svn-src-all/2020-March/195013.html Li-Wen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBkRUx5DgDyDSim81ScCJKeMmFf7vXs613D1=h=TfF1ekXBmg>