From owner-freebsd-threads@FreeBSD.ORG Thu Apr 14 16:27:12 2005 Return-Path: <owner-freebsd-threads@FreeBSD.ORG> Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A35FA16A4CE for <freebsd-threads@freebsd.org>; Thu, 14 Apr 2005 16:27:12 +0000 (GMT) Received: from bute.st-andrews.ac.uk (bute.st-and.ac.uk [138.251.12.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC1F943D4C for <freebsd-threads@freebsd.org>; Thu, 14 Apr 2005 16:27:11 +0000 (GMT) (envelope-from s_sourceforge@nedprod.com) Received: from kate (res04-ned6.res.st-and.ac.uk [138.251.234.67]) by bute.st-andrews.ac.uk (8.9.1a/8.9.1) with SMTP id RAA06409 for <freebsd-threads@freebsd.org>; Thu, 14 Apr 2005 17:22:09 +0100 (BST) From: "Niall Douglas" <s_sourceforge@nedprod.com> To: freebsd-threads@freebsd.org Date: Thu, 14 Apr 2005 17:26:40 +0100 MIME-Version: 1.0 Message-ID: <425EA7D0.20279.12A9E357@localhost> Priority: normal In-reply-to: <425E4B01.2020104@fer.hr> References: <425E4810.7553.1133DEA0@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Content-Transfer-Encoding: 7BIT Subject: Re: thread aware malloc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads> List-Post: <mailto:freebsd-threads@freebsd.org> List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, <mailto:freebsd-threads-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 14 Apr 2005 16:27:12 -0000 On 14 Apr 2005 at 12:50, Ivan Voras wrote: > > I finally have a native 64 bit platform which I just bought, I'm > > just waiting on the release of v5.4. I'll post benchmarks here when > > I know, but I'm still expecting an order of magnitude difference. > > For performance reasons, RELENG_5_4 in the current state will be the > same as 5.4-RELEASE[1] - no way re@ would allow serious commits to it > :) If you're planning doing benchmarks on real hardware (not vmware), > which would be most interesting, you might as well start doing it now > (or do the linux part now, do preliminary 5.4, and update to > 5.4-release when it's ready, maybe repeat benchmarks) My university does not permit use of CVS or CVSup (firewalled), so I'll be waiting for the release. > Also, to avoid flames, you might want to run the results through > ministat (/usr/src/tools/tools/ministat) :) Useful. > [1] : You might need to exclude debugging facilities from kernel - > witness & invariants mostly, and do 'ln -fs jrz /etc/malloc.conf' Noted. Cheers, Niall