From owner-freebsd-arch@FreeBSD.ORG Tue Aug 29 10:35:42 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.ORG Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA87616A4DA for ; Tue, 29 Aug 2006 10:35:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 058FD43D5A for ; Tue, 29 Aug 2006 10:35:41 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (fgjajc@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k7TAZZkW008821; Tue, 29 Aug 2006 12:35:40 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k7TAZTiZ008820; Tue, 29 Aug 2006 12:35:29 +0200 (CEST) (envelope-from olli) Date: Tue, 29 Aug 2006 12:35:29 +0200 (CEST) Message-Id: <200608291035.k7TAZTiZ008820@lurza.secnetix.de> From: Oliver Fromme To: freebsd-arch@FreeBSD.ORG, John-Mark Gurney In-Reply-To: <20060828214712.GJ37035@funkthat.com> X-Newsgroups: list.freebsd-arch User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 29 Aug 2006 12:35:40 +0200 (CEST) Cc: Subject: Re: msgbuf default size... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 10:35:42 -0000 John-Mark Gurney wrote: > Poul-Henning Kamp wrote: > > John-Mark Gurney wrote: > > > > > I believe we should make the default 64k, and let other platforms, > > > like arm, use DEFAULTS to change it to smaller values if necessary... > > > > Better idea: > > I'd give you: > > > if (ram <= 64MB) > > msgbuf_size = 8k > > else > > msgbuf_size = 64k > > But anyone who is installing -current on a low memory system these days > are going to be tweaking and building custom kernels already... why > can't they tweak this option along w/ the rest? (look at Warner's work > to break out the PHY's) I noticed that AHC_REG_PRETTY_PRINT and AHD_REG_PRETTY_PRINT (which increase kernel size by 400 KB!) are also in GENERIC. Someone who builds a kernel for a small system will have to remove those anyway, so tuning MSGBUF_SIZE is probably not a big deal for him either. Therefore I also vote for increasing the default from 32 KB to 64 KB. It makes bug reports more useful if they include output from a verbose boot of GENERIC, which can easily exceed 32 KB these days. For similar reasons, I would like to ask for including the option INCLUDE_CONFIG_FILE by default in GENERIC. It only requires about 10 KB of space, but it can be extremely helful. I've quite often seen people asking how to recover their kernel configuration (e.g. lost during an update). INCLUDE_CONFIG_FILE would have saved their day ... It's probably a good idea to add a section to the tuning(7) manual page describing how to tune a kernel for systems with small memory. I might give it a try when I have a bit of spare time. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I learned Java 3 years before Python. It was my language of choice. It took me two weekends with Python before I was more productive with it than with Java." -- Anthony Roberts