From owner-freebsd-performance@FreeBSD.ORG Fri Dec 23 15:24:55 2011 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FC0B1065670 for ; Fri, 23 Dec 2011 15:24:55 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 22D208FC1C for ; Fri, 23 Dec 2011 15:24:54 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta06.emeryville.ca.mail.comcast.net with comcast id CeZt1i0041Y3wxoA6fQocS; Fri, 23 Dec 2011 15:24:48 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta15.emeryville.ca.mail.comcast.net with comcast id Cfml1i0171t3BNj8bfmlmr; Fri, 23 Dec 2011 15:46:46 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BC566102C19; Fri, 23 Dec 2011 07:24:52 -0800 (PST) Date: Fri, 23 Dec 2011 07:24:52 -0800 From: Jeremy Chadwick To: John Baldwin Message-ID: <20111223152452.GA21957@icarus.home.lan> References: <4EF3C0CE.5040802@zedat.fu-berlin.de> <20111222235846.GA6071@icarus.home.lan> <201112231000.05712.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201112231000.05712.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Fri, 23 Dec 2011 15:49:29 +0000 Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, igor@hybrid-lab.co.uk, Alexander Leidinger , freebsd-performance@freebsd.org, "O. Hartmann" Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 15:24:55 -0000 On Fri, Dec 23, 2011 at 10:00:05AM -0500, John Baldwin wrote: > On Thursday, December 22, 2011 6:58:46 pm Jeremy Chadwick wrote: > > On Fri, Dec 23, 2011 at 12:44:14AM +0100, O. Hartmann wrote: > > > On 12/21/11 19:41, Alexander Leidinger wrote: > > > > Hi, > > > > > > > > while the discussion continued here, some work started at some other > place. Now... in case someone here is willing to help instead of talking, feel > free to go to http://wiki.freebsd.org/BenchmarkAdvice and have a look what can > be improved. The page is far from perfect and needs some additional people > which are willing to improve it. > > > > > > > > This is only part of the problem. A tuning page in the wiki - which > could be referenced from the benchmark page - would be great too. Any > volunteers? A first step would be to take he tuning-man-page and wikify it. > Other tuning sources are welcome too. > > > > > > > > Every FreeBSD dev with a wiki account can hand out write access to the > wiki. The benchmark page gives contributor-access. If someone wants write > access create a FirstnameLastname account and ask here for contributor-access. > > > > > > > > Don't worry if you think your english is not good enough, even some one- > word notes can help (and _my_ english got already corrected by other people on > the benchmark page). > > > > > > > > Bye, > > > > Alexander. > > > > > > > > > > > > > > > > > > > > > > Nice to see movement ;-) > > > > > > But there seems something unclear: > > > > > > man make.conf(5) says, that MALLOC_PRODUCTION is a knob set in > > > /etc/make.conf. > > > The WiJi says, MALLOC_PRODUCTION is to be set in /etc/src.conf. > > > > > > What's right and what's wrong now? > > > > I can say with certainty that this value belongs in /etc/make.conf > > (on RELENG_8 and earlier at least). > > > > src/share/mk/bsd.own.mk has no framework for MK_MALLOC_PRODUCTION, > > so, this is definitely a make.conf variable. > > Eh, normal make variables can go in src.conf as well. They do not have > to be listed in bsd.own.mk. World builds include /etc/src.conf whereas > every make invocation includes /etc/make.conf via sys.mk. The only reason > to use /etc/src.conf is to have a place to put variables only affect > make buildworld / buildkernel but do not affect other make invocations. I was always under the impression src.conf(5) variables had to be manually added to bsd.own.mk and similar bits (e.g. src/tools/build/options/WITH_xxx which is what's used to create the src.conf(5) man page), but upon your comment and manual investigation on my part, I found you're indeed right. Taken from bsd.own.mk: 107 .if !defined(_WITHOUT_SRCCONF) 108 SRCCONF?= /etc/src.conf 109 .if exists(${SRCCONF}) 110 .include "${SRCCONF}" 111 .endif 112 .endif As long as third-party software doesn't depend on MALLOC_PRODUCTION for something (I don't know why something would, but who knows; maybe there's a third-party malloc implementation which might?), then putting it in src.conf would be fine (src/lib/libc/stdlib files reference it). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |