From owner-freebsd-arch Mon Jul 17 14: 0:48 2000 Delivered-To: freebsd-arch@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7230737BBD0 for ; Mon, 17 Jul 2000 14:00:44 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA92875; Mon, 17 Jul 2000 15:00:15 -0600 (MDT) (envelope-from ken) Date: Mon, 17 Jul 2000 15:00:15 -0600 From: "Kenneth D. Merry" To: Neil Blakey-Milner Cc: arch@FreeBSD.ORG Subject: Re: Conditionally removing cosmetic messages for small kernels (PICOBSD). Message-ID: <20000717150015.A92780@panzer.kdm.org> References: <20000717152514.A2056@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717152514.A2056@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Mon, Jul 17, 2000 at 03:25:14PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 17, 2000 at 15:25:14 +0200, Neil Blakey-Milner wrote: > Hi, > > While building a PicoBSD disk for work purposes, I noticed that > pcisupport.c was the largest object file sitting there, at 43k. > > By removing (#ifndef PICOBSD, better names accepted) the cosmetic probe > messages, I managed to reduce that to 23k easily enough, buying me a few > more executables (and NTFS support, which was why I was building the > disk). I would call it PCI_NO_STRINGS or maybe PCI_NO_DESCRIPTIONS, so that it can be easily used with something other than PicoBSD, and so it is a little more self-documenting. > If I were to do/start the work on the rest of the system, would this be > acceptable? Initial patch attached. (There seems to be "quirk" fixes > mixed in with the cosmetic stuff, so the patches aren't as clean as they > could be.) I think you'll find that most other areas of the system with large numbers of strings have already been taken care of. The only area other than the PCI code that I can think of with lots of text is CAM, and that has been #ifdef'ed since the beginning. For both the PCI code and the CAM code, though, I think the strings should be compiled out only when necessary. (like for PicoBSD) In most cases, the win from having the strings is far greater than the size cost. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message